• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Crash after Update

Marek M.

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
18.0.62
Hello,

I have got a VPS at OVH with licensed plesk instance.

There was a plesk update performed tonight. It caused lots of errors, and the worst is (according to OVH helpdesk) that AppArmor denies any kind of connection right now. The only access I have got right now is through mounted vol in rescue mode so I can change any file in the system but cannot execute any plesk command.

Former plesk update was 4 days ago and successfully touched py3 only.

Resume of the last update systemupdatestool.log (too large to attach) :

Code:
Removing systemd (247.3-7+deb11u4) ...
systemd is the active init system, please switch to another before removing systemd.
dpkg: error processing package systemd (--remove):
 installed systemd package pre-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
/var/lib/dpkg/info/systemd.postinst: line 82: addgroup: command not found
dpkg: error while cleaning up:
 installed systemd package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
 systemd
Processing was halted because there were too many errors.
E:Sub-process /usr/bin/dpkg returned an error code (1)
2024-08-06 06:27:44 ERROR: installArchives() failed
2024-08-06 06:27:44 ERROR: Exited with returncode 1.

What other log files shall I attach you to get broader view?

Any help appreciated. Thank you

Marek
 
Just an idea,

Did you try to chroot to the mounted volume?

#chroot /mountedvol

Then,

#systemctl stop apparmor && systemctl disable apparmor

#exit
 
Hi @WebHostingAce ,
Just an idea,

Did you try to chroot to the mounted volume?

#chroot /mountedvol

Then,

#systemctl stop apparmor && systemctl disable apparmor

#exit

Idea was perfect, but for some reason I could not manage apparmor through chroot. I spent several hours on that. Looks ike my system was more corrubpted than it looked liked originally. Effect: fresh install server, plesk and data retrieved from backup.

Thanks anyway. Really appreciated.
M.
 
Back
Top