>From global section: log 127.0.0.1 local0 log 127.0.0.1 local1 err
>From defaults section: log global option httplog option log-separate-errors >From rsyslog confg: $Umask 0000 $FileCreateMode 0644 local1.* -/var/log/haproxy/haproxy_errors.log No network capture available. On Fri, Jul 15, 2016 at 3:45 PM, Cyril Bonté <cyril.bo...@free.fr> wrote: > Le 15/07/2016 à 19:35, CJ Ess a écrit : > >> I think I gave the relevant details but here is a sample (with hostname, >> frontend name, backend name, server name, user agent, x-forwarded-for >> chain, and url path changed). I have thousands of these, identical >> frontends, backends, method, and url) to a pool of identical servers. >> Each of these appears in the error log, however they all have in common >> a 200 result code and -'s for state flags. I don't know why these would >> appear in the error log. >> >> 2016-07-15T13:00:19-04:00 hostname haproxy[116593]: 127.0.0.1:62401 >> <http://127.0.0.1:62401> [15/Jul/2016:13:00:16.191] frontend_name >> backend_name/server_name 790/0/953/1155/2898 200 135 - - ---- >> 17847/17845/5414/677/0 0/0 {user_agent|x-forwarded-for} "POST >> /services/xxxxx HTTP/1.1" >> > > Well this log line is a beginning, but details are : > - the haproxy configuration > - the syslog server configuration/rules > - a network capture showing that logs are sent at an error level > > > >> On Fri, Jul 15, 2016 at 1:24 PM, Cyril Bonté <cyril.bo...@free.fr >> <mailto:cyril.bo...@free.fr>> wrote: >> >> Le 15/07/2016 à 17:46, CJ Ess a écrit : >> >> I've got thousands of errors showing up in my haproxy error.log >> but I'm >> not sure why, the requests being logged there have a 200 result >> code and >> the session state flags are all -'s. However its primarily >> requests to a >> particular backend being logged there. What can I do to diagnose? >> >> >> At least, provide some details. >> >> >> >> My HAProxy version is 1.5.18 >> >> >> >> -- >> Cyril Bonté >> >> >> > > -- > Cyril Bonté >
