• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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