Hi, Yesterday i installed FC6 from rawhide repository. I did not played with any rpm command or with rpm database but today when I then tried to install rpmlint package i got yum install rpmlint Loading "installonlyn" plugin Setting up Install Process Setting up repositories extras-development 100% |=========================| 1.1 kB 00:00 pnq-rawhide 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for rpmlint to pack into transaction set. rpmlint-0.78-1.fc6.noarch 100% |=========================| 19 kB 00:00 ---> Package rpmlint.noarch 0:0.78-1.fc6 set to be updated --> Running transaction check
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Installing: rpmlint noarch 0.78-1.fc6 extras-development 167 k
Transaction Summary ============================================================================= Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s)
Total download size: 167 k Is this ok [y/N]: y Downloading Packages: (1/1): rpmlint-0.78-1.fc6 100% |=========================| 167 kB 00:01 Running Transaction Test /etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /media/.hal-.*. Finished Transaction Test Transaction Test Succeeded Running Transaction /etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /media/.hal-.*. Installing: rpmlint ######################### [1/1] rpmdb: PANIC: Invalid argument rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) storing record Config.pyo into Basenames rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ConfigCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ConfigCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ConfigCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DistributionCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DistributionCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DistributionCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DocFilesCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DocFilesCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "DocFilesCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FHSCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FHSCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FHSCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FilesCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FilesCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "FilesCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Filter.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Filter.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Filter.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "I18NCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "I18NCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "I18NCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "InitScriptCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "InitScriptCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "InitScriptCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "LSBCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "LSBCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "LSBCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuXDGCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuXDGCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "MenuXDGCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "NamingPolicyCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "NamingPolicyCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "NamingPolicyCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PamCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PamCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PamCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Pkg.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Pkg.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Pkg.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PostCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PostCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "PostCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "RpmFileCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "RpmFileCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "RpmFileCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SignatureCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SignatureCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SignatureCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SourceCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SourceCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SourceCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SpecCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SpecCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "SpecCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "TagsCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "TagsCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "TagsCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Testing.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Testing.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "Testing.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ZipCheck.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ZipCheck.pyc" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "ZipCheck.pyo" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "config" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30977) getting "rpmlint.py" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Group index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Requirename index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 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: db4 error(-30977) from db->open: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Filemd5s index using db3 - (-30977) rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run database recovery
Installed: rpmlint.noarch 0:0.78-1.fc6 Complete! rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command rpm -ivh kernel-xen-devel-2.6.18-1.2747.fc6.i686.rpm whats that mean? how to recover rpm database? regards, Parag.
On Tue, 2006-10-10 at 10:17 +0530, Parag N(पराग़) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command
On my Dual Core laptop I see those problems a _lot_, almost every second time I do an update. I would be interested to hear if you are using an dual core or SMP machine?
I always could fix it by removing the /var/lib/rpm/__* files and than run rpm --rebuilddb
- Erwin
hi, On 10/10/06, Erwin Rol mailinglists@erwinrol.com wrote:
On Tue, 2006-10-10 at 10:17 +0530, Parag N(पराग़) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command
On my Dual Core laptop I see those problems a _lot_, almost every second time I do an update. I would be interested to hear if you are using an dual core or SMP machine?
I always could fix it by removing the /var/lib/rpm/__* files and than run rpm --rebuilddb
looks like i have done that already. Nope i am not using any dual core nor any SMP machine. but still i am facing same errors with any rpm -ivh foo.rpm command
regards, Parag.
Erwin Rol mailinglists@erwinrol.com wrote:
On Tue, 2006-10-10 at 10:17 +0530, Parag N(परा〓) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command
On my Dual Core laptop I see those problems a _lot_, almost every second time I do an update. I would be interested to hear if you are using an dual core or SMP machine?
I've got both a dual-core i686 notebook and a dual-core x86_64 desktop, and I've /never/ seen anything like this... The following are the things I check first when seeing aberrant behaviour:
Have you checked the hardware (memtest, overheating due to bad fan, ...)?
Bad electric power (yes, some machines here used to go crazy due to voltage fluctuations)? Bad/undersized power supply?
Have you checked the relevant packages (at least yum, rpm, glibc, fileutils, etc; "rpm -q --requires ..." should point you in the right direction)? "rpm -V ..." is your friend.
/var (or other filesystems) filled up? (Yes, rpm (at least used to) go nuts and spew strange messages)
Anybody frobbing disk parameters "for performance"?! That leads to (regrettably mostly silent) filesystem corruption... Overclocking?
On Tue, 2006-10-10 at 16:18 -0400, Horst H. von Brand wrote:
Erwin Rol mailinglists@erwinrol.com wrote:
I've got both a dual-core i686 notebook and a dual-core x86_64 desktop, and I've /never/ seen anything like this... The following are the things I check first when seeing aberrant behaviour:
I have never seen the error on my x86_64 AMD single cpu/core machine, but a lot on my Dell Latitude D620.
Have you checked the hardware (memtest, overheating due to bad fan, ...)?
Never seen any other error ever, and i do a lot of C++ compiling on the machine, which most of the time will trigger memory and heat related errors.
Bad electric power (yes, some machines here used to go crazy due to voltage fluctuations)? Bad/undersized power supply?
Unlikely since its a laptop and not a desktop. (and No it does not have a Sony battery ;-)
Have you checked the relevant packages (at least yum, rpm, glibc, fileutils, etc; "rpm -q --requires ..." should point you in the right direction)? "rpm -V ..." is your friend.
All the latest rawhide versions.
/var (or other filesystems) filled up? (Yes, rpm (at least used to) go nuts and spew strange messages)
Nope lots of Gigs space left.
Anybody frobbing disk parameters "for performance"?! That leads to (regrettably mostly silent) filesystem corruption... Overclocking?
Have not "tuned" anything, certainly not any overclocking.
I always had the felling it was a deadlock of some kind that caused the problem. It seemed that /etc/cron.daily/rpm would hang, and that causing a yum update to get a corrupted rpm DB.
Maybe its just a messed up rawhide install I will do a complete clean install when FC6 is ready and see if the problem goes away.
- Erwin
On Tue, 2006-10-10 at 09:49 +0200, Erwin Rol wrote:
On Tue, 2006-10-10 at 10:17 +0530, Parag N(पराग़) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command
On my Dual Core laptop I see those problems a _lot_, almost every second time I do an update. I would be interested to hear if you are using an dual core or SMP machine?
I always could fix it by removing the /var/lib/rpm/__* files and than run rpm --rebuilddb
I can't believe your timing. I just slammed smack into this when I ran an update this morning. I was within minutes of rebuilding the whole system from scratch (it is just a test system anyways) when I read your message. That worked. Saved me a couple of hours rebuild.
Point on the curve - I noticed a hung rpmq process running this morning. Not sure if it was a cause of the problem or an effect of the problem.
Yes - This was on an SMP machine. I had never run into that before. Could not --rebuilddb or --initdb or anything until I removed those __* files. Then --rebuilddb recovered the system. Many thanks!
- Erwin
Mike
I can't believe your timing. I just slammed smack into this when I ran an update this morning.
Me too. This morning's update was greeted by lots of lovely dbfail messages. Is anyone looking into the root cause of this? My machine is x86_64.
-Steve
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Tue, 10 Oct 2006, [UTF-8] Parag N(पराà¥^Z) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command rpm -ivh kernel-xen-devel-2.6.18-1.2747.fc6.i686.rpm whats that mean? how to recover rpm database?
You can try rpm --rebuilddb also cd /var/lib/rpm; /usr/lib/rpm/rpmdb_recover
Michael Young
hi, On 10/10/06, M A Young m.a.young@durham.ac.uk wrote:
On Tue, 10 Oct 2006, [UTF-8] Parag N(鄐芹什鄐擒匆Z) wrote:
rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run database recovery
I even removed all /var/lib/rpm/__* files and tried to install any rpm but same errors i got when i executed following command rpm -ivh kernel-xen-devel-2.6.18-1.2747.fc6.i686.rpm whats that mean? how to recover rpm database?
You can try rpm --rebuilddb also cd /var/lib/rpm; /usr/lib/rpm/rpmdb_recover
did above but same kinds of errors when i tried rpm -ivh foo.rpm
Regards, Parag.
-
Erwin Rol -
Horst H. von Brand -
M A Young -
Michael H. Warfield -
Parag Nemade -
Steve G