bug report in upstream is open: https://github.com/haproxy/haproxy/issues/963
On Wednesday, 2020-11-18, 09:31:59 (GMT +0100), Vincent Bernat wrote:
> ❦ 18 novembre 2020 09:11 +01, Katharina Drexel:
>
> >> > local0.* /var/log/haproxy.log
> >> >
> >> 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.
> >> --
> >
> > Here some log output from the syslog (when above patch not applied):
> >
> > Nov 18 08:21:48 node1 node1.proxy.nextcloud-test.example.com
> > haproxy[63848]: 194.193.242.80:46764 [18/Nov/2020:08:21:47.102] http-lb4~
> > http-nodes4/node1.nextcloud-test.example.com 0/0/4/1846/1850 200 1785 - -
> > --NN 1/1/2/2/0 0/0 {Mozilla/5.0 (X11; Linux x86_64; rv:82.0) Gecko/20100101
> > Firefox/82.0} "GET
> > https://nextcloud-test.example.com/index.php/svg/core/actions/public?color=fff&v=1
> > HTTP/2.0"
>
> The hostname seems to be repeated. There have been many changes in the
> log infrastructure in 2.3. Looking a bit at the history, maybe this is
> "MEDIUM: log/sink: re-work and merge of build message API." As there are
> many subsequent changes, it's not easy to revert to test.
>
> Could you report this upstream? Maybe they'll have a clue.
>
> Thanks.
> --
> 10.0 times 0.1 is hardly ever 1.0.
> - The Elements of Programming Style (Kernighan & Plauger)
--
Berner Fachhochschule / Bern University of Applied Sciences
IT-Services / Team Linux & Infrastructure Services
Katharina Drexel
IT System Engineer
___________________________________________________________
Dammweg 3, CH-3013 Bern
Telefon direkt +41 31 848 48 87
Telefon Servicedesk +41 31 848 48 48
[email protected]
https://bfh.ch
https://bfh.science
