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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1096531
Title:
After touch /forcefsck and reboot: Assertion failed in
log_clear_unflushed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1096531/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
