This bug was fixed in the package rsyslog - 8.16.0-1ubuntu7

rsyslog (8.16.0-1ubuntu7) artful; urgency=medium

  * Cherry pick restart on configuration changes fix from Debian (LP: #1668639)
    - Trigger restart on configuration changes.
      Register a dpkg trigger on /etc/rsyslog.d that calls restart on
      configuration changes. (Closes: #791337)
    - Update dpkg trigger to use try-restart.
      Add try-restart action to SysV initscript for that, systemd supports
      this natively.
    - debian/control: Add Depends on init-system-helpers (>= 1.47~) to rsyslog.

 -- Frode Nordahl <>  Mon, 26 Jun 2017
06:29:30 +0000

** Changed in: rsyslog (Ubuntu Artful)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs

  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:
Status in rsyslog source package in Xenial:
Status in rsyslog source package in Yakkety:
Status in rsyslog source package in Zesty:
Status in rsyslog source package in Artful:
  Fix Released
Status in rsyslog package in Debian:
  Fix Released

Bug description:
  Servers or cloud instances will not log important messages after initial 
deployment. Manual reboot or restart of services is necessary to get expected 

  [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 
  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]

  This patch merges a patch from Debian where a trigger is added to the
  rsyslog package that fires when other debs drop files into

  [Original Bug Description]
  rsyslog should reload its configuration when other packages drop 
configuration in /etc/rsyslog.d

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to