Home > Uncategorized > vzyum Database Recovery

vzyum Database Recovery

September 19th, 2008 Leave a comment Go to comments

Copied from others:

I’m getting this problem too after just having upgraded some packages on the host node. The fact that this can be corrected by entering the VPS and running any rpm command makes it look suspiciously like a bug. Any rpm database inside a VPS is somehow left in an inconsistent state. Of course, this makes vzyum unusable. Does vzyum need an upgrade in order to handle this?

vzyum 139 install wget

Yields:

exec /usr/share/vzyum/bin/yum -c /vz/template/centos/5/i386/config/yum.conf --installroot /vz/root/139 --vps=139 install wget
rpmdb: unable to initialize mutex: Invalid argument
rpmdb: PANIC: Invalid argument
rpmdb: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery

—

I’ve experienced the same behavior and found that a simple
rpm -qa run inside the VE (either via ‘vzctl exec’ or entering the VE and running it inside) solves the issue

update: unfortunately, this fix isn’t permanent and the issue reappears as soon as the VE is restarted as mentioned above
At least this workaround doesn’t need the installation of yum inside the VE

Categories: Uncategorized Tags:
  1. Grrruk
    October 18th, 2009 at 04:41 | #1
    Reply | Quote

    Yesssss! Many thanks! It works now. This post was the last piece of the centos 5 container puzzle.

    Btw, it’s very easy to fix completely by adding a line to /etc/rc.d/rc.local inside the container:

    /bin/rpm -qa >> /dev/null

    I’m shocked to see that they did not fix this problem yet 🙁

  1. No trackbacks yet.