• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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