• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk 8.1.1 Update Fail: componentUpdate() failed: Unable to exec utility packagemng

D

disillusioned

Guest
I'm getting the following when trying to access Plesk through the web:

ERROR: PleskFatalException
Components::componentUpdate() failed: Unable to exec utility packagemng: Empty error message from utility.

0: /usr/local/psa/admin/auto_prepend/auth.php3:484



Looking at the console-based updater logs, we made it pretty far into the process:

Trying to start Plesk...
Trying to start Apache server... Stopping httpd: [ OK ]^M
Starting httpd: [ OK ]^M
done
/usr/local/psa/admin/bin/websrvmng: error while loading shared libraries: libmysqlclient.so.10: cannot open shared object file: No such file or directory
Trying to reconfigure Tomcat services...
ERROR while trying to configure PSA service

Aborting...

STOP psa-8.1.1-rhel3.build81070322.16 upgrading AT Thu Mar 29 21:43:00 MST 2007


It appears that Tomcat killed things. We don't use it, and could easily configure without it, if it were an option, but I have no idea how to do this, or why Tomcat can't configure.

Have rebooted. Have tried to run again from console. All domains are of course down, since Plesk isn't getting past its fatal error.

Any help would be much appreciated.
 
Back
Top