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

[Steve Langasek]

So apparently I was quite badly mistaken; not only does upstart
integrate with logrotate, I seem to have added the support for that to
the package myself.

Anyway, yes, we don't want upstart to still be logging to deleted files;
so either upstart needs to detect that the file has been moved/deleted
and reopen its log (which rings a bell with me - maybe this is how it's
supposed to work), or it needs to be sent a signal by the logrotate rule
telling it to reopen the logs on a per-service basis.

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