Thanks guys. I'll look further at the haproxy logging and decide whether to
turn off normal log output or not.
Regards,
Guy
On Thu, Apr 5, 2012 at 9:26 PM, Baptiste wrote:
> Hi,
>
> Well, there is a directive called "dontlog-normal" to log only errors
> You should give it a try.
>
> cheers
>
>
Hi,
Well, there is a directive called "dontlog-normal" to log only errors
You should give it a try.
cheers
On Thu, Apr 5, 2012 at 6:30 PM, Guy Knights wrote:
> Thanks Baptiste. I turned on HTTP logging and I'm now getting the actual
> HTTP request path in the log output. It looks like it's just
On 5 April 2012 17:30, Guy Knights wrote:
> Thanks Baptiste. I turned on HTTP logging and I'm now getting the actual
> HTTP request path in the log output. It looks like it's just logging all
> calls from the Nginx reverse proxy we have on the box that's doing SSL
> termination. Is there a way to
Thanks Baptiste. I turned on HTTP logging and I'm now getting the actual
HTTP request path in the log output. It looks like it's just logging all
calls from the Nginx reverse proxy we have on the box that's doing SSL
termination. Is there a way to disable this output to the log? Obviously I
still w
Hi,
You're logging using the tcp log format (option tcplog from your defaults).
You may turn on "option httplog" in your http listen section to get
more information about this request.
It may be some monitoring systems.
Regards
On Thu, Apr 5, 2012 at 4:07 AM, Guy Knights wrote:
> I happened t
I happened to check the haproxy logs today on our load balancer and I'm
seeing a ton of weird logs showing
localhost.localdomain haproxy[18309]: 127.0.0.1:41386[04/Apr/2012:21:03:31.942]
example.com example.com/example-server 0/0/25 238 -- 0/0/0/0/0 0/0
The port number for 127.0.0.1 seems to chan
6 matches
Mail list logo
