[Bug 1244513] rpm rebuild --what to do to recover from database crash

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1244513

Jan Silhan <jsilhan at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lsatenstein at yahoo.com
          Component|dnf                         |system-administrator's-guid
                   |                            |e
            Version|rawhide                     |devel
           Assignee|packaging-team-maint at redhat |swadeley at redhat.com
                   |.com                        |
            Product|Fedora                      |Fedora Documentation
            Summary|RFE: detect corrupt rpmdb,  |rpm rebuild --what to do to
                   |rebuild it                  |recover from database crash
         QA Contact|extras-qa at fedoraproject.org |docs-qa at lists.fedoraproject
                   |                            |.org
              Flags|needinfo?(packaging-team-ma |needinfo?(lsatenstein at yahoo
                   |int at redhat.com)             |.com)



--- Comment #4 from Jan Silhan <jsilhan at redhat.com> ---
we actually print log:
"...To diagnose the problem, try running: ''rpm -Va --nofiles --nodigest'
You probably have corrupted RPMDB, running rpm --rebuilddb"

Are we on the same page and talking about transaction check error after
transaction confirmation and not "Delta RPM rebuild failed"?

Your suggestions to improve this message are welcomed.

It's not a good idea to do rpmdb rebuild automatically by DNF itself. It could
cause more harm than good. The problems are usually more complicated ones
needed to be resolved by human. I'd prefer to document dealing with corrupted
database in examples. Once we identify most database issues then maybe some
community plugin will be made to detect and fix some of the cases but it's
really problematic.

Stephen, try to execute the commands above.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.