Description of problem: If set env ROUTER_SYSLOG_ADDRESS=127.0.0.1 for haproxy router, then find below warning message in haproxy log: [WARNING] 010/021149 (26) : parsing [/var/lib/haproxy/conf/haproxy.config:31] : 'option httplog' not usable with frontend 'public_ssl' (needs 'mode http'). Falling back to 'option tcplog'. Looks it's harmless since it shows "Falling back to 'option tcplog'", but better to dismiss it by updating haproxy-config.template. Version-Release number of selected component (if applicable): openshift v3.9.0-0.16.0 kubernetes v1.9.0-beta1 How reproducible: always Steps to Reproduce: 1. oc env dc/router ROUTER_SYSLOG_ADDRESS=127.0.0.1 2. oc logs router-x-xxxxx 3. Actual results: [WARNING] 010/021149 (26) : parsing [/var/lib/haproxy/conf/haproxy.config:31] : 'option httplog' not usable with frontend 'public_ssl' (needs 'mode http'). Falling back to 'option tcplog'. Expected results: should not show the warning message Additional info: update the haproxy-config.template as below, no warning message. <---snip---> frontend public_ssl {{- if ne (env "ROUTER_SYSLOG_ADDRESS") ""}} option tcplog {{- end }} <---snip--->
Jake: Can you take a look at this please? I suspect that it no longer applies. If it does, PR https://github.com/openshift/origin/pull/18057 may address it.
https://github.com/openshift/origin/pull/19510
Hi, Can anyone please elaborate on why this occurs at all?
Joel: option tcplog and option httplog just control what information gets logged when there is a request. Unless you set the syslog env, no logging of requests occurs. But when logging is requested, the more verbose httplog can not be used with tcp-only connections (i.e. passthrough) so haproxy warns you and falls back to tcplog information only. This is completely harmless.
verified in atomic-openshift-3.10.0-0.47.0.git.0.2fffa04.el7 and issue has been fxied. OS: Red Hat Enterprise Linux Server release 7.5 (Maipo) kernel: Linux ip-172-18-5-139.ec2.internal 3.10.0-862.el7.x86_64 #1 SMP Wed Mar 21 18:14:51 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1816