xy_VVM/cas-au61 1/0/9998 1239 -- 442/442/442/88/0 0/0
2. The maxconn is much more than we need and test.
-Original Message-
From: Cyril Bonté [mailto:cyril.bo...@free.fr]
Sent: Sunday, December 20, 2015 3:51 PM
To: Cohen Galit
Cc: haproxy@formilux.org
Subject: Re: haproxy log
Le
your "server" lines
- ensure your load tests don't exhaust tcp ports.
*From:*Cohen Galit
*Sent:* Tuesday, December 15, 2015 10:59 AM
*To:* Cohen Galit; 'haproxy@formilux.org'
*Subject:* RE: haproxy log
I'm talking about the prints in logs:
Dec 13 10:55:15
Guys,
We really need your advice here.
From: Cohen Galit
Sent: Tuesday, December 15, 2015 10:59 AM
To: Cohen Galit; 'haproxy@formilux.org'
Subject: RE: haproxy log
I'm talking about the prints in logs:
Dec 13 10:55:15 localhost.localdomain haproxy[11803]: 10.106.161.146:34747
I'm talking about the prints in logs:
Dec 13 10:55:15 localhost.localdomain haproxy[11803]: 10.106.161.146:34747
[13/Dec/2015:10:55:05.698] HAProxy_VVM HAProxy_VVM/cas-au53 1/0/ 966 --
447/447/447/88/0 0/0
Dec 13 10:55:15 localhost.localdomain haproxy[11803]: 10.106.161.163:63043
[13/Dec/20
Hi Manoj,
On Fri, Nov 11, 2011 at 04:48:45AM +, Manoj Kumar wrote:
> Hi All,
>
> I have seen some wired issue with haproxy logs files. Tail of HA proxy log,
> notice time is 3 hours ahead. This is hindering our ability to correlate
> logs. It has been fixed after reloading haproxy config.
5 matches
Mail list logo