Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 159386 - Up2date crashed and now it doesn't work anymore
Summary: Up2date crashed and now it doesn't work anymore
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: up2date
Version: 3.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Fanny Augustin
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-02 09:24 UTC by Bas van Schooten
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-10-19 19:01:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Bas van Schooten 2005-06-02 09:24:13 UTC
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 "", line 151, in updateLoginInfo
  File "", line 105, in login
  File "", line 49, in maybeUpdateVersion
  File "/usr/share/rhn/up2date_client/", line 228, in getVersion
    release, version = getOSVersionAndRelease()
  File "/usr/share/rhn/up2date_client/", line 221, in getOSVersionAndRelease
    raise up2dateErrors.RpmError(
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 

                rpm --rebuilddb

Version-Release number of selected component (if applicable):

How reproducible:

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. 

Additional info:

No, it's all in the description.

Comment 1 Adrian Likins 2005-06-06 18:27:27 UTC
what happens after you run:

       rpm --rebuilddb

Comment 2 Bas van Schooten 2005-06-07 13:35:37 UTC
It runs, and then, when I run up2date again, I'll still see the same errors

Comment 3 Bas van Schooten 2005-08-02 11:51:03 UTC
(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! 

Comment 4 Jon Fautley 2005-09-12 13:47:25 UTC
Dear Sir,

Could you please follow the instructions detailed at

I believe this will fix the corrupt database you are seeing, and resolve your issue.

Best Regards,


Comment 5 RHEL Product and Program Management 2007-10-19 19:01:10 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.