Bug 30488
Summary: | upgrade fails while 'finding packages to update' | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Dana P. Cook <danacook> |
Component: | rpm | Assignee: | Brent Fox <bfox> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | jbj, teg |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-03-28 05:00:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dana P. Cook
2001-03-03 21:16:04 UTC
Please try wolverine, our more recent beta. retried with wolverine release and saw same results. The line number of the error moved to Line 551. Please look at VC3 and VC4 (cntl-alt-f3 and -f4) and see if you are getting read errors during the long pause. tried to view ctrl-alt-f3 and ctrl-alt-f4 durring pause and after the system panic. At no time did I see anything being appended to the system startup info that is there when the process begins. I browsed through the entries in these windows and did not see anything that looked abnormal. Are you able to type on VC2? If so, what does 'cat /proc/meminfo' say? How much swap space does your machine have? The 2.4 kernel needs more swap than the 2.2.x kernels did, so your system may be running out of swap. I was able to get memory stats in vc2. The machine has 256M memory and 256M swap partition. When I press "next" to start the upgrade I have about 140M of mem Free and swap has not been used. I dumped /proc/meminfo every 10 seconds or so and watched the FreeMemory drop at a rate of a few meg/minute. My last dump before it dies showed 118M free and swap still not touched... Here is what the lasts memstats screen said : MemTotal : 255768 MemFree : 118312 MemShared : 0 Buffers : 4932 Cached : 73944 Active : 43584 Inact_drty : 35292 Inact_clean : 0 Inact_target : 160 SwapTotal : 265032 SwapAvailable : 265032 Trond, is this a duplicate of your bug? No, no system panic or other bug messages on my problem . If you just boot the machine without the installer, does the installed system run correctly after the failed upgrades? We have seen some problems with upgrading in house in that the machines will sometimes hang during the upgrade, but it's usually at the very end of the install...and we haven't seen a system return to console mode and shut down...the GUI just gets frozen and doesn't do anything. I'm sorry, but I don't really know what you are asking here. What do you mean "without the installer" and "installed system"? When I have attempted an install and it fails, the computer I am attempting to upgrade has not been touched. It continues to function as it did before attempting to upgrade it. I don't beleive that there have been any changes made to my existing system because the upgrade did not get far enough to actually upgrade any packages. If this doesn't cover what you are asking, please be more specific and I'll try again... Your answer covers what I was asking. I wanted to know if the system was working properly with 7.0, just to make sure we are starting from a 'known good' state and it appears that we are. When the system crashes, exactly what appears on the screen? Is it a python traceback? In your original report, you said that the message: 'python:header.c:496:headerLoad:Assertion `rdlen == dl` failed' appears. I'm a little confused because I can't find any file named 'header.c' in the installer. When the crash happens It looks like I get returned to a VC. It prints the python error and then a short series of kernel shutdown messages. The python error I listed above is verbatum of what is on the screen. Please note however that on a followup ( testing with wolverine instead of fisher ) the error line is 551. Can you attach a copy of your package db? That would be helpful. Adding jbj to the list...the problem could stem from a problem with the rpm package db. I'd be happy to. What filename/path would that be? Just do cd /var/lib tar czvf /tmp/rpmdb.tar.gz rpm and mail me <jbj> rpmdb.tar.gz. Thanks. I just upgraded my redhat7.0 system to use the following updates : rpm-4.0.2-7x.i386.rpm rpm-devel-4.0.2-7x.i386.rpm rpm-build-4.0.2-7x.i386.rpm rpm-python-4.0.2-7x.i386.rpm I now get the same error message I reported above when I do a "rpm -qa" command. Here is the error : rpmq: header.c:511: headerLoad: Assertion `rdlen == dl' failed. Thought this might help you diagnose since it seems related... If this is appearing outside the context of the installer, I'm inclined to think the problem is somewhere in rpm. Changing component to rpm. If I am wrong here, please reassign it back to anaconda. Your Packages hash is damaged, verify by doing (you will need db3-utils installed): bash$ cd /var/lib/rpm bash$ db_verify Packages db_verify: Overflow page 3085 has bogus prev_pgno value db_verify: Overflow item incomplete on page 3090 db_verify: DB->verify: Packages: DB_VERIFY_BAD: Database verification failed That can be "fixed" by doing bash$ cd /var/lib/rpm bash$ mv Packages Packages-BUGGY bash$ db_dump Packages-BUGGY | db_load Packages However the problem persists, verify using "rpm -qa". But "db_verify Packages" is happy. So, the assumption is that this is (known) file system corruption running kernel-2.4.2 on IDE. The last set of operations you described behaves exactly as you predicted. Closing the bug since the rpm database was corrupt to begin with. |