I just updated the status to Incomplete for both bug tasks, as I may have been too confident in the original bug description given to me by the customer.
The logrotate script as written is not meant to "restart" rsyslogd. Looking at the man page, the HUP signal (as sent by the /usr/lib/rsyslog /rsyslog-rotate script on postrotate) is meant to trigger rsyslogd to close all open files. My testing shows that this does seem to be working OK on both 16.04 classic and Core 16. I suspect that the problem may be due the way the customer is integrating with rsyslogd, and that this in turn might be why rsyslogd is holding on to the deleted files. I'm going to leave this bug open until we can determine the actual root cause, because as mentioned in the bug description, this can lead to a device running out of storage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875493 Title: [core] log rotation doesn't properly restart rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1875493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
