[Bug 1058884] Re: do-release-upgrade crashed with EOFError in /usr/lib/ubuntu-release-upgrader/check-new-release: EOF read where not expected

Barry Warsaw 1058884 at bugs.launchpad.net
Wed Apr 10 18:30:47 UTC 2013


This message comes from Python's built-in 'marshal' module, and it
happens when EOF occurs unexpectedly while unmarshalling a string
object.  Marshal is the technology that underlies .pyc files, so this is
only going to happen if you have corrupt .pyc files.

I have no idea what could be causing your .pyc files to be corrupted,
but it's unlikely to be a problem in Python or do-release-upgrade.
Perhaps you have a bad disk or some other hardware problem, or perhaps
you're running on a weird or corrupted file system.  E.g. problems with
an encrypted disk or RAID could cause this.  It's possible that a full
file system at the time of package installation or upgrade could also
cause such problems.

There's probably nothing we can do about it except to recommend that you
re-install the affected packages.  This will cause Python to re-byte
compile the py files into new pyc files, hopefully fixing the
corruption.

I'm going to mark this as Incomplete, but if you find a way to reliably
reproduce this, and can discount hardware or filesystem problems, feel
free to re-open it.  If you can identify a corrupt .pyc file, please
attach it - it would be interesting to pick that apart.

** Changed in: ubuntu-release-upgrader (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1058884

Title:
  do-release-upgrade crashed with EOFError in /usr/lib/ubuntu-release-
  upgrader/check-new-release: EOF read where not expected

Status in “ubuntu-release-upgrader” package in Ubuntu:
  Incomplete

Bug description:
  yeay for automatic bug reporting!

  this is happening pretty regular, I have no idea what's triggering it,
  a cron job maybe?

  if I run it manually, it get:

  ~$ sudo do-release-upgrade 
  Traceback (most recent call last):
    File "/usr/bin/do-release-upgrade", line 8, in <module>
      from DistUpgrade.DistUpgradeVersion import VERSION
  EOFError: EOF read where not expected

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: ubuntu-release-upgrader-core 1:0.181
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 29 15:11:46 2012
  ExecutablePath: /usr/bin/do-release-upgrade
  InterpreterPath: /usr/bin/python3.2mu
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/check-new-release -q
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  PythonArgs: ['/usr/lib/ubuntu-release-upgrader/check-new-release', '-q']
  SourcePackage: ubuntu-release-upgrader
  Title: do-release-upgrade crashed with EOFError in /usr/lib/ubuntu-release-upgrader/check-new-release: EOF read where not expected
  Traceback:
   Traceback (most recent call last):
     File "/usr/lib/ubuntu-release-upgrader/check-new-release", line 8, in <module>
       from DistUpgrade.DistUpgradeVersion import VERSION
   EOFError: EOF read where not expected
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 1: cat: /var/log/dist-upgrade/apt-clone_system_state.tar.gz: No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1058884/+subscriptions




More information about the foundations-bugs mailing list