Issue plesk not restarting

[Dominik_]

Server operating system version

Ubuntu 20.04

Plesk version and microupdate number

plesk obsidian

I tried restarting the server from the interface but plesk is unavailable since then.
`service sw-engine restart && service sw-cp-server restart` is supposed to restart the plesk services but doesn't seem to be working either.

Where can I find any log files or try to figure out whats happening?

 

[Maarten.]

Hi,

Check these files for errors or any related issues:

/var/log/sw-cp-server/error_log
/var/log/sw-cp-server/sw-engine.log

Also, check this support article:

Plesk for Linux services logs and configuration files

Applicable to: Plesk for Linux Question Where to find Plesk for Linux services logs and configuration files? Answer This article's sole purpose is to provide information regarding the services t...

support.plesk.com

 

[Dominik_]

ah okay thanks. though in there are only a bunch of failed requests - doesn't seem to be related to plesk itself not working
services sw-engine and sw-cp-server are supposedly running, psa is active(exited) so not sure about that

 

[bnda]

has this been resolved? I have a similar issue.

 

[Peter Debik]

@bnda Did you apply the above mentioned steps? What results did you get?

 

[bnda]

@Peter Debik

Job for sw-engine.service failed because the control process exited with error code. See "systemctl status sw-engine.service" and "journalctl -xe" for details.

 

[Peter Debik]

And what are the details that you find by following the output instructions?

 

[bnda]

sw-engine.service - Startup script for Panel sw-engine
Loaded: loaded (/usr/lib/systemd/system/sw-engine.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/sw-engine.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: exit-code) since Fri 2023-01-27 09:04:46 UTC; 4s ago
Process: 17376 ExecStopPost=/usr/bin/find /run/lock/lmlib/ -mindepth 1 -delete (code=exited, status=0/SUCCESS)
Process: 17362 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=254)
Main PID: 17362 (code=exited, status=254)
CGroup: /system.slice/sw-engine.service

Jan 27 09:04:46 p-hosting.example.com systemd[1]: Failed to start Startup script for Panel sw-engine.
Jan 27 09:04:46 p-hosting..example.com systemd[1]: Unit sw-engine.service entered failed state.
Jan 27 09:04:46 p-hosting..example.com systemd[1]: sw-engine.service failed.

 

[Peter Debik]

Hmm, not starting without giving a reason for it. Please try to find more details in /var/log/plesk/sw-cp-server/sw-engine.log or /var/log/plesk/sw-cp-server/error_log or - maybe - in the last rotated sw-engine log that may be named like sw-engine.log-20230126 or similar.

 

[bnda]

results from journalctl -xe

 

[Peter Debik]

- Do you have enough disk space on your partitions or might an upgrade have filled them up to the max so that daemons cannot write to them? Please check with # df.
- Did you apply any security measures, e.g. SELinux?
- Where any other changes applied to the file system, e.g. repartitioning, renaming of paths etc.?

 

[bnda]

Yes we have enough space. I believe. Plesk is working and then it autoupdate and then it happened like this. We are not doing any changes.

[root@p-hosting ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 16402044 0 16402044 0% /dev
tmpfs 16414848 0 16414848 0% /dev/shm
tmpfs 16414848 402572 16012276 3% /run
tmpfs 16414848 0 16414848 0% /sys/fs/cgroup
/dev/md4 485440648 152177176 308534752 34% /
/dev/md2 1373160 150440 1222720 11% /boot
/dev/md1 522160 10392 511768 2% /boot/efi
tmpfs 3282972 0 3282972 0% /run/user/0

 

[bnda]

checked /etc/fs-tab. do you see any issue?

[root@p-hosting ~]# cat /etc/fstab
/dev/md1 /boot/efi vfat defaults 0 2
/dev/md2 /boot/ ext3 defaults 0 2
/dev/nvme0n1p3 none swap sw 0 0
/dev/nvme1n1p3 none swap sw 0 0
/dev/md4 / ext4 errors=remount-ro 0 1

 

[Peter Debik]

Have there been any reports in autoinstaller3.log on a failed update?

 

[bnda]

I don't see any failure though.

 

[Peter Debik]

What is the output of
# plesk repair fs -system -v -n
?
(It's not gonna change a thing, it will only report.)

 

[bnda]

[root@p-hosting ~]# plesk repair fs -system -v -n
Could not open Repository at "/etc/sw/keys": Cannot create: /etc/sw/keys/lock/repository: Read-only file system
Error: must run as root.
exit status 1

 

[Peter Debik]

There seems to be some significant issue with file or user permissions on the server. It does not look as if this is related to Plesk itself, but the file system of the server. Either way this can only be checked and fixed by working on the server itself. Please open a ticket with Plesk support and let them access your server through SSH.

How to get support directly from Plesk?

Question How to get support directly from Plesk? Answer Lease-type Plesk licenses purchased directly from Plesk running on supported Plesk version include full free support. Perpetual-type license...

support.plesk.com