[Bug 1668639] [NEW] Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[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

** Affects: rsyslog (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: rsyslog (Ubuntu Trusty)
     Importance: Undecided
         Status: New

** Affects: rsyslog (Ubuntu Xenial)
     Importance: Undecided
         Status: New

** Affects: rsyslog (Ubuntu Yakkety)
     Importance: Undecided
         Status: New


** Tags: patch sts sts-sponsor
-- 
Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d
https://bugs.launchpad.net/bugs/1668639
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.