It is fixed in Ubuntu Bionic and late but this LP bug have never been
mentioned in the changelog, which explains why the status didn't change
until now (after a manual status change from my part)
Xenial hasn't been fix, I did some quick verification and base on the
fix, which add a Depends as follow:
debian/control: init-system-helpers (>= 1.47~)
and considering rmadison:
init-system-helpers | 1.29ubuntu1 | xenial | source, all
init-system-helpers | 1.29ubuntu4 | xenial-updates | source, all
I'm afraid the fix won't work for Xenial.
With that being said, I will set Xenial to "Won't fix".
Please feel free to re-open it if you judge Xenial need the fix by
providing good justification/rational.
- Eric
** Changed in: rsyslog (Ubuntu Zesty)
Status: Won't Fix => Fix Released
** Changed in: rsyslog (Ubuntu Xenial)
Status: In Progress => Fix Released
** Changed in: rsyslog (Ubuntu Xenial)
Status: Fix Released => Won't Fix
** Changed in: rsyslog (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1668639
Title:
Add a trigger to reload rsyslog when a new configuration file is
dropped in /etc/rsyslog.d
Status in rsyslog package in Ubuntu:
Fix Released
Status in rsyslog source package in Trusty:
Won't Fix
Status in rsyslog source package in Xenial:
Won't Fix
Status in rsyslog source package in Zesty:
Fix Released
Status in rsyslog source package in Artful:
Fix Released
Status in rsyslog package in Debian:
Fix Released
Bug description:
[Impact]
Servers or cloud instances will not log important messages after initial
deployment. Manual reboot or restart of services is necessary to get expected
behaviour.
[Test Case]
1) Install, enable and start haproxy
2) Observe that /etc/rsyslog.d/49-haproxy.conf is installed
3) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log is NOT
created
4) Restart rsyslog service
5) Observe that /var/lib/haproxy/dev/log and /var/log/haproxy.log IS created
6) Restart haproxy service and observe that log now is filled with entries
With the patched deb steps 3,4 and 6 becomes irrelevant and everything
works out of the box.
[Regression Potential]
Minimal.
This patch merges a patch from Debian where a trigger is added to the
rsyslog package that fires when other debs drop files into
/etc/rsyslog.d.
[Original Bug Description]
rsyslog should reload its configuration when other packages drop
configuration in /etc/rsyslog.d
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337
https://anonscm.debian.org/cgit/collab-
maint/rsyslog.git/commit/?id=8d4074003f8fb19dae07c59dd19f0540a639210f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+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
