From owner-freebsd-stable@FreeBSD.ORG Sun Aug 29 16:00:23 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64F331065674 for ; Sun, 29 Aug 2010 16:00:23 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id CD5218FC0C for ; Sun, 29 Aug 2010 16:00:22 +0000 (UTC) Received: (qmail 43803 invoked from network); 29 Aug 2010 15:31:39 -0000 Received: from localhost (HELO [127.0.0.1]) ([127.0.0.1]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 29 Aug 2010 15:31:39 -0000 Message-ID: <4C7A7DD4.9020803@freebsd.org> Date: Sun, 29 Aug 2010 17:33:40 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Mike Tancsa References: <201008291409.o7TE9QCJ082862@lava.sentex.ca> In-Reply-To: <201008291409.o7TE9QCJ082862@lava.sentex.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: syncache errors X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Aug 2010 16:00:23 -0000 On 29.08.2010 16:09, Mike Tancsa wrote: > After upgrading to a recent STABLE, I have been seeing the following sporadic errors > > Aug 28 04:15:15 smarthost2 kernel: TCP: [xx.yy.165.120]:53617 to [xx.yy.164.50]:25; syncache_socket: > Socket create failed due to limits or memory shortage > > this is with > FreeBSD 8.1-STABLE #7: Wed Aug 25 15:32:05 EDT 2010 > and the previous kernel was from July 20th. > > The odd thing is that the error is triggered from a RELENG_6 host only it would seem. I noticed > there are a number of syncache and tcp updates to RELENG_8, is it possible this is related ? I dont > have any specific tweaks in /etc/sysctl.conf > > other than > net.inet.tcp.log_in_vain: 1 > net.inet.udp.log_in_vain: 1 The log_in_vain sysctl would cause the logging of syncache errors as well (net.inet.tcp.log_debug). This was a POLA violation and I've separated them on August 27 on 8-stable. So if you update you won't see them anymore. That doesn't change the fact that the socket create failed though. If it only happens from a RELENG_6 box it probably is a problem with port re-usage by RELENG_6. The difficulty is that sonewconn() fails and doesn't return an error code. Hence it may be one of listen queue limits reached, memory shortage or a problem with inserting the inpcb into the hash lists. -- Andre