[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

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)

Trusty and Xenial hasn't been fix, I did some quick verifications 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

 init-system-helpers | 1.14| trusty | source, all
 init-system-helpers | 1.14ubuntu1 | trusty-updates | source, all

I'm afraid the fix won't work for Trusty and Xenial.
Trusty is also in EOL.

With that being said, I will set Trusty/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



** Tags removed: patch

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Mathieu Trudel-Lapierre]

** Tags added: rls-x-notfixing

-- 
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:
  In Progress
Status in rsyslog source package in Xenial:
  In Progress
Status in rsyslog source package in Zesty:
  Won't Fix
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Brian Murray]

** Changed in: rsyslog (Ubuntu Zesty)
   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:
  In Progress
Status in rsyslog source package in Xenial:
  In Progress
Status in rsyslog source package in Zesty:
  Won't Fix
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

** Changed in: rsyslog (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: rsyslog (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: rsyslog (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: rsyslog (Ubuntu Zesty)
   Status: Confirmed => In Progress

** Changed in: rsyslog (Ubuntu Xenial)
   Status: Confirmed => In Progress

** Changed in: rsyslog (Ubuntu Trusty)
   Status: Confirmed => In Progress

** No longer affects: rsyslog (Ubuntu Yakkety)

-- 
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:
  In Progress
Status in rsyslog source package in Xenial:
  In Progress
Status in rsyslog source package in Zesty:
  In Progress
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4944790/+files/rsyslog-zesty.debdiff

-- 
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:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  Won't Fix
Status in rsyslog source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

Marking Won't fix for Yakkety as it is EOL.

Removing sts-sru-needed tag until patches are ready.

** Changed in: rsyslog (Ubuntu Yakkety)
   Status: New => Won't Fix

** Tags removed: sts-sru-needed

-- 
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:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  Won't Fix
Status in rsyslog source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Simon Quigley]

Unsubscribing ~ubuntu-sponsors as there's nothing left to do. Please
feel free to resubscribe once patches are ready to upload (or mark your
diff as a patch and let the bot do it for you) or if this was done in
error.

Thank you!

-- 
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:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

@cyphermox Thank you!

-- 
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:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

@slashd Thank you! I will start work on debdiffs for the SRU's ASAP.

-- 
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:
  New
Status in rsyslog source package in Xenial:
  New
Status in rsyslog source package in Yakkety:
  New
Status in rsyslog source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Launchpad Bug Tracker]

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 +

** Changed in: rsyslog (Ubuntu Artful)
   Status: Fix Committed => 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:
  Fix Released
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 source package in Zesty:
  New
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

Hi Frode,

Now that cyphermox sponsored it for Artful ... Could you prepare the
debdiff(s) for the affected supported releases ? and I'll sponsored
them.

Regards,
Eric

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

-- 
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 Committed
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  Fix Committed
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Mathieu Trudel-Lapierre]

Looks like this is still missing one additional commit from when it was
included in Debian; namely the addition of init-system-helpers in the
Depends: field for rsyslog (this makes sure we have a new-enough init-
system-helpers so try-restart works).

I'll add it for you in this case. It feels counterproductive for me to
reject the change again when you already did go back on it before.

By the way, this means that for a xenial SRU, this would need to be
adjusted to the right version number, or that feature will need to be
backported...

-- 
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:
  In Progress
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  In Progress
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

** Changed in: rsyslog (Ubuntu Artful)
   Status: New => Confirmed

** Changed in: rsyslog (Ubuntu Artful)
   Status: Confirmed => In Progress

-- 
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:
  In Progress
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  In Progress
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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch removed: "rsysog-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff

** Patch added: "rsysog-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903910/+files/rsysog-artful.debdiff

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsysog-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4903402/+files/rsysog-artful.debdiff

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch removed: "rsyslog-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff

** Patch removed: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901471/+files/rsyslog-xenial.debdiff

** Patch removed: "rsyslog-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901470/+files/rsyslog-artful.debdiff

** Patch removed: "rsyslog-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900272/+files/rsyslog-yakkety.debdiff

** Patch removed: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900271/+files/rsyslog-zesty.debdiff

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901471/+files/rsyslog-xenial.debdiff

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch removed: "rsyslog-aa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900261/+files/rsyslog-aa.debdiff

