WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Frequent rpm db corruption / lock-up

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Frequent rpm db corruption / lock-up
From: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>
Date: Thu, 22 Sep 2005 11:26:55 -0700
Delivery-date: Thu, 22 Sep 2005 18:24:38 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hELz/b3QgjyyCsZUP89IPcqVQmvBn7r+a07oI3VUfiB+NelJTHUvp1geEPr6c/kQuDSm9eXTWkjvad4b50sWbpvt+E8wONY68NOywEdfZ2rHMeRlPFJdGMsW6plSItKzRX26js1Cg5MVgJl1bHKKzkPqHj05M4WI5FoT/gB1TkI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Reply-to: "Gino LV. Ledesma" <gledesma@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi, all

After deploying several xen hosts for various purposes (staging,
production, development, qa, etc), I've been seeing strange problems
involving rpm and yum. Two of the most frequently occuring problems
are:

1. Indefinite lock-up / "hang" when using yum or rpm -- doing an
strace shows that the process is waiting for a futex to complete, and
this will take forever (not sure if it actually completes).

2. rpmdb corruption -- rpm / yum complains about incorrect db version,
corrupted index, or whatnot.

In both cases, deleting /var/lib/rpm/__db* and recreating the db via
rpm --rebuilddb (optional) fixes it. But the problem will recur again
later. One fix I've found is to force it to use LD_ASSUME_KERNEL=x
where x is a really old kernel (pre-2.4.6).

Anyone else observed this problem? I'm not sure if /lib/tls is to be
blamed (I left it in place because I need db4 and a lot of ther
things). Using xen-2.0.7 and noticed this with 2.0.6 as well.

As always, thanks for the help in advance. :-)

- gino

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>