Re: Logging with syslog-ng: Won't work

Thank you very much, Benoit,

I'll try it when I get back on the system... a question, if you know the answer... I thought one of the advantages to syslog-ng was that it would use sockets or tcp for logging, not the less reliable udp. I see the solution is to turn on udp -- is this the only way to log from haproxy (via udp, that is?)

Thanks again for the help,
Matt

On Tue, Oct 28, 2008 at 6:29 PM, Benoit <max.maverick#maverick.eu.org>wrote:

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

-- 
It is from the wellspring of our despair and the places that we are broken
that we come to repair the world.
-- Murray Waas