❦ 17 novembre 2020 14:52 +01, Katharina Drexel:
> When updating from haproxy 2.2.5 to 2.3.0, the logs only go into syslog, not
> to haproxy.log any more.
> For fixing that, you need an additional line in the 49-haproxy.conf of
> rsyslog:
>
> local0.* /var/log/haproxy.log
>
> The diff would be:
>
> --- 49-haproxy.conf 2020-11-16 18:27:04.628696482 +0100
> +++ /tmp/49-haproxy.conf 2020-11-16 18:26:30.896699927 +0100
> @@ -3,7 +3,8 @@
> $AddUnixListenSocket /var/lib/haproxy/dev/log
>
> # Send HAProxy messages to a dedicated logfile
> +local0.* /var/log/haproxy.log
> +
> :programname, startswith, "haproxy" {
> /var/log/haproxy.log
> stop
>
> Im am using bullseye/sid and kernel 5.7.0-2progress5+u1-amd64.
Logging all local0 to /var/log/haproxy.log is too wide. The match below
should still work as the program name is still HAProxy. I don't see
anything that would explain why it would not work. Can you copy/paste
one log line to check if program name is haproxy.
--
F.S. Fitzgerald to Hemingway:
"Ernest, the rich are different from us."
Hemingway:
"Yes. They have more money."
