Red Hat Bugzilla – Bug 75985
up2date crashed when run
Last modified: 2015-01-07 19:01:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
Get error message when running up2date
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run up2date
Actual Results: error: unrecognized db option: "tmpdir" ignored
error: cannot open Packages index using db3 - Invalid argument (22)
Traceback (innermost last):
File "/usr/sbin/up2date", line 17, in ?
from up2date_client import rpcServer
File "/usr/share/rhn/up2date_client/rpcServer.py", line 8, in ?
File "/usr/share/rhn/up2date_client/up2dateAuth.py", line 4, in ?
File "/usr/share/rhn/up2date_client/rpmSource.py", line 11, in ?
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 15, in ?
File "/usr/share/rhn/up2date_client/rpmUtils.py", line 274, in ?
rpm_version = getRpmVersion()
File "/usr/share/rhn/up2date_client/rpmUtils.py", line 265, in getRpmVersion
db = openrpmdb()
File "/usr/share/rhn/up2date_client/rpmUtils.py", line 52, in openrpmdb
raise up2dateErrors.RpmError(_("Could not open RPM database for reading.
Perhaps it is already in use?"))
up2date_client.up2dateErrors.RpmError: RPM error. The message was:
Could not open RPM database for reading. Perhaps it is already in use?
Expected Results: Up2date client should have run
is there a rpm process running somewhere that would hold
the rpm database open?
Shouldnt traceback of course, taking a look at that...
There are no rpm Processes running that would hold the rpm database open
Can you try:
Was this install a upgrade from a previous release (6.2?)
Also, it could be a permssions problem if ran as non-root.
up2date is supposed to detect this case and handle it (
and does so correctly as far as I know) but the rpm maintainer
suggested it as possible reason the rpm db would fail to
Shouldnt be an issue with currently supported releases.