I've confirmed with the original customer that this indeed *is* working
as expected. As such, I'm updating the status on both tasks to
'Invalid'.
** Changed in: rsyslog (Ubuntu)
Status: Incomplete => Invalid
** Changed in: snappy
Status: Incomplete => Invalid
--
You received
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
** Changed in: snappy
Status: New => Incomplete
--
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
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
@ogra If the component in question was removed and/or deprecated and no
longer used in the current development release, then the policy
shouldn't apply. In this case I don't think it would be much of a
stretch to get a waiver for this. That said, as I'm pretty sure this bug
is specific to Core, so
it is a hard requirement of the SRU process that fixes land in the devel
release and then propagate backwards through all other releases ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875493
@ogra This is a bug in the core[16] snap. I'm not sure why we'd even
consider SRU'ing to UC18 or UC20. On both of the those systems, core
wouldn't be the booting snap, so any fix would be a no-op.
Possible ways to fix include:
- releasing an rsyslog SRU for 16.04, but as Michael points out this
well, rsyslog is completely gone from core after UC16 ... how would you
test that in UC18 or UC20 to verify SRUs ?
--
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
Thanks for your bugreport.
What happens is that rsyslog:
- has a rsyslog.logrotate config file that has "postrotate"
/usr/lib/rsyslog/rsyslog-rotate
- the rsyslog-rotate has "systemctl kill -s HUP rsyslog.service" in it
It looks like neither rsyslog.logrotate nor rsyslog-rotate have changed
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
--
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
