On Mon, 25 Feb 2002, Buchan Milne wrote: > Fran�ois Pons wrote:
> >>/mnt/cdrom/Mandrake/RPMS2/openssh-askpass-gnome-3.0.2p1-5mdk.i586.rpm > >>Preparing... ########################################### [100%] > >>Segmentation fault (core dumped) > > > > Are you sure this is rpm which segfault, this could be located in %post of > > package (update-alternatives) ? > > > > Does you have staling /var/lib/rpm/__db* files ? > > You mean these: > [bgmilne:~]# ll /var/lib/rpm/*db* > -rw-r--r-- 1 root root 8192 Feb 25 10:37 /var/lib/rpm/__db.001 > -rw-r--r-- 1 root root 655360 Feb 25 10:37 /var/lib/rpm/__db.002 > [bgmilne:~]# > > Is a rpm --rebuilddb in order? Experience tells me this won't help :-( I mentioned this last week -- these are stale lockfiles -- a RPM process is dying (your segfault issue) -- or being killed without being allowed to clean up the lock files. A rpm --rebuilddb will remove stale lockfiles -- but if new lockfiles are being left, due to other issues, the problem will recur. The way to diagnose the underlying issue with the initial segfault is to run: rpm -Uvvvh (whatever) This is as verbose as RPM can get, and will (hopefully) show exactly where the segfault is occurring. Knowing that, you may then address the real issue, and once fixed, the lock files will be properly cleaned up. -- Russ Herrodl
