Your message dated Tue, 28 Feb 2017 14:59:39 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-haproxy-maintainers] Bug#856353: rsyslog not reloaded
on install
has caused the Debian Bug report #856353,
regarding rsyslog not reloaded on install
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
856353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856353
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: haproxy
Version: 1.5.8-3+deb8u2
The haproxy package adds rsyslogd configuration in /etc/rsyslog.d/ on
install, however the rsyslog service is not reloaded or restarted.
Subsequently any relevant log messages from haproxy will get lost until a
newly commissioned server is rebooted or rsyslog is restarted manually or
by other means.
Steps to reproduce:
1) Install 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
I would suggest that the package triggers reload or restart of the rsyslog
service.
--
Frode Nordahl
--- End Message ---
--- Begin Message ---
❦ 28 février 2017 13:03 +0100, Frode Nordahl <[email protected]> :
> The haproxy package adds rsyslogd configuration in /etc/rsyslog.d/ on
> install, however the rsyslog service is not reloaded or restarted.
> Subsequently any relevant log messages from haproxy will get lost
> until a newly commissioned server is rebooted or rsyslog is restarted
> manually or by other means.
>
> Steps to reproduce:
> 1) Install 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
>
> I would suggest that the package triggers reload or restart of the
> rsyslog service.
This is the same bug as #790871. We won't fix anything in HAProxy as
interacting with another (unexpecting) package during upgrade is
dangerous. Recent versions of rsyslog package comes with a trigger to do
the reload when a configuration file is changed. This should handle this
issue.
--
O, what a tangled web we weave, When first we practice to deceive.
-- Sir Walter Scott, "Marmion"
signature.asc
Description: PGP signature
--- End Message ---
