On Thu, Mar 1, 2018 at 5:08 PM, Vincent Bernat <ber...@luffy.cx> wrote:
> ❦ 1 mars 2018 09:53 +1100, Igor Cicimov <ig...@encompasscorporation.com
> > :
>
> >> > Same, no logging:
> >> [...]
> >>
> >> Could you strace rsyslogd and check if it is receiving the messages?
> >
> >
> > Sure:
> >
> > # pidof rsyslogd
> > 4145
> > # strace -p 4145
> > strace: Process 4145 attached
> > select(1, NULL, NULL, NULL, {469, 541106}) = 0 (Timeout)
> > select(1, NULL, NULL, NULL, {600, 0}
> >
> > and that's it, sitting like this for 15 minutes.
>
> Try with -ff
>
Good point:
[*pid 4150*] 09:32:20 open("/var/log/haproxy.log",
O_WRONLY|O_CREAT|O_NOCTTY|O_APPEND|O_CLOEXEC, 0640) = -1 EACCES (Permission
denied)
which means the syslog user does not have permissions to write to this
file, which is correct:
# ls -l /var/log/haproxy.log
-rw-r--r-- 1 haproxy haproxy 0 Feb 28 15:31 /var/log/haproxy.log
On the working server I can see:
$ ls -l /var/log/haproxy.log
-rw-r----- 1 syslog adm 48939 Mar 1 20:17 /var/log/haproxy.log
and I'm sure this file was automatically created (by rsyslog I guess?).
I'm sure this has always been the case hence the reason I was confused when
I had to create it manually (obviously with wrong permissiosn :-/ ).
So the question is now why this file did not get created in the first place
although I restarted rsyslog and haproxy several times?
