Segfaults with rpm 4.1.1 on Red Hat Linux 7.0 and 7.3

[Matthias Saou <matthias rpmforge net>]

Hi,

I've upgraded about 100 servers, some running Red Hat Linux 7.0 and others
7.3 to rpm 4.1.1 with yum 2.0.3. On a few of them, I'm getting segfaults,
and am unable to rebuilddb. The strange thing is that this may happen on
one of, say, 10 identical (hardware+software) servers.

Here is for instance what I'm getting on one of them :

# rpm -vvv --rebuilddb
D: rebuilding database /var/lib/rpm into /var/lib/rpmrebuilddb.27257
D: creating directory /var/lib/rpmrebuilddb.27257
D: opening old database with dbapi 3
D: unshared posix mutexes found(38), adding DB_PRIVATE, using fcntl lock
D: opening  db environment /var/lib/rpm/Packages create:cdb:mpool:private
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: locked   db index       /var/lib/rpm/Packages
D: opening new database with dbapi 3
D: unshared posix mutexes found(38), adding DB_PRIVATE, using fcntl lock
D: opening  db environment /var/lib/rpmrebuilddb.27257/Packages
create:mpool:private
D: opening  db index       /var/lib/rpmrebuilddb.27257/Packages create
mode=0x42D: unshared posix mutexes found(38), adding DB_PRIVATE, using
fcntl lock
D: opening  db environment /var/lib/rpm/Packages create:mpool:private
D: opening  db index       /var/lib/rpm/Packages rdonly mode=0x0
D: opening  db index       /var/lib/rpm/Pubkeys rdonly mode=0x0
error: rpmdbNextIterator: skipping h#     389 Header V3 DSA signature: BAD,
key ID db42a60e
D:  read h#     392 Header sanity check: OK
D: ========== ??? pubkey id a0d40840d0950840
Segmentation fault

This one segfaults early for every single operation. Others segfault much
later, like this for instance :

[...]
D:  read h#     260 Header V3 DSA signature: OK, key ID db42a60e
D:  read h#     264 Header sanity check: OK
D:  read h#     266 Header sanity check: OK
D:  read h#     278 Header V3 DSA signature: OK, key ID db42a60e
error: rpmdbNextIterator: skipping h#     312 Header V3 DSA signature: BAD,
key ID e42d547b
D: ========== ??? pubkey id 0000000000000000
error: rpmdbNextIterator: skipping h#     280 Header V3 DSA signature: BAD,
key ID 00000000
error: rpmdbNextIterator: skipping h#     312 Header V3 DSA signature: BAD,
key ID e42d547b
D: ========== ??? pubkey id 0000000000000000
error: rpmdbNextIterator: skipping h#     282 Header V3 DSA signature: BAD,
key ID 00000000
D: ========== DSA pubkey id 219180cddb42a60e
D:  read h#     284 Header V3 DSA signature: OK, key ID db42a60e
D:  read h#     286 Header SHA1 digest: OK
(38dfcda7e7fc0f76a716c9390b3de4ee42870bd7)
D:  read h#     288 Header V3 DSA signature: OK, key ID db42a60e
D:  read h#     290 Header V3 DSA signature: OK, key ID db42a60e
D:  read h#     292 Header V3 DSA signature: OK, key ID db42a60e
error: rpmdbNextIterator: skipping h#     312 Header V3 DSA signature: BAD,
key ID e42d547b
D: ========== ??? pubkey id 0000000000000000
error: rpmdbNextIterator: skipping h#     294 Header V3 DSA signature: BAD,
key ID 00000000
error: rpmdbNextIterator: skipping h#     312 Header V3 DSA signature: BAD,
key ID e42d547b
D: ========== ??? pubkey id 0000000000000000
error: rpmdbNextIterator: skipping h#     296 Header V3 DSA signature: BAD,
key ID 00000000
error: rpmdbNextIterator: skipping h#     312 Header V3 DSA signature: BAD,
key ID e42d547b
D: ========== ??? pubkey id b882060803000000
Segmentation fault (core dumped)

Any hints on how to fix this? For the "identical" servers, rsync'ing
/var/lib/rpm over is an option, but for the few "standalone" servers, it's
more of a problem.

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
 running Linux kernel 2.4.22-20.1.2024.2.36.nptl
Load : 0.26 0.32 0.35