[Bug 1096531] Re: After touch /forcefsck and reboot: Assertion failed in log_clear_unflushed

[James Hunt]

Investigation shows that this problem is only triggered by '/forcefsck':
the actual problem results from jobs that satisfy both conditions below:

- *end* before /var/log/upstart/ becomes writeable.
- has spawned one or more processes that continue to run *after* the job has finished and after /var/log/upstart/
  has become writeable.

Problem is more reliably recreatable if a job such as the following is created:
____________________

start on startup
    # spawn a process quickly that allows the job itself to end fast,
    # but which also produces output after the job has finished.
    /bin/sh -c 'while :; do cat /etc/fstab; done' &
script

end script
____________________

On my test server system, the standard job that triggered the problem
was network-interface: it calls ifup which spawns off dhclient which is
still running after the network-interface instance job has finished.

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

Title:
  After touch /forcefsck and reboot: Assertion failed in
  log_clear_unflushed

Status in “upstart” package in Ubuntu:
  In Progress

Bug description:
  I made a copy of raring-server-cloudimg-amd64-disk1.img, launched in
  KVM on my 12.10 system, updated all the packages on it and then
  rebooted it after touching /forcefsck.  Even though its a clean
  reboot, it still core dumpes.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
  Uname: Linux 3.7.0-7-generic x86_64
  ApportVersion: 2.7-0ubuntu2
  Architecture: amd64
  Date: Sun Jan  6 06:39:07 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=screen
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1096531/+subscriptions