[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
Thu Apr 11 23:06:32 UTC 2013


Note that .pyc files are not included in the packaging, they are
produced at install time, so they don't contribute to any checksums.
The .py files do, but these aren't what trigger the error message.

The reason for this is that at package build time, you don't know what
versions of Python may be installed on the target system, and .pyc files
are Python version specific.  IOW, a .pyc file built for Python 3.2 is
not guaranteed to work for 3.3.

AFAICT, what must have happened is that when a package was installed,
and its pyc file was being written, *something* caused the pyc file to
be truncated.  The question is what though?  Re-installing fixes the
problem because the .pyc files are re-built at that time.  Thus the
corruption went away.

If it's not a file system problem or a hardware problem, I'm not sure
what it could be.  Another thing to note is that Python does its best to
write a new .pyc file atomically, so I can't see how this could be a
race condition (e.g. one process trying to read a .pyc file while the
installation process is writing it).  Plus, if the write fails you won't
get a bogus .pyc file *and* you'd get an exception.

-- 
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:
  Triaged

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