On Sun, Jul 19, 2009 at 10:42 AM, devzero2000 <[email protected]> wrote:
> On Sun, Jul 19, 2009 at 10:26 AM, Ralf S. Engelschall < > [email protected] <rse%[email protected]>> wrote: > >> Although we've not changed the underlying DB version in RPM 5, since >> recently with 5.1.9 I see at the end of the OpenPKG "bootstrap" package >> upgrade: >> >> | rpmdb: PANIC: fatal region error detected; run recovery >> | error: db4 error(-30974) from db->cursor: DB_RUNRECOVERY: Fatal error, >> run database recovery >> | [...] >> | rpmdb: File handles still open at environment close >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/__db.001 >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Packages >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Basenames >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Name >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Sha1header >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Triggername >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Group >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Providename >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Requirename >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Dirnames >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Requireversion >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Provideversion >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Installtid >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Sigmd5 >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Filedigests >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Packagecolor >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Nvra >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/Filepaths >> | rpmdb: Open file handle: /v/gmbh/sw/RPM/DB/BuildEnvironment >> | rpmdb: PANIC: fatal region error detected; run recovery >> | error: db4 error(-30974) from dbenv->close: DB_RUNRECOVERY: Fatal error, >> run database recovery >> >> The reason is that because in %pre and %post a few "rpm -q" operations >> are performed. Those seem to be still work fine as before, but at the >> end of the outer "rpm -U" operation RPM seems to detect the above >> problem now. Nothing seems to be actually broken afterwards, but the >> above errors make me feel bad and also confuse users. >> >> Two questions come up for me: >> >> 1. Why were no such errors in the past with 5.0.x and <= 5.1.[7-9] >> (approximately)? >> > > I have no clue - and but rpm-package-bundle - that do more that just > querying rpm inside an rpm - worked very well > in the near past http://rpm5.org/community/rpm-users/0262.html > Hmm, perhaps the issue is that rpm died while in middle of Berkeley DB call which is something that obviously should not happen and this is a situation which doesn't get automatically cleaned up, almost if something abnormal happen, Can you try - if it is important do a backup first :=) - a manual 'rm -f /var/lib/rpm/__*' and see if this solve the issue ? > > regards >> >> ______________________________________________________________________ >> RPM Package Manager http://rpm5.org >> Developer Communication List [email protected] >> > >
