FC5t3 - rpm -e hangs up

Jan Andrejkovic jandrejkovic at gmail.com
Fri Mar 3 21:56:15 UTC 2006


Hello Jim and everybody who is willing to help,

Runlevel 1 did not help, but I have found the source of the problem,
unfortunatelly not the solution:

The source of the problem is that I have deleted some installed files
manually, without RPM.
Anyway I think rpm should be robust and it should not hang if some files are
deleted.
It should display some warning instead.

I have used -vv option and here is deailed output from rpm:
rm -f /var/lib/rpm/__db*
rpm -evv --justdb kernel-xen0-devel kernel-xenU-devel --allmatches
D: opening  db environment /var/lib/rpm/Packages create:cdb:mpool
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: locked   db index       /var/lib/rpm/Packages
D: opening  db index       /var/lib/rpm/Name rdonly mode=0x0
D:  read h#     468 Header SHA1 digest: OK (xxx)
D: opening  db index       /var/lib/rpm/Pubkeys rdonly mode=0x0
D:  read h#    1040 Header sanity check: OK
D: ========== DSA pubkey id xxx xxx (h#1040)
D:  read h#     732 Header V3 DSA signature: OK, key ID 4f2a6fd2
D:  read h#     117 Header SHA1 digest: OK (xxx)
D:  read h#     678 Header V3 DSA signature: OK, key ID 4f2a6fd2
D: ========== --- kernel-xen0-devel-2.6.12-1.1454_FC4 i686/linux 0x0
D: opening  db index       /var/lib/rpm/Requirename rdonly mode=0x0
D: ========== --- kernel-xen0-devel-2.6.13-1.1532_FC4 i686/linux 0x0
D: ========== --- kernel-xenU-devel-2.6.12-1.1454_FC4 i686/linux 0x0
D: ========== --- kernel-xenU-devel-2.6.13-1.1532_FC4 i686/linux 0x0
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, tree,
depth, breadth)
D:     0    0    0    3    1    0   -
kernel-xenU-devel-2.6.13-1.1532_FC4.i686
D: ========== successors only (0 bytes)
D:     1    0    0    0    1    1   -
kernel-xen0-devel-2.6.12-1.1454_FC4.i686
D:     2    0    0    1    1    2   -
kernel-xen0-devel-2.6.13-1.1532_FC4.i686
D:     3    0    0    2    1    3   -
kernel-xenU-devel-2.6.12-1.1454_FC4.i686
D: closed   db index       /var/lib/rpm/Pubkeys
D: closed   db index       /var/lib/rpm/Requirename
D: closed   db index       /var/lib/rpm/Name
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm/Packages
D: opening  db environment /var/lib/rpm/Packages joinenv
D: opening  db index       /var/lib/rpm/Packages create mode=0x42
D: mounted filesystems:
D:     i        dev    bsize       bavail       iavail mount point
D:     0 0x00000307     1024       287812       167116 /
D:     1 0x00000003     4096            0           -1 /proc
D:     2 0x00000000     4096            0           -1 /sys
D:     3 0x0000000a     4096            0           -1 /dev/pts
D:     4 0x00000011     4096        64439        64438 /dev/shm
D:     5 0x0000030c     1024       135546        99333 /home
D:     6 0x0000030b     1024       397619       131519 /tmp
D:     7 0x00000308     4096       260065      1462823 /usr
D:     8 0x0000030a     4096       157409       285427 /var
D:     9 0x00000013     4096            0           -1
/proc/sys/fs/binfmt_misc
D:    10 0x00000014     4096            0           -1
/var/lib/nfs/rpc_pipefs
D:    11 0x00000015     4096            0           -1 /net
D: sanity checking 4 elements
D: running pre-transaction scripts
D: computing 24608 file fingerprints
D: computing file dispositions
D: opening  db index       /var/lib/rpm/Basenames create mode=0x42
Killed

It hanged after the last step and I had to kill it.
I have straced it as well and here is the part of output from strace which
is running in a neverending loop:
<cut>
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/mach-visws",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/mach-voyager",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/math-emu",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/mm",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/oprofile",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/pci",
0xbfbd6784) = -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386", 0xbfbd6784)
= -1 ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch", 0xbfbd6784) = -1
ENOENT (No such file or directory)
stat64("/usr/src/kernels/2.6.12-1.1454_FC4-xenU-i686/arch/i386/power",
0xbfbd6784) = -1 ENOENT (No such file or directory)
<cut>

I have deleted my FC4 xen kernels in FC5t3 manually because I thought that
rpm dabase is already clear. I was wrong.
My RPM version is: 4.4.2

Do you think I should open bugzilla ticket?
Do you have any advice how can I reinstall my xen or what can I do?

By the way I have found very good rpm guide, but it did not help me either:
http://www.redhat.com/docs/books/max-rpm

Thank you very much,

Jan

On 3/1/06, Jim Cornette <fct-cornette at insight.rr.com> wrote:
>
> Jan Andrejkovic wrote:
> > Hello,
> >
> > I have upgraded FC4 to FC5t3. I had some xen problems therefore I have
> > decided to reinstall xen packages.
> > But when I try
> > rpm -e kernel-xen-hypervisor-devel or rpm -e kernel-xen-guest-devel rpm
> > hangs up and eats almost 100% cpu for long time.
> > I need to use kill -9 to stop it.
> >
> > I have tried to do
> > rm -f /var/lib/rpm/__db*
> > and
> > rpm --rebuilddb
> > but nothing helped after those commands - it hangs again.
> >
> > I have also tried rpm -e --justdb but it did not help either.
> >
> > Initially it was "yum remove" which hanged first. But as far as I know
> > it uses rpm therefore I report this as rpm problem.
> >
> > Does anybody have the same problem or can anybody tell me some
> > workaround how I can remove those packages manually and possibly rebuild
> > database without them?
> >
> > Thank you very much,
> >
> > Jan
> >
> >
>
> If rpm is consuming a lot of cpu percentage in regular boot, have you
> tried runlevel 1 or booting into rescue mode? Are the actions the same
> with cpu usage?
> There is an option to run rpm in rescue mode by issuing some parameter
> to reference the root in terms where rpm from the rescue CD is used and
> rpm removal/addition is performed in reference to /mnt/sysimage. I
> believe it was used successfully when some had problems with i386 arch
> packages were installed instead of the proper i686 rpms.
>
> The documentation is scarce for rescue mode and rpm. I found RHL 7.2, 9
> and RHEL4 The link is for RHEL4 which should be close to current
> information anyway.
>
>
> http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/sysadmin-guide/s1-rescuemode-boot.html
>
> If the rescue mode link does not help, how are others who upgraded from
> FC4 to FC5T3 systems reacting?
>
> Rawhide after FC5T3 was released installs go backwards and replace later
> version installed packages. I am wondering if this same personality for
> the installer is effecting FC4 to FC5T3 upgrades also. Major libraries
> were involved.
>
> FC5T1 through rawhide, then to FC5T3 install disc bug. (not supported,
> but may happen for FC4 or similar supported paths.
>
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183153
>
> Jim
>
> --
> Well fix that in the next (upgrade, update, patch release, service pack).
>
> --
> fedora-test-list mailing list
> fedora-test-list at redhat.com
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-test-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20060303/06f5b6d4/attachment.htm>


More information about the fedora-test-list mailing list