Bug 64399
| Summary: | ValueError: bad marshal data | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Isaiah Weiner <iweiner> |
| Component: | up2date | Assignee: | Adrian Likins <alikins> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | cturner, gafton, mihai.ibanescu, pjones, taw |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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: | --- | Target Upstream Version: | |
| Embargoed: | |||
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... rpm -ivh --force fixed it. Didn't get rpm -V output before that, sorry. Will close. |
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: