Mock Error Cannot Open Packages Database In /var/lib/rpm
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of thread died in berkeley db library rpmdb this site About Us Learn more about Stack Overflow the company Business Learn
Error: Cannot Open Packages Index Using Db3
more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question
Error Rpmdb Open Failed Centos
_ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's
Error: Cannot Open Packages Index Using Db3 - (-30974)
how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top yum Error:rpmdb open failed up vote 10 down vote favorite 3 I'm trying to run yum update and I'm running this error: rpmdb: PANIC: fatal region error detected; run recovery error: db3 error(-30974) from dbenv->open: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot db_runrecovery: fatal error, run database recovery open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: Error: rpmdb open failed I checked page like this one but running yum clean all runs the same error. How can I solve this? centos yum share|improve this question asked Apr 25 '15 at 15:40 Alex Jolig 364129 migrated from serverfault.com Apr 26 '15 at 12:51 This question came from our site for system and network administrators. add a comment| 2 Answers 2 active oldest votes up vote 21 down vote accepted This is how I fixed my problem. This is quite the messy situation. You may fix this by cleaning out rpm database. To minimize risk, make a backup of files in /var/lib/rpm/ using cp command: mkdir /root/backups.rpm.mm_dd_yyyy/ cp -avr /var/lib/rpm/ /root/backups.rpm.mm_dd_yyyy/ To fix this problem, try: # rm -f /var/lib/rpm/__db* # db_verify /var/lib/rpm/Packages # rpm --rebuilddb # yum clean all Verify that error has gone with the following yum command # yum update share|improve this answer answered Apr 25 '15 at 15:40 Alex Jolig 364129 This solution seems to work with dnf instead of yum as well. –unhammer Jan 18 at 14:30
the system gave me the below db3 error(-30974) from dbenv->failchk: db_runrecovery: fatal error, run database recovery error. [root@fedora-cloudibee home]# yum list | grep -i xml rpmdb: /var/lib/rpm/packages: unexpected file type or format rpmdb: Thread/process 31902/140347322918656 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: rpmdb open failed redhat DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: http://unix.stackexchange.com/questions/198703/yum-errorrpmdb-open-failed/198704 Error: rpmdb open failed [root@fedora-cloudibee home]# 12345678 [root@fedora-cloudibee home]# yum list | grep -i xmlrpmdb: Thread/process 31902/140347322918656 failed: Thread died in Berkeley DB libraryerror: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recoveryerror: cannot open Packages index using db3 - (-30974)error: cannot open Packages database in http://www.cloudibee.com/corrupt-rpmdb-and-recovery/ /var/lib/rpmCRITICAL:yum.main:Error: rpmdb open failed[root@fedora-cloudibee home]# I inititally thought it was some issue with yum and its cache, so tried yum clean. That did not work!. [root@fedora-cloudibee home]# yum clean rpmdb: Thread/process 31902/140347322918656 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main: Error: rpmdb open failed [root@fedora-cloudibee home]# rpm -qa rpmdb: Thread/process 31902/140347322918656 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm rpmdb: Thread/process 31902/140347322918656 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages database in /var/lib/rp
the epel-5-i386target. I had considered mach, which I have already used in the past,but since mock seems newer, better mantained an more integrated withfedora and some other tools which look to me very useful and promising( http://buildsys.fedoraproject.narkive.com/fzvUWkyH/mock-rpmdb-version-issue-with-epel-5-i386-target Cobbler, Koan, Koji ), I wanted to give it a shot.But? I seem http://forums.fedoraforum.org/showthread.php?t=188021 to have an issue with it. I started with a fresh FC11install, with the updates repo enabled, and installed mock from therepos;version 0.9.17 installed cleanly, and seems to be the latest version.My issue seems related to different rpmdb versions inside and outsidethe chroot which gets created. Take the following output:It seems the rpmdb cannot open of the chroot has been created with an rpmemploying a different format ( I can assume it's the 'host' system rpm), hence leading to a format mismatch which prevents from using rpmdbfrom inside the chroot.I have tinkered around for a little, but I couldn't find an easysolution (beyond installing everything from outside using mock--install, of course). Hence I've got some questions:Is that an intended behaviour? Is the cannot open packages rpmdb supposed to be convertedback to the proper format later on in the deployment process, if usingmock for building packages which be used later on in a possiblypre-build system?Alan Franzoni Alan Franzoni 2009-09-14 15:54:16 UTC PermalinkRaw Message I think I've forgot mock output :-/[user at cobblerserver mock]$ mock --init -r epel-5-i386INFO: mock.py version 0.9.17 starting...State Changed: init pluginsState Changed: startState Changed: lock buildrootState Changed: cleanState Changed: initState Changed: lock buildrootMock Version: 0.9.17INFO: Mock Version: 0.9.17INFO: enabled root cacheINFO: enabled yum cacheState Changed: cleaning yum metadataINFO: enabled ccacheState Changed: running yumState Changed: creating cache[user at cobblerserver mock]$ mock --shell -r epel-5-i386INFO: mock.py version 0.9.17 starting...State Changed: init pluginsState Changed: startState Changed: lock buildrootmock-chroot> rpm -qarpmdb: /var/lib/rpm/Packages: unsupported hash version: 9error: cannot open Packages index using db3 - Invalid argument (22)error: cannot open Packages database in /var/lib/rpmmock-chroot> rpm --rebuilddbrpmdb: /var/lib/rpm/Packages: unsupported hash version: 9error: cannot open Packages index using db3 - Invalid argument (22)mock-chroot> exit Mike McLean 2009-09-14 16:26:19 UTC PermalinkRaw Message Post by Alan Franzoni (mailing)It seems the rpmdb of the chroot has been created with an rpmemploying a different format ( I can assume it's the 'host' system rpm), hence leading to a format mismatch which pre
Common F23 Bugs Common F24 Bugs Communicate with Fedora The Documents Bug Reports Fedora Update System (Bodhi) Fedora Build System (Koji) Official Spins FedoraForum.org > Fedora 23/24 > Using Fedora How can I build i386 packages on a x86_64 system? FedoraForum Search User Name Remember Me? Password Forgot Password? Join Us! Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Ask questions about Fedora that do not belong in any other forum. Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Thread Tools Search this Thread Display Modes #1 11th May 2008, 04:43 PM nemesis963 Offline Registered User Join Date: Nov 2007 Posts: 16 How can I build i386 packages on a x86_64 system? I have a x86_64 system and I'm trying to build some packages for i386. For pidgin I execute the following command: Code: rpmbuild -ba --target i386 build/SPECS/pidgin.spec And I get the following output: Code: Building target platforms: i386 Building for target i386 Executing(%prep): /bin/sh -e /home/builder/build/tmp/rpm-tmp.28789 + umask 022 + cd /home/builder/build/BUILD + LANG=C + export LANG + unset DISPLAY + cd /home/builder/build/BUILD + rm -rf pidgin-2.4.1 + /usr/bin/bzip2 -dc /home/builder/build/SOURCES/pidgin-2.4.1.tar.bz2 + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd pidgin-2.4.1 ++ /usr/bin/id -u + '[' 484 = 0 ']' ++ /usr/bin/id -u + '[' 484 = 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + echo 'Patch #0 (pidgin-2.0.0-beta7-reread-resolvconf.patch):' Patch #0 (pidgin-2.0.0-beta7-reread-resolvconf.patch): + patch -p1 -s + cp /home/builder/build/SOURCES/purple-fedora-prefs.xml prefs.xml + exit 0 Executing(%build): /bin/sh -e /home/builder/build/tmp/rpm-tmp.66186 + umask 022 + cd /home/builder/build/BUILD + cd pidgin-2.4.1 + LANG=C + export LANG + unset DISPLAY + SWITCHES=--with-extraversion=1.fc8 + SWITCHES='--with-extraversion=1.fc8 --with-krb4' + SWITCHES='--with-extraversion=1.fc8 --with-krb4 --with-silc-includes=/usr/include/silc --with-silc-libs=/usr/lib64' + SWITCHES='--with-extraversion=1.fc8 --with-krb4 --with-silc-includes=/usr/include/silc --with-silc-libs=/usr/lib64 --enable-perl' + SWITCHES='--with-extraversion=1.fc8 --with-krb4 --with-silc-includes=/usr/include/silc --with-silc-libs=/usr/lib64 --enable-perl --enable-dbus' + SWIT