[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
** Changed in: canonical-devices-system-image Milestone: 12 => backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
Yes, but both sets are in the same state, I originally noticed and reported against the system logs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
note that ~/.cache/upstart is not /var/log/upstart :) so we are looking at session logs here ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
Once there is activity on the system after a reboot I do see some logs being opened but not for all processes. But prior to the reboot, I was using the tablet and no logs were open for example http://pastebin.ubuntu.com/17177401/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
well, if there are actual writes the files should be re-created ... are they also not created newly after a reboot ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
This is making it difficult to debug in some cases ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: backlog => 12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Confirmed 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578628] Re: Upstart log files are not reopened after rolling
** Description changed: 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. + + See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation + and perhaps bug #1350782 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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. See http://askubuntu.com/questions/481236/upstart-not-reopening-log-files-on-logrotation and perhaps bug #1350782 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1578628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
