2010/4/1 Joe P.H. Chiang <jo3chiang#gmail.com>:
> Hi
> Yes im using net/haproxy port
> Yes the log file exist
> i've tried your setup.. and still not logging..
> Im using haproxy 1.4.2 , i wonder if that have anything to do with the
> logging.. im going to downgrade to 1.3.x see if that makes any differences
Hi,
Can you try to put your rule in the first line of syslog.conf
local1.* /var/log/haproxy.log *.err;kern.warning;auth.notice;mail.crit /dev/console
Joris
>
> On Wed, Mar 31, 2010 at 10:53 PM, Ross West <westr#connection.ca> wrote:
>>
>> JPHC> I've trouble logging my haproxy on freebsd 7.2 HA-Proxy version
>> 1.4.2
>> JPHC> 2010/03/17
>>
>> Are you using the net/haproxy port?
>>
>> Make sure the log files exist and/or use the "-C" option (create
>> non-existent log files) for syslogd.
>>
>> Here's an example that works on my test system:
>>
>> -= /etc/rc.conf
>> syslogd_enable="YES"
>> syslogd_flags="-b localhost -C"
>> -=
>>
>> -= /usr/local/etc/haproxy.conf
>> global
>> daemon # set to daemonize
>> log 127.0.0.1:514 local1 debug # syslog logging
>> -=
>>
>> -= /etc/syslog.conf
>> local1.* /var/log/haproxy.log
>> -=
>>
>> Doing a /usr/local/etc/rc.d/haproxy reload generates a bunch of log
>> entries nicely for each config section. You might want to turn down
>> debug mode though. :-)
>>
>>
>> R.
>>
>>
>>
>>
>>
>>
>> --
>>
>>
>
>
>
> --
> Thanks,
> Joe
>
Received on 2010/04/01 10:07
This archive was generated by hypermail 2.2.0 : 2010/04/01 10:15 CEST