[Bug 1130611] Re: Upstart never closes /var/log/upstart/mysql.log

[TJ]

I suspect I've just hit this issue while working within a chroot.

After a suspend/resume cycle the external device hosting the file-
systems mounted in the chroot are generating kernel read errors.

One file-system could not be umount-ed because a file was in use:

$ sudo ls -l /proc/1/fd/ | grep target
l-wx------ 1 root root 64 Feb 10 14:42 13 -> /target/var/log/upstart/ureadahead-other.log

The job was stopped but the file remained open:

$ initctl status ureadahead-other
ureadahead-other start/killed, process 803

$ ps -efly | grep 803
S tj        1058  2828  0  80   0   940  2361 pipe_w 15:59 pts/4    00:00:00 grep --color=auto 803

$ sudo initctl start
## hangs indefinitely and needs Ctrl+C to exit

-- 
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/1130611

Title:
  Upstart never closes /var/log/upstart/mysql.log

Status in “upstart” package in Ubuntu:
  New

Bug description:
  I ran "init u" after noticing a lingering FD to a log file that lsof
  showed as "(deleted)". However because the file handle is never
  closed, and the log files get logrotate'd it keeps happening, like so:

  init      1 root   11w   REG              252,0     3532  394558
  /var/log/upstart/mysql.log.1 (deleted)

  It's possible this might be fixed by a version update, as I noticed
  there were closed bugs relating to "leaked" file descriptors?

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