Hi Willy,

The version is 1.4.21
We will try to remove "option abortonclose" and test if the problem persists.

Thanks.

Liang Hong

--


Liang Hong


System Operation Engineer


T    8586 5673-821


F    010-6550 5686


M   187 1019 5645


E    liang.h...@ipinyou.com

北京市朝阳区八里庄西里100号东区 住邦2000,1号楼A座2101室,100025

  北京·上海·广州·硅谷

http://www.ipinyou.com

微博招聘:http://weibo.com/pinyouhudonghr



> -----原始邮件-----
> 发件人: "Willy Tarreau" <w...@1wt.eu>
> 发送时间: 2012年11月7日 星期三
> 收件人: ?????? <liang.h...@ipinyou.com>
> 抄送: yux...@gmail.com, haproxy@formilux.org, "weipeng.wang" 
> <weipeng.w...@ipinyou.com>, mingming....@ipinyou.com, bo.s...@ipinyou.com
> 主题: Re: Re: When will haproxy 1.5 stable version release
> 
> Hi Liang,
> 
> On Wed, Nov 07, 2012 at 04:03:47PM +0800, ?????? wrote:
> > Hi Willy/Yuxans,
> > 
> > Appreciate for your quick reply. Another question is our haproxy log shows
> > many 503 errors. Could you please take a look the attached configuration and
> > log files and give us some suggestions?
> 
> There's something strange there. All of them show the same pattern :
> 
>   Aug 20 09:50:04 cache195 haproxy[5722]: 113.134.48.103:60269 
> [20/Aug/2012:09:50:01.771] www-pool optimus_deliver_server/web116 
> 2237/0/-1/-1/2237 503 212 - - CC-- 22272/22249/76/11/0 0/0 {Mozilla/4.0 
> (compatible; MSIE 6.0; Windows NT 5.1; SV1)} "GET 
> /static/userback163.gif?jsType=6&meStationId=1&clUrl=http%3A%2F%2Fnews.163.com%2F12%2F0820%2F01%2F89AK98C600011229.html&referUrl=http%3A%2F%2Fwww.163.com%2F
>  HTTP/1.1" 
> 
> An apparent immediate client close while connecting to the server. Having
> one such from time to time would not surprize me, but here you have a lot.
> I suspect that haproxy is improperly logging the origin of the issue ('C'
> for client close while it might be another reason). The queues are empty,
> there was no connect retry, so I think that the connection was not even
> attempted.
> 
> Maybe the request came in immediately followed by a FIN packet. It could
> be a proxy causing this to many of your users. Could you please try to
> remove "option abortonclose" and see if the problem persists ? You might
> be observing the side effect of an external misbehaviour.
> 
> BTW, what version is this ?
> 
> Willy
> 

Reply via email to