Reese Knowledgebase

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

View Kristian Reese's profile on LinkedIn


If you like this article, please +1 or Recommend via FB with the provided buttons above:

Article ID: 71
by: Reese K.
Posted: 20 Oct, 2012
Last updated: 22 Oct, 2012
Views: 1560

PleskFatalException

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

If you see this error while attempting to load Plesk, look at the sw-cp-server error log for clues:

-bash-3.2# tail -f /var/log/sw-cp-server/error_log

rpmdb: Program version 4.3 doesn't match environment version
error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch
error: cannot open Packages index using db3 -  (-30974)
Internal RPM error: cannot open Packages index using db3 -  (-30974)
rpmdb: Program version 4.3 doesn't match environment version
error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch
error: cannot open Packages index using db3 -  (-30974)
Internal RPM error: cannot open Packages index using db3 -  (-30974)

In this case, the rpm database is corrupt.  This issue can be fixed by rebuilding the rpm database:

Solution:

-bash-3.2# rm /var/lib/rpm/__db.00*
-bash-3.2# rpm --rebuilddb

This article was:   Helpful | Not Helpful
Prev   Next
Using vzstat to get real time rx/tx rates per CTID     Blank login page with Parallels Plesk

RSS