Re: Syslog with systemd

2018-03-02 Thread Vincent Bernat
❦ 2 mars 2018 19:24 +1100, Igor Cicimov  : >> I suppose the permissions of /var/log are incorrect. It should be owned >> by syslog? > > ​The permissions look ok: > ​ > ​# ls -ld /var/log/ > drwxrwxr-x 16 root syslog 4096 Mar 2 00:00 /var/log/ > # id -a syslog >

Re: Syslog with systemd

2018-03-02 Thread Igor Cicimov
On Fri, Mar 2, 2018 at 5:49 PM, Vincent Bernat wrote: > ❦ 2 mars 2018 09:49 +1100, Igor Cicimov > : > > > $ 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

Re: Syslog with systemd

2018-03-01 Thread Vincent Bernat
❦ 2 mars 2018 09:49 +1100, Igor Cicimov  : > $ 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

Re: Syslog with systemd

2018-03-01 Thread deoren
On 2/27/2018 10:28 PM, Igor Cicimov 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

Re: Syslog with systemd

2018-03-01 Thread Igor Cicimov
On Thu, Mar 1, 2018 at 5:08 PM, Vincent Bernat wrote: > ❦ 1 mars 2018 09:53 +1100, Igor Cicimov > : > > >> > ​Same, no logging:​ > >> [...] > >> > >> Could you strace rsyslogd and check if it is receiving the messages? > > > > > > ​Sure: > > >

Re: Syslog with systemd

2018-02-28 Thread Igor Cicimov
On Thu, Mar 1, 2018 at 2:08 AM, Vincent Bernat wrote: > ❦ 28 février 2018 22:14 +1100, Igor Cicimov com> : > > > ​Same, no logging:​ > [...] > > Could you strace rsyslogd and check if it is receiving the messages? ​Sure: # pidof rsyslogd 4145 #

Re: Syslog with systemd

2018-02-28 Thread Vincent Bernat
❦ 28 février 2018 22:14 +1100, Igor Cicimov  : > ​Same, no logging:​ [...] Could you strace rsyslogd and check if it is receiving the messages? -- This is the first age that's paid much attention to the future, which is a little ironic since we may not have one.

Re: Syslog with systemd

2018-02-28 Thread Igor Cicimov
On Wed, Feb 28, 2018 at 9:28 PM, Vincent Bernat wrote: > ❦ 28 février 2018 21:00 +1100, Igor Cicimov com> : > > > ​# ls -l /var/lib/haproxy/dev/log > > srw-rw-rw- 1 root root 0 Feb 28 16:06 /var/lib/haproxy/dev/log > > > > # lsof -n -p $(pidof

Re: Syslog with systemd

2018-02-28 Thread Vincent Bernat
❦ 28 février 2018 21:00 +1100, Igor Cicimov  : > ​# ls -l /var/lib/haproxy/dev/log > srw-rw-rw- 1 root root 0 Feb 28 16:06 /var/lib/haproxy/dev/log > > # lsof -n -p $(pidof haproxy) | grep dev/log > # In fact, this seems expected because HAProxy is only using

Re: Syslog with systemd

2018-02-28 Thread Igor Cicimov
Hi Vincent, On Wed, Feb 28, 2018 at 6:18 PM, Vincent Bernat wrote: > ❦ 28 février 2018 17:51 +1100, Igor Cicimov com> : > > >> > ​Actually spoke too soon, still have an issue. One of the servers > started > >> > logging there but then stopped and

Re: Syslog with systemd

2018-02-27 Thread Vincent Bernat
❦ 28 février 2018 17:51 +1100, Igor Cicimov  : >> > ​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.​ >> >> Is the issue fixed just by restarting HAProxy or does

Re: Syslog with systemd

2018-02-27 Thread Igor Cicimov
On Wed, Feb 28, 2018 at 5:51 PM, Igor Cicimov < ig...@encompasscorporation.com> wrote: > Hi Vincent, > > On Wed, Feb 28, 2018 at 5:14 PM, Vincent Bernat wrote: > >> ❦ 28 février 2018 15:50 +1100, Igor Cicimov < >> ig...@encompasscorporation.com> : >> >> > ​Actually spoke too

Re: Syslog with systemd

2018-02-27 Thread Igor Cicimov
Hi Vincent, On Wed, Feb 28, 2018 at 5:14 PM, Vincent Bernat wrote: > ❦ 28 février 2018 15:50 +1100, Igor Cicimov com> : > > > ​Actually spoke too soon, still have an issue. One of the servers started > > logging there but then stopped and on the

Re: Syslog with systemd

2018-02-27 Thread Vincent Bernat
❦ 28 février 2018 15:50 +1100, Igor Cicimov  : > ​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.​ Is the issue fixed just by restarting HAProxy or does it persist

Re: Syslog with systemd

2018-02-27 Thread Igor Cicimov
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 com> wrote: > >> Hi all, >> >> I have haproxy 1.7.10-1ppa1~xenial installed on Ubuntu-16.04 and >> struggling to enable

Re: Syslog with systemd

2018-02-27 Thread Igor Cicimov
On Wed, Feb 28, 2018 at 3:28 PM, Igor Cicimov < ig...@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

Syslog with systemd

2018-02-27 Thread Igor Cicimov
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