From owner-freebsd-questions@FreeBSD.ORG Tue Mar 28 20:00:57 2006 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3EA416A401 for ; Tue, 28 Mar 2006 20:00:57 +0000 (UTC) (envelope-from freebsd@voidmain.net) Received: from pgh.nepinc.com (pgh.nepinc.com [66.207.129.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E55143D73 for ; Tue, 28 Mar 2006 20:00:57 +0000 (GMT) (envelope-from freebsd@voidmain.net) Received: from [192.168.97.222] (dhcp222.eng.nepinc.com [192.168.97.222]) (authenticated bits=0) by pgh.nepinc.com (8.12.11/8.12.11) with ESMTP id k2SK0tkI054421 for ; Tue, 28 Mar 2006 15:00:55 -0500 (EST) (envelope-from freebsd@voidmain.net) Message-ID: <442995E5.9070106@voidmain.net> Date: Tue, 28 Mar 2006 15:00:37 -0500 From: Tom Grove User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060325 X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 4.11 Server Locks Up X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@voidmain.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2006 20:00:57 -0000 Over the past few months I have noticed that our mail server is flat out locking up. I monitor it via Nagios and about once every two months I get emails saying it is down and when I go over to the console the server is totally unresponsive. I've gone through logs every time and find nothing at all wrong. This is a Dell PowerEdge 2850 with Dual Xeon cpu's and 2GB of memory. Uname replies with: FreeBSD colossus 4.11-RELEASE-p13 FreeBSD 4.11-RELEASE-p13 #0: Fri Oct 14 13:34:01 EDT 2005 root@colossus:/usr/obj/usr/src/sys/COLOSSUS i386 One, has anyone else had similar problems with boxes just becoming unresponsive under high load? Two, is there any reason this would occur? -Tom Grove