On 06/04/2017 11:44 AM, Adam Williamson wrote: > Hi folks! > > So as you may have read, F26 Beta was held up by a tricky bug which > causes upgrades to hang in some situations: > > https://bugzilla.redhat.com/show_bug.cgi?id=1397087 > https://bugzilla.redhat.com/show_bug.cgi?id=1394862 > > There are updates in F24, F25 and F26 at present which we hope should > resolve this bug without causing other problems, but the code in > question is quite sensitive so we want to be as sure as possible that > it's good to go. On an F25 box, I ran 'dnf update', and it installed libdb.x86_64 5.3.28-21.fc25 among others. That run of 'dnf' dumped core, and all subsequent runs of dnf were unhappy: # dnf update ... Verifying : libdb-5.3.28-21.fc25.x86_64 18/80 ... Complete! Segmentation fault (core dumped) # dnf update error: rpmdb: BDB0113 Thread/process 6173/140680480651008 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 /var/lib/rpm Error: Error: rpmdb open failed I don't know how many others will have hosed systems now that libdb appears to have been pushed to stable, but it's a bummer that it happened to me. > > It would be great if folks can help test. You should probably only test > if you're confident in the old RPM database recovery trick - 'rm -f > /var/lib/rpm/__db* ; rpm --rebuilddb' - and on systems which aren't > *completely* mission critical. Thankfully, this tip appeared to work for me. > If you do run into any problems, please report them in the bug reports > and/or in reply to this mail. Hopefully my report helps; I'm willing to provide more details if you ask me questions and guide me to what I need to provide. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
