SHIFT

--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools


Sidebar

Sponsor:

Would you like to sponsor this site?
Or buy me a beer?:


Recently Changed Pages:

View All Pages
View All Q Pages


View All Tags


Sign up for Q to post comments.





WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.


Terms And Conditions for Q users


Pages with comments

PageDateDiscussionTags
2019/05/01 14:08 2 Comments
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments

fixvumerror

Fix: Vmware Update Manager Unknown Error

During the upgrade from one of our hosts from 4.0 to 4.1 we experienced that the host would hang during the upgrade process, at exactly 33%. The first time I was inpatient and restarted vcenter, the host and tried again. That time I decided to wait. After more than an hour it failed with this error:

VMware vCenter Update Manager had an unknown error. Check the Tasks and Events tab and log files for details.

Also, when looking at the host in the esxupdate log (/var/log/vmware/esxupdate.log) I saw these errors:

[2011-03-03 22:56:14]   DEBUG:    cos.rpm: error: rpmdbNextIterator: skipping h#       2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)
[2011-03-03 22:56:14]   DEBUG:    cos.rpm: error: rpmdbNextIterator: skipping h#       2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)
[2011-03-03 22:56:14]   DEBUG:    cos.rpm: error: rpmdbNextIterator: skipping h#       2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)
[2011-03-03 22:56:14]   DEBUG:    cos.rpm: error: rpmdbNextIterator: skipping h#       2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)
[2011-03-03 22:56:14]   DEBUG:    cos.rpm: error: rpmdbNextIterator: skipping h#       2 Header SHA1 digest: BAD Expected(ec2f873ad51b3275ad5656a8a85cd0e2f7cff681) != (f777d38c915c35e45de79023745b6757c9b61038)

Fix

The problem is a corrupted rpm database. But when I tried to fix it I ran into a locking problem, probably because VMware Update Manager is still using the database:

[root@ESX-02 vmware]# rpmdb --rebuilddb
warning: waiting for transaction lock on /var/lib/rpm/__db.000

So I had to reboot the host (again), and after that I could fix the database:

[root@ESX-02 ~]# rpmdb --rebuilddb
error: rpmdbNextIterator: skipping h#       2 Header V3 DSA signature: BAD, key ID 37017186
[root@ESX-02 ~]# rpmdb --rebuilddb
Note: I ran the rebuilddb option twice to make sure there were no errors left.
You could leave a comment if you were logged in.
fixvumerror.txt · Last modified: 2013/04/20 13:05 by sjoerd