Red Hat Bugzilla – Bug 159386
Up2date crashed and now it doesn't work anymore
Last modified: 2007-11-30 17:07:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1
Description of problem:
This is a normal workstation doing very important imports. It's regularly updated via up2date --nox --update. Suddenly, something went wrong and now it's broken, leaving a production system vunerable, since it can't be updated anymore. It's very important to get this working again!
[root@elo root]# up2date
Traceback (most recent call last):
File "/usr/sbin/up2date", line 1174, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date", line 668, in main
File "up2dateAuth.py", line 151, in updateLoginInfo
File "up2dateAuth.py", line 105, in login
File "up2dateAuth.py", line 49, in maybeUpdateVersion
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 228, in getVersion
release, version = getOSVersionAndRelease()
File "/usr/share/rhn/up2date_client/up2dateUtils.py", line 221, in getOSVersionAndRelease
up2date_client.up2dateErrors.RpmError: RPM error. The message was:
Could not determine what version of Red Hat Linux you are running.
If you get this error, try running
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Just run up2date
Actual Results: See Description. It just won't work anymore
Expected Results: To update the packages like it should. Now it doesn't do anything.
No, it's all in the description.
what happens after you run:
It runs, and then, when I run up2date again, I'll still see the same errors
(In reply to comment #1)
> what happens after you run:
> rpm --rebuilddb
It's a month later, our machine still can't do up2date without a clue of what's
wrong. This is important to us!
Could you please follow the instructions detailed at
I believe this will fix the corrupt database you are seeing, and resolve your issue.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.