SCIENTIFIC-LINUX-USERS Archives

May 2012

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Frank Lanitz <[log in to unmask]>
Reply To:
Frank Lanitz <[log in to unmask]>
Date:
Thu, 10 May 2012 08:31:48 +0200
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (1639 bytes) , smime.p7s (4 kB)
Hi folks,

Did anyone of you see something like this before:

> ]# yum update
> Loaded plugins: kernel-module
> rpmdb: unable to join the environment
> error: db4 error(11) from dbenv->open: Resource temporarily unavailable
> error: cannot open Packages index using db3 - Resource temporarily unavailable (11)
> error: cannot open Packages database in /var/lib/rpm
> Traceback (most recent call last):
>   File "/usr/bin/yum", line 29, in ?
>     yummain.user_main(sys.argv[1:], exit_code=True)
>   File "/usr/share/yum-cli/yummain.py", line 309, in user_main
>     errcode = main(args)
>   File "/usr/share/yum-cli/yummain.py", line 157, in main
>     base.getOptionsConfig(args)
>   File "/usr/share/yum-cli/cli.py", line 187, in getOptionsConfig
>     self.conf
>   File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 665, in <lambda>
>     conf = property(fget=lambda self: self._getConfig(),
>   File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 240, in _getConfig
>     self._conf = config.readMainConfig(startupconf)
>   File "/usr/lib/python2.4/site-packages/yum/config.py", line 804, in readMainConfig
>     yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg)
>   File "/usr/lib/python2.4/site-packages/yum/config.py", line 877, in _getsysver
>     idx = ts.dbMatch('provides', distroverpkg)
> TypeError: rpmdb open failed

I already found out, that it seems that the pm-database is broken by
$reason. Unfortunately I cannot say, what the reasons are nor when it
did happen. However, also access rpm directly is ending up in an error
like this (besides the Python backtrace).

cheers,
Frank




ATOM RSS1 RSS2