Zypper Update

Hello, today when I tried to update my computer, this is what I get…

jonathan@linux-c8b3:~> sudo zypper update
root's password:
Loading repository data...
Reading installed packages...

The following packages are going to be upgraded:
  bind-utils compiz evolution-tracker gnutls libboost_date_time1_42_0 libboost_filesystem1_42_0 libboost_graph1_42_0 libboost_iostreams1_42_0 
  libboost_math1_42_0 libboost_mpi1_42_0 libboost_program_options1_42_0 libboost_python1_42_0 libboost_regex1_42_0 libboost_serialization1_42_0 
  libboost_signals1_42_0 libboost_system1_42_0 libboost_test1_42_0 libboost_thread1_42_0 libboost_wave1_42_0 libgnutls26 libgnutls-extra26 libpurple 
  libpurple-tcl libtracker-extract-0_8-0 libtracker-miner-0_8-0 nautilus-tracker nfs-client pidgin python-xml tracker tracker-gui 

31 packages to upgrade.
Overall download size: 7.4 MiB. After the operation, additional 222.0 KiB will be used.
Continue? [y/n/?] (y): y
Retrieving package python-xml-2.6.5-3.3.1.i586 (1/31), 174.0 KiB (825.0 KiB unpacked)
Retrieving delta: ./rpm/i586/python-xml-2.6.5-2.14_3.3.1.i586.delta.rpm, 13.0 KiB
Retrieving: python-xml-2.6.5-2.14_3.3.1.i586.delta.rpm [done (0 B/s)]
Applying delta: ./python-xml-2.6.5-2.14_3.3.1.i586.delta.rpm [done]
Installing: python-xml-2.6.5-3.3.1 [done]
Retrieving package bind-utils-9.7.1P2-0.4.1.i586 (2/31), 182.0 KiB (604.0 KiB unpacked)
Retrieving delta: ./rpm/i586/bind-utils-9.7.1P2-0.2.1_0.4.1.i586.delta.rpm, 18.0 KiB
Retrieving: bind-utils-9.7.1P2-0.2.1_0.4.1.i586.delta.rpm [done (0 B/s)]
Applying delta: ./bind-utils-9.7.1P2-0.2.1_0.4.1.i586.delta.rpm [done]
Installing: bind-utils-9.7.1P2-0.4.1 [error]
Installation of bind-utils-9.7.1P2-0.4.1 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: 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 '�
���)���6Hf!�edig into Filedigests
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 "S]�|��9��P,�J�edig" records from Filedigests 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 "Y��@]��+��1��r.edig" records from Filedigests 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 "y�lN"
                                    ��K�%p
edig" records from Filedigests 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 "F�<M�Z7 �r��}edig" records from Filedigests 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 "F�w>
                                  ���!����oWmedig" records from Filedigests index
rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery
n���b�edig" records from Filedigests 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 "D�ݦ,�m�����n��edig" records from Filedigests 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 "���{��'���wcedig" records from Filedigests 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 "S#֝






rpmdb: PANIC: fatal region error detected; run recovery
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recoveryecovery
rpmdb: PANIC: fatal region error detected; run recoveryds from Filedigests index
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoveryecovery
rpmdb: PANIC: fatal region error detected; run recoveryrds from Filedigests index
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoveryecovery
rpmdb: PANIC: fatal region error detected; run recoveryds from Filedigests index
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoveryecovery
rpmdb: PANIC: fatal region error detected; run recoveryrds from Filedigests index
error: db3 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoveryecovery
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 recoveryCOVERY: Fatal error, run database 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 recoverycovery
rpmdb: PANIC: fatal region error detected; run recoveryrds from Filedigests index
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoverycovery
rpmdb: PANIC: fatal region error detected; run recoveryds from Filedigests index
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoverycovery
rpmdb: PANIC: fatal region error detected; run recoverycords from Filedigests index
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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 recoverycovery
rpmdb: PANIC: fatal region error detected; run recoveryFiledigests index
error: db3 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
rpmdb: PANIC: fatal region error detected; run recoveryCOVERY: Fatal error, run database 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


Abort, retry, ignore? [a/r/i] (a): ^Cjonathan@linux-c8b3:~> 

If I press “Ignore”, it just shows all of this. Even if I try to update through YaSt, it still says the exact same thing.

Please Help! :’(

Open a terminal and this as su -

zypper clean --all
rpmdb --rebuilddb

try again

rebuild your database

rpm --rebuilddb

Thanks Guys!

Just wanted to know…What was this? What happened?

On 2010-12-11 00:36, Rabbitdog wrote:

> Just wanted to know…What was this? What happened?

The rpm is corrupt, as it says in the message you posted, and has to be
rebuilt, as it says in that message. You just have to read the text the
program printed and which you posted :slight_smile:

|> Error: Subprocess failed. Error: RPM failed: 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

See? “run database recovery”.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)

I just had the same thing happen on a 64-bit 12.1 install. The zypper line needs to be executed twice.

zypper clean --all
zypper clean --all
rpmdb --rebuilddb