** Patch added: "rsyslog-artful.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4901470/+files/rsyslog-artful.debdiff

** Patch removed: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900273/+files/rsyslog-xenial.debdiff

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Eric Desrochers]

** Also affects: rsyslog (Ubuntu Artful)
   Importance: Wishlist
   Status: New

** Also affects: rsyslog (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: rsyslog (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: rsyslog (Ubuntu Zesty)
   Importance: Medium => Wishlist

** Changed in: rsyslog (Ubuntu Trusty)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Changed in: rsyslog (Ubuntu Xenial)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Changed in: rsyslog (Ubuntu Yakkety)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Changed in: rsyslog (Ubuntu Zesty)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Changed in: rsyslog (Ubuntu Artful)
 Assignee: (unassigned) => Frode Nordahl (fnordahl)

** Changed in: rsyslog (Ubuntu Trusty)
   Importance: Wishlist => Low

** Changed in: rsyslog (Ubuntu Xenial)
   Importance: Wishlist => Low

** Changed in: rsyslog (Ubuntu Yakkety)
   Importance: Wishlist => Low

** Changed in: rsyslog (Ubuntu Zesty)
   Importance: Wishlist => Medium

** Changed in: rsyslog (Ubuntu Xenial)
   Importance: Low => Medium

** Changed in: rsyslog (Ubuntu Trusty)
   Importance: Low => Medium

** Changed in: rsyslog (Ubuntu Artful)
   Importance: Wishlist => Medium

** Changed in: rsyslog (Ubuntu Yakkety)
   Importance: Low => Medium

-- 
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 source package in Zesty:
  New
Status in rsyslog source package in Artful:
  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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900273/+files/rsyslog-xenial.debdiff

** Tags removed: sts-sponsor
** Tags added: sts-sru-needed

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900271/+files/rsyslog-zesty.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900272/+files/rsyslog-yakkety.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900262/+files/rsyslog-trusty.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch removed: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842263/+files/rsyslog-zesty.debdiff

** Patch removed: "rsyslog-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828296/+files/rsyslog-yakkety.debdiff

** Patch removed: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828297/+files/rsyslog-xenial.debdiff

** Patch removed: "rsyslog-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828298/+files/rsyslog-trusty.debdiff

** Patch added: "rsyslog-aa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4900261/+files/rsyslog-aa.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Louis Bouchard]

Too late now for sponsorship to Zesty. Since it will come with the next
rsyslog merge in 8.24.0-1, well go forward with the SRU post-merge of
the next rsyslog

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch removed: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842248/+files/rsyslog-zesty.debdiff

** Patch added: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842263/+files/rsyslog-zesty.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-zesty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4842248/+files/rsyslog-zesty.debdiff

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Mathew Hodson]

** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: rsyslog (Ubuntu Trusty)
   Importance: Undecided => Wishlist

** Changed in: rsyslog (Ubuntu Xenial)
   Importance: Undecided => Wishlist

** Changed in: rsyslog (Ubuntu Yakkety)
   Importance: Undecided => Wishlist

-- 
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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Bug Watch Updater]

** 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 : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Brian Murray]

This doesn't yet seem to be fixed in Zesty, although debian fixed it in
package version 8.24.0-1.

** Bug watch added: Debian Bug tracker #791337
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337

** Also affects: rsyslog (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791337
   Importance: Unknown
   Status: Unknown

-- 
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:
  Unknown

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Ubuntu Foundations Team Bug Bot]

The attachment "rsyslog-yakkety.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Louis Bouchard]

** Also affects: rsyslog (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: rsyslog (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: rsyslog (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828298/+files/rsyslog-trusty.debdiff

** Tags added: sts-sponsor

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-yakkety.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828296/+files/rsyslog-yakkety.debdiff

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Patch added: "rsyslog-xenial.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1668639/+attachment/4828297/+files/rsyslog-xenial.debdiff

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

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

[Touch-packages] [Bug 1668639] Re: Add a trigger to reload rsyslog when a new configuration file is dropped in /etc/rsyslog.d

[Frode Nordahl]

** Description changed:

- rsyslog should reload its configuration when other packages drop
- configuration in /etc/rsyslog.d
+ [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

** Tags added: sts

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

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