Hello,
as per Mathias Weiersmueller's report on discourse [1], there is a bug
in TCP logging when using a custom log-format, accessing the frontend
IP or port (%fi/%fp or the deprecated form %Fi/%Fp) in conjunction with
other log variables like %Tw or %B.
Repro config:
global
log <syslog-destination> syslog debug
defaults
log global
log-format %Fi/%B
listen Test
bind :80
server test-src2 10.0.0.254:80
If the %B variable is removed from the above config, logging also works
fine.
This is broken since commit 9b061e332 ("MEDIUM: bstream_sock: add a
get_src and get_dst callback and remove SN_FRT_ADDR_SET"), which is in
1.5-dev9, so this is broken for some time now.
Gonna need someone smarter than me for this one.
cheers,
lukas
[1]
http://discourse.haproxy.org/t/frontend-ip-and-ports-not-logged-in-tcp-mode-custom-log-format-fi-fp/1353/1
