[Bug 1578628] [NEW] Upstart log files are not reopened after rolling

[Pat McGowan]

Public bug reported:

Seen on stable and proposed vivid based touch images
I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all.
The config for upstart includes nocreate but this has always been this way.
Is this intended or did something change in logrotate?
A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening.

** Affects: canonical-devices-system-image
     Importance: Undecided
     Assignee: Thomas Voß (thomas-voss)
         Status: New

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

- Seen on stable and proposed
+ Seen on stable and proposed vivid based touch images
  I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all.
  The config for upstart includes nocreate but this has always been this way.
  Is this intended or did something change in logrotate?
  A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening.

** Also affects: upstart (Ubuntu)
   Importance: Undecided
       Status: New

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

Title:
  Upstart log files are not reopened after rolling

Status in Canonical System Image:
  New
Status in upstart package in Ubuntu:
  New

Bug description:
  Seen on stable and proposed vivid based touch images
  I noticed on two of my devices that after a scheduled rolling of the files in /var/log/upstart that there were no active *.log files at all.
  The config for upstart includes nocreate but this has always been this way.
  Is this intended or did something change in logrotate?
  A similar bug report states that the files will be opened on a subsequent write from the upstart process, but this is clearly not happening.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions