Description of problem: Went to install yum updates and got a pirut component dump error. I saved it to the file pirutdump. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can yopu attach that? Or at least the last few lines should make it obvious what has happened.
Created attachment 323352 [details] Trace produced when entered root password after clicking on update available notifier box I got this crash this morning while trying to apply a routine RedHat update to my EL 5.2 SMP x86_64 system. It appears to fit this existing bug report. This process has always worked routinely until today. The attachment was generated by the system with a request to file it at bugzilla, so here it is. I also have a core file which I will save and will provide upon request. Due to its large size, it may be necessary for you to acquire it from me via our University large file server--I will send instructions and a password on request--but please provide an email where these instructions should be sent, as it is a scripted process that I cannot modify. George Reeke Rockefeller University
Sorry, I do not have a core dump file--the one mentioned in Comment #2 was from some other program. Please disregard that part of my comment. George Reeke Rockefeller University
The error is: TypeError: Parsing primary.xml error: Extra content at the end of the document ...can you show the data that's at the end of /var/cache/yum/*/primary.xml.gz ... also can you show what repos you have available (yum repolist)?
Created attachment 323372 [details] Requested ending of primary.xml.gz file You did not say how much of primary.xml.gz you would like to see--I arbitrarily sent last 1000 lines. The output of the command 'yum repolist' is as follows: Loading "rhnplugin" plugin repo id repo name status rhel-x86_64-server-5 None enabled George Reeke
With today's (Nov. 13, 2008) RedHat updates, it "just worked". I didn't change anything except installed new 2.6.18-92.1.18.el5 kernel yesterday (when the pup notifier failed, I did a "yum update" and the update worked normally). So maybe that kernel change fixed it, but that seems unlikely. I will enter another comment if this fails again. Sorry I can no longer reproduce this issue for you. George Reeke
*** This bug has been marked as a duplicate of bug 452538 ***