Bug 64399 - ValueError: bad marshal data
Summary: ValueError: bad marshal data
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
(Show other bugs)
Version: 4.0
Hardware: All Linux
medium
high
Target Milestone: ---
: ---
Assignee: Adrian Likins
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-03 16:22 UTC by Isaiah Weiner
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-05-03 19:30:35 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Isaiah Weiner 2002-05-03 16:22:08 UTC
Description of problem:
With up2date-2.7.61-7.x.2 on one particular client all invocations of `up2date` 
yield a traceback with 'bad marshal data' during one of the imports.  What does 
this indicate as the likely problem and solution?  Google seems to indicate 
corrupted python modules; reinstall up2date client?

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


How reproducible:
Always

Steps to Reproduce:
1. up2date
	

Actual Results:  Traceback (innermost last):
  File "/usr/sbin/up2date", line 24, in ?
    from up2date_client import lilocfg
  File "/usr/share/rhn/up2date_client/lilocfg.py", line 14, in ?
    import lilo, iutil
  File "/usr/share/rhn/up2date_client/lilo.py", line 13, in ?
    import iutil
ValueError: bad marshal data

Additional info:

Comment 1 Adrian Likins 2002-05-03 18:23:31 UTC
hmm, could be. Whats `rpm -V up2date` show?

Have never seen that error before, and the iutil module hasnt
changed in months.

So corrupt files seems as likely as anything...

Comment 2 Isaiah Weiner 2002-05-03 19:30:31 UTC
rpm -ivh --force fixed it.  Didn't get rpm -V output before that, sorry.  Will
close.


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