Red Hat Bugzilla – Bug 966025
[abrt] yum-3.4.3-91.fc19: rpmsack.py:38:<module>:ValueError: bad marshal data (string size out of range)
Last modified: 2013-05-24 10:01:29 EDT
Description of problem: Belw are the steps. 1. Installed fedora 18 machine. Did a "yum update -y" to update it 2. Executed fedup to upgrade it to fedora19 i.e. a. "su -c 'fedup-cli --network 19 --debuglog fedupdebug.log --instrepo http://dl.fedoraproject.org/pub/fedora/linux/development/19/x86_64/os/'" b. reboot to complete fedup 3. Did a "yum update -y" to update and it got completed successfully. But during the process it gave following error ************************************ error: rpmdb: BDB0113 Thread/process 28120/139758544803840 failed: BDB1507 Thread died in Berkeley DB library- ] 790 kB/s | 76 MB 00:00:13 ETA error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in (204/204): linux-firmware-20130418-0.1.gitb584174.fc19.noarch.rpm | 16 MB 00:01:03 error: rpmdb: BDB0113 Thread/process 28139/140727522924544 failed: BDB1507 Thread died in Berkeley DB library error: db5 error(-30973) from dbenv->failchk: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db5 - (-30973) error: cannot open Packages database in Finishing delta rebuilds of 43 package(s) (72 M) ******** 4. After the last step i.e. yum update, I rebooted the machine and logged and this issue came Version-Release number of selected component: yum-3.4.3-91.fc19 Additional info: reporter: libreport-2.1.4 cmdline: /usr/bin/python /usr/bin/yum update executable: /usr/bin/yum kernel: 3.9.3-301.fc19.x86_64 runlevel: N 5 uid: 0
Created attachment 751630 [details] File: backtrace
Created attachment 751632 [details] File: core_backtrace
Created attachment 751635 [details] File: environ
Without --downloadonly, Yum keeps rpmdb open when downloading packages. During that, applydeltarpm is spawned to rebuild RPMs from DRPMs, and it acesses rpmdb, too. But IMO this should not cause any problems, even if no locking was involved (two readers case). Anyway, rpmdb is corrupted. Does rpm --rebuilddb help?
*** This bug has been marked as a duplicate of bug 924417 ***
"rpm --rebuilddb " fixes the issue
Though "rpm --rebuilddb " fixes the issue. Thanks for the work around. But we still need to fix the root cause