hobaitsolutions
New Pleskian
- Server operating system version
- Ubuntu 22.04 x86_64
- Plesk version and microupdate number
- Plesk Obsidian 18.0.50.2
If I try to login, I end up with error 502.
Repair page says sw-engine.service is not running, but I'm unable to start it.
journalctl -xeu sw-engine.service gives following output
Repair page says sw-engine.service is not running, but I'm unable to start it.
journalctl -xeu sw-engine.service gives following output
systemctl status sw-engine.service░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ Automatic restarting of the unit sw-engine.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Feb 23 10:40:33 __server_name__ systemd[1]: Stopped Startup script for Panel sw-engine.
░░ Subject: A stop job for unit sw-engine.service has finished
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A stop job for unit sw-engine.service has finished.
░░
░░ The job identifier is 1236542 and the job result is done.
Feb 23 10:40:33 __server_name__ systemd[1]: Starting Startup script for Panel sw-engine...
░░ Subject: A start job for unit sw-engine.service has begun execution
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit sw-engine.service has begun execution.
░░
░░ The job identifier is 1236542.
Feb 23 10:40:33 __server_name__ systemd[1]: sw-engine.service: Main process exited, code=exited, status=219/CGROUP
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ An ExecStart= process belonging to unit sw-engine.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 219.
Feb 23 10:40:33 __server_name__ systemd[1]: sw-engine.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ The unit sw-engine.service has entered the 'failed' state with result 'exit-code'.
Feb 23 10:40:33 __server_name__ systemd[1]: Failed to start Startup script for Panel sw-engine.
░░ Subject: A start job for unit sw-engine.service has failed
░░ Defined-By: systemd
░░ Support: Enterprise open source support | Ubuntu
░░
░░ A start job for unit sw-engine.service has finished with a failure.
░░
░░ The job identifier is 1236542 and the job result is failed.
I'm unable to locate the problem, any hints?● sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/lib/systemd/system/sw-engine.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/sw-engine.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Thu 2023-02-23 10:42:21 CET; 2s ago
Process: 437592 ExecStart=/usr/sbin/sw-engine-fpm --fpm-config /etc/sw-engine/sw-engine-fpm.conf -c /usr/local/psa/admin/conf/php.ini --nodaemonize --pid /run/sw-engine.pid (code=exited, status=219/CGROUP)
Process: 437593 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=219/CGROUP)
Main PID: 437592 (code=exited, status=219/CGROUP)
Tasks: 1 (limit: 165)
Memory: 100.0M
CGroup: /system.slice/sw-engine.service
Feb 23 10:42:21 h3002040.stratoserver.net systemd[1]: sw-engine.service: Failed with result 'exit-code'.
Feb 23 10:42:21 h3002040.stratoserver.net systemd[1]: Failed to start Startup script for Panel sw-engine.