|
Bugzilla – Full Text Bug Listing |
| Summary: | rpmdb PANIC | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Bakos Ludvig <ludvigbakos> |
| Component: | YaST2 | Assignee: | Michael Schröder <mls> |
| Status: | VERIFIED INVALID | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Critical | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Bakos Ludvig
2011-03-29 21:41:37 UTC
Please run 'rpm --rebuilddb', after that package management should work again. (It's not really a rpm problem, but some problem in the berkeley db implementation.) Please reopen if you still have problems after the database is rebuilt. (In reply to comment #0) > Yast was not able to install it the fresh packages! > > --------------------------------------------------- > > > Subprocess failed. Error: RPM sikertelen: rpmdb: PANIC: Invalid argument > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) storing record libc.so.6(GLIBC_2.2) into Requirename > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libc.so.6(GLIBC_2.3.4)" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libc.so.6(GLIBC_2.4)" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libgdk-x11-2.0.so.0" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libgdk_pixbuf-2.0.so.0" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libglib-2.0.so.0" records from Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libgobject-2.0.so.0" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libgtk-x11-2.0.so.0" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "liblcms.so.1" records from Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libm.so.6" records from Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libm.so.6(GLIBC_2.0)" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libm.so.6(GLIBC_2.1)" records from Requirename > index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libpango-1.0.so.0" records from Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libpthread.so.0" records from Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run > database recovery > error: error(-30977) getting "libpthread.so.0(GLIBC_2.0)" records from > Requirename index > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Providename index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Dirnames index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Requireversion index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Provideversion index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Installtid index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Sigmd5 index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Sha1header index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > error: cannot open Filedigests index using db3 - (-30977) > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run > database recovery > rpmdb: PANIC: fatal region error detected; run recovery > error: db3 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run > database recovery (In reply to comment #1) > Please run 'rpm --rebuilddb', after that package management should work again. > (It's not really a rpm problem, but some problem in the berkeley db > implementation.) > Please reopen if you still have problems after the database is rebuilt. Thank you! Now already it's okay! |