Matthew Pettis a écrit :
> Hi,
>
> I had a previous post on here about not getting logs out with syslog
> from haproxy. Well, I changed to syslog-ng to see if that would help
> me, and I have similar questions, but for syslog-ng. I have haproxy
> configured as below, and I have the relevant syslog-ng.conf file
> section below, and the full syslog-ng.conf file below that.
> Currently, I am running haproxy with the cfg specified below, and my
> output log from syslog-ng is empty. Any idea why it isn't getting
> picked up?
>
> Thanks,
> Matt
>
> [...]
> syslog-ng.conf full
> ----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+----+
> ...
>
> # all known message sources
> source s_all {
> [...]
> # use the following line if you want to receive remote UDP
> logging messages
> # (this is equivalent to the "-r" syslogd flag)
> # udp();
> };
> ...
haproxy make use of the networked syslog protocol (that's why you have
to set an IP address
in haproxy.cfg.
So as long as you won't enable network listening within your syslog
server you won't be able to
catch thoses messages.
=> uncomment the udp(); line and you shall be fine Received on 2008/10/29 00:29
This archive was generated by hypermail 2.2.0 : 2008/10/29 00:31 CET