Bug 64399 – ValueError: bad marshal data

Bug 64399 - ValueError: bad marshal data

Summary:	ValueError: bad marshal data

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	up2date (Show other bugs)
Sub Component:
Version:	4.0
Hardware:	All Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-05-03 12:22 EDT by Isaiah Weiner
Modified:	2007-11-30 17:07 EST (History)
CC List:	5 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Isaiah Weiner 2002-05-03 12:22:08 EDT

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 14:23:31 EDT

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 15:30:31 EDT

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.