From owner-freebsd-stable@FreeBSD.ORG Sun Aug 29 17:17:08 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 A8F4F10656A3; Sun, 29 Aug 2010 17:17:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2-6.sentex.ca [IPv6:2607:f3e0:80:80::2]) by mx1.freebsd.org (Postfix) with ESMTP id 668808FC1A; Sun, 29 Aug 2010 17:17:08 +0000 (UTC) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.4/8.14.4) with ESMTP id o7THH0Cq027618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 29 Aug 2010 13:17:00 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.3) with ESMTP id o7THGxcF083744; Sun, 29 Aug 2010 13:16:59 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201008291716.o7THGxcF083744@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 29 Aug 2010 13:16:54 -0400 To: Andre Oppermann From: Mike Tancsa In-Reply-To: <4C7A7DD4.9020803@freebsd.org> References: <201008291409.o7TE9QCJ082862@lava.sentex.ca> <4C7A7DD4.9020803@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.67 on 205.211.164.50 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 17:17:08 -0000 At 11:33 AM 8/29/2010, Andre Oppermann wrote: >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. Actually, I think I might have found the issue. I was focusing on the "memory" part not the limits. The 'RELENG_6 only' is just a fluke as thats a box that sends a lot of email to this particular server. It turns out, sendmail was rate limiting the server sm-mta[25923]: deferring connections on daemon IPv4: 8 per second and somehow syncache is aware/logs this now where as it did not before ? ---Mike >-- >Andre -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike