unattended-upgrade-shutdown crashed with IOError in _open(): [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-shutdown.log'

Bug #1013363 reported by AO
50
This bug affects 11 people
Affects Status Importance Assigned to Milestone
unattended-upgrades (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

On a freshly installed daily live Quantal 64 14th June fully updated

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unattended-upgrades 0.77
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
Uname: Linux 3.4.0-5-generic x86_64
ApportVersion: 2.2.2-0ubuntu2
Architecture: amd64
Date: Thu Jun 14 15:38:14 2012
ExecutablePath: /usr/share/unattended-upgrades/unattended-upgrade-shutdown
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/share/unattended-upgrades/unattended-upgrade-shutdown
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
PythonArgs: ['/usr/share/unattended-upgrades/unattended-upgrade-shutdown']
SourcePackage: unattended-upgrades
Title: unattended-upgrade-shutdown crashed with IOError in _open(): [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-shutdown.log'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
AO (aofrl10n) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Scott Moser (smoser) wrote :

This is easily recreated on an EC2 image (likely elsewhere), the user just needs to do:
  sudo service unattended-upgrades start
  sudo service unattended-upgrades stop

Changed in unattended-upgrades (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Scott Moser (smoser)
visibility: private → public
Revision history for this message
PeterPall (peterpall) wrote :

To me it seems like the real problem is that the directory the file is supposed to be in isn't created if it is missing

sudo mkdir /var/log/unattended-upgrades

should fix the problem. Can anyone confirm that?

Revision history for this message
Michele Olivo (micheleolivo) wrote :

Probably i have this problem because my var/log is in ram, because i have an SSD.

Revision history for this message
AO (aofrl10n) wrote :

As Michele Olivo mentions I too use tmpfs for var/log, so there might be something there. Still this should not happen.

Revision history for this message
col reilly (lupinehorror) wrote :

i too use tmpfs as i have an ssd. seems like that's the problem

Revision history for this message
Nate (n2cubed) wrote :

Yep, same for me. I have SSD and use tmpfs for var/log.

Revision history for this message
AO (aofrl10n) wrote :

I temporarily palliated by adding the following line to my fstab, seems to have fixed it for now:
tmpfs /var/log/unattended-upgrades tmpfs defaults,noatime 0 0

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

I am using an SSD with /var/log mounted in tmpfs as well.

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

Still happens in beta1 as of today.

Revision history for this message
Rainer Rohde (rainer-rohde) wrote :

This happens just now again when first logging in for the day.

Revision history for this message
richud (richud.com) wrote :

am using ssd with tmpfs, I am sure this occured several versions ago and was fixed, it seems to have reappeared.

Michael Vogt (mvo)
Changed in unattended-upgrades (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unattended-upgrades - 0.79.3ubuntu3

---------------
unattended-upgrades (0.79.3ubuntu3) quantal; urgency=low

  * lp:~mvo/unattended-upgrades/lp1061498:
    - fix crash in dpkg_conffile_prompt() (LP: #1061498)
  * lp:~mvo/unattended-upgrades/create-logdir-in-shutdown-helper-lp1013363:
    - create logdir in the shutdown helper if needed (LP: #1013363)
 -- Michael Vogt <email address hidden> Fri, 05 Oct 2012 17:57:38 +0200

Changed in unattended-upgrades (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.