Search results

[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

I don't see any failure though.

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...

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...

results from journalctl -xe

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...

I did service sw-engine restart && service sw-cp-server restart I have this result. Redirecting to /bin/systemctl restart sw-engine.service 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 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.

has this been resolved? I have a similar issue.

After automatic updates from plesk, I cannot access plesk on browser anymore. The error is: This site can’t be reached "