** Changed in: rsyslog (Debian)
Status: Unknown => Fix Released
--
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:
New
Status in rsyslog source package in Trusty:
New
Status in rsyslog source package in Xenial:
New
Status in rsyslog source package in Yakkety:
New
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 : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
