From owner-freebsd-current@FreeBSD.ORG Wed Oct 29 09:30:28 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D911316A4D1 for ; Wed, 29 Oct 2003 09:30:28 -0800 (PST) Received: from light.sdf.com (light.sdf.com [207.200.153.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB57243FA3 for ; Wed, 29 Oct 2003 09:30:26 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by light.sdf.com with local-esmtp (Exim 4.22) id 1AEu9d-000J17-GV; Wed, 29 Oct 2003 09:30:45 -0800 Date: Wed, 29 Oct 2003 09:30:45 -0800 (PST) From: Tom To: Niklas Saers Mailinglistaccount In-Reply-To: <20031029095404.E28526@doriath.saers.com> Message-ID: <20031029092824.E1970@light.sdf.com> References: <20031029095404.E28526@doriath.saers.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Postfix locks 5.1-servers? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 29 Oct 2003 17:30:29 -0000 Usually if networking locks up like this, you should check the mbuf usage. It is possible for resource starvation to cause a situation where TCP connections are accepted, but can't be sent data. "netstat -m" If that doesn't work, I would recommend cvsup'ping one of the machines to -current. 5.1-p10 just has security fixes, not bug fixes. Tom On Wed, 29 Oct 2003, Niklas Saers Mailinglistaccount wrote: > Hi, > are anyone familiar with conditions where postfix may bring a 5.1-p10 > server to a halt, making the server accept incoming ports (such as 22) but > serve nothing, making getty(8) become non-respondent (pressing enter > doesn't give any feedback) and making the server ignore ctrl-alt-del etc? > > I've got two boxes running FreeBSD 5.1-p10 and Postfix 2.0.10,1 and > 2.0.13,1. They also have a java process (v1.3.1 and v1.4.1) running, but > that one is an extremely tiny process that can only be accessed from one > specific IP and when executing lives for a couple of milliseconds. > > Does this ring any bells with anyone? We've been at it for a while and not > being able to figure it out. The boxes are quite different hardwareish, so > I don't suspect that being the problem. > > Cheers > > Niklas Saers > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >