Sintomas

• Plesk não está acessível:

  502 Bad Gateway

• O serviço sw-engine está fora do ar:

  # systemctl status sw-engine -l .......... plesk.example.com systemd[1]: Starting Startup script for Panel sw-engine... plesk.example.com sw-engine-fpm[17102]: ERROR: failed to open error_log (/var/log/sw-cp-server/sw-engine.log): No such file or directory (2) plesk.example.com sw-engine-fpm[17102]: ERROR: failed to post process the configuration plesk.example.com sw-engine-fpm[17102]: ERROR: FPM initialization failed plesk.example.com systemd[1]: sw-engine.service: main process exited, code=exited, status=78/n/a plesk.example.com systemd[1]: sw-engine.service stop-sigterm timed out. Killing. plesk.example.com systemd[1]: Failed to start Startup script for Panel sw-engine. plesk.example.com systemd[1]: Unit sw-engine.service entered failed state. plesk.example.com systemd[1]: sw-engine.service failed.

Causa

O arquivo de log /var/log/sw-cp-server/sw-engine.log não existe no servidor.

Resolução

1. Conecte-se ao servidor usando SSH .

2. Recrie o diretório de log se ele não existir:

   # if [ ! -d "/var/log/sw-cp-server" ]; then mkdir /var/log/sw-cp-server && chmod 750 /var/log/sw-cp-server; fi

3. Recrie o arquivo de log ausente:

   # touch /var/log/sw-cp-server/sw-engine.log && chmod 600 /var/log/sw-cp-server/sw-engine.log

4. Começar sw-engine:

   # service sw-engine start