From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 11:42:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC0EE16A46C for ; Mon, 20 Aug 2007 11:42:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id A110513C461 for ; Mon, 20 Aug 2007 11:42:13 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id E8F3D1B10EEB; Mon, 20 Aug 2007 13:42:11 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id E54BE1B10EE8; Mon, 20 Aug 2007 13:42:11 +0200 (CEST) Message-ID: <46C97E13.3080002@moneybookers.com> Date: Mon, 20 Aug 2007 14:42:11 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.4pre (X11/20070711) MIME-Version: 1.0 To: Eygene Ryabinkin References: <46C18B60.8050400@moneybookers.com> <20070814145759.GB25169@void.codelabs.ru> <20070814193150.GA21553@rot26.obsecurity.org> <46C30FA6.7060108@moneybookers.com> <20070815145640.GQ988@void.codelabs.ru> <46C319DD.3010806@moneybookers.com> <20070815172731.GR988@void.codelabs.ru> <46C3FEBC.80409@moneybookers.com> <20070816080516.GW988@void.codelabs.ru> <46C55684.4050402@moneybookers.com> <20070817083135.GM988@void.codelabs.ru> In-Reply-To: <20070817083135.GM988@void.codelabs.ru> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: current@freebsd.org Subject: Re: "tcpflags 0x18; tcp_do_segment" kernel messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2007 11:42:14 -0000 Hello Eygene, Eygene Ryabinkin wrote: > Stefan, good day. > > Fri, Aug 17, 2007 at 11:04:20AM +0300, Stefan Lambrev wrote: > >> Their response is that the mail server timeout. >> > > And how they are detecting the timeout? They are using alarm(), > just polling for the time with non-blocking read calls, setting the > socket timeout or something else? > They do not provide such information. But they have some kind of cronjob to restart the program if the PHP script stall, which makes me think that it is not something very rare in this case. I'm still waiting better response from their support team and if this happened will let you know. > >> Now the question is why the program things that the server timeouts when it >> does not :) >> > > May be this is connected to the socket timeout stuff: chances are > good that the PHP program uses apr_socket_timeout_set(), so there > can be issues with SO_SNDTIMEO/SO_RCVTIMEO socket options in the > -CURRENT. At least Apache (that I have problems with) sets keep-alived > sockets with apr_socket_timeout_set(). I will try to have a look > if this can be true. > > Thanks for your information! > > Mike, Robert, there are chances that some timeout code behaves > weirdly. And maybe the magic number 3 (every 3rd keep-alived > connection seems to be dropped due to the timeout, Stefan sees it > too) should be searched in the timeout code. Maybe you can give > some hints or point to the exact place where the error can occur? > > Thank you. > -- Best Wishes, Stefan Lambrev ICQ# 24134177