From owner-freebsd-questions@FreeBSD.ORG Sat Sep 17 18:57:36 2005 Return-Path: X-Original-To: freebsd-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 00B9216A41F for ; Sat, 17 Sep 2005 18:57:36 +0000 (GMT) (envelope-from snacktime@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B9E943D46 for ; Sat, 17 Sep 2005 18:57:35 +0000 (GMT) (envelope-from snacktime@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so273874nzk for ; Sat, 17 Sep 2005 11:57:35 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=fGzF/qunpJd17BwYNShIfu/B++lWzdo8bl7fFJHzkOixJamk/rC3ptxW0PQ0QGqpx/TINkhGkKmxOTjM5145fGZPSnoPvsU46wG12x7Pc9JYakJFkMpPC2U3EEHOJCh92w3+LSmVNi/cmDug+Gmso16JvLmE5/Gq2BPrfYvz1eo= Received: by 10.54.68.11 with SMTP id q11mr273271wra; Sat, 17 Sep 2005 11:57:35 -0700 (PDT) Received: by 10.54.23.29 with HTTP; Sat, 17 Sep 2005 11:57:35 -0700 (PDT) Message-ID: <1f060c4c05091711577de1e539@mail.gmail.com> Date: Sat, 17 Sep 2005 11:57:35 -0700 From: snacktime To: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: server locks up when unable to allocate swap X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: snacktime@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2005 18:57:36 -0000 A FBSD 4.7 server this morning locked up and when I got to the data center = I=20 found a bunch of IO error messages saying the pager couldn't allocate neede= d=20 swap space (or something close to that). Unfortunately these messages didn'= t=20 get logged anywhere that I could find and I didn't have anything on me to= =20 write them down. The server has 500mb ram and is usually using about 70% of= =20 that. The server didn't panic, but the console was not responsive so I had= =20 to do a cold reboot. Everything came back up fine. Any ideas on how to debug this further? This server has run with the same= =20 configuration (apache/zope/mysql/qmail) for about 2 years without any=20 issues. If something did actually use up all the swap, would what happened= =20 be normal behavior?=20 Chris