Ak je to RHEL6/Centos6, tak by to mohlo byt: Bug 1184613 - Periodic Corrupt RPM database (RPM out of memory, Duplicate RPM packages)
BZ je private, diskusia viedla k problemu s db4: https://community.oracle.com/message/13022444#13022444
2015-07-20 10:21 GMT+02:00 Petr Fišer priestcz@gmail.com:
Ahoj, Stalo se mi to jednou na CentOS6, ale bylo to po updatu yum a rpm. Pripisoval jsem to tomu, rebuildnul db a dal to neresil. Od te doby ok. Mozna ti pomuzou verze balicku, ten update byl u me na verze:
Transaction performed with: Installed rpm-4.8.0-38.el6_6.x86_64 @updates Installed yum-3.2.29-60.el6.centos.noarch @base Installed yum-metadata-parser-1.1.2-16.el6.x86_64 installed Installed yum-plugin-fastestmirror-1.1.30-30.el6.noarch @base
Fiisch
Dne 17. července 2015 13:58 Ondrej Mikle ondrej.mikle@gmail.com napsal(a):
Ahoj,
zacala se mi na VPS opetovne rozbijet rpmdb. Projevuje se to napriklad
tak,
ze autoupdater neupdatuje a pri manualnim updatu to vyplivne:
# yum update rpmdb: Thread/process 8471/139911281358592 failed: Thread died in
Berkeley
DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal
error,
run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open Packages database in /var/lib/rpm CRITICAL:yum.main:
Error: rpmdb open failed
Vechny nalezene reseni funguji jen docasne (napr. smazani a rebuild
rpmdb).
Yum ani rpm se tento rok neupdatoval.
Vcera, kdyz jsem to debugoval, tak se rpmdb rozbila po kazdem druhem "yum history info", dnes to po smazani a rebuildu zas magicky drzi pohromade.
Nestalo se to nekomu jinymu, nebo netusite, cim by to mohlo byt
zpusobeny?
Napada me jedine filesystem corruption, ale nevim jak by to slo odladit.
OM
Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list
Community-list mailing list Community-list@lists.vpsfree.cz http://lists.vpsfree.cz/listinfo/community-list