On Wed, Feb 28, 2018 at 3:33 PM, Igor Cicimov <
ig...@encompasscorporation.com> wrote:

>
>
> On Wed, Feb 28, 2018 at 3:28 PM, Igor Cicimov <igorc@encompasscorporation.
> com> wrote:
>
>> Hi all,
>>
>> I have haproxy 1.7.10-1ppa1~xenial installed on Ubuntu-16.04 and
>> struggling to enable rsyslog-ing for the service.
>>
>> I have rsyslog running and the following haproxy related config:
>>
>> # cat /etc/rsyslog.d/49-haproxy.conf
>> # Create an additional socket in haproxy's chroot in order to allow
>> logging via
>> # /dev/log to chroot'ed HAProxy processes
>> $AddUnixListenSocket /var/lib/haproxy/dev/log
>>
>> # Send HAProxy messages to a dedicated logfile
>> if $programname startswith 'haproxy' then
>> ​​
>> /var/log/haproxy.log
>> &~
>>
>> Haproxy is started with:
>>
>> global
>>     log /dev/log    local0
>>     log /dev/log    local1 debug
>>     maxconn         4096
>>     debug
>>     chroot          /var/lib/haproxy
>>     stats socket    /run/haproxy/admin.sock mode 660 level admin
>>     stats timeout   30s
>>     user            haproxy
>>     group           haproxy
>>     daemon
>>
>> same as I had for Ubuntu-14.04.
>>
>> What am I doing wrong?
>>
>> ​Thanks,
>> Igor​
>>
>>
> ​*sigh* ignore that, forgot to create the ​
> ​
> /var/log/haproxy.log file before i started the service :-/
>
>
​Actually spoke too soon, still have an issue. One of the servers started
logging there but then stopped and on the other the file is still empty.​

Reply via email to