From owner-freebsd-questions Wed Jan 24 18:38:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id D4CF537B69C for ; Wed, 24 Jan 2001 18:38:16 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id f0P2fgJ45458; Wed, 24 Jan 2001 18:41:42 -0800 (PST) (envelope-from kris) Date: Wed, 24 Jan 2001 18:41:42 -0800 From: Kris Kennaway To: David Fuchs Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Cyrus causing kernel panic 12 Message-ID: <20010124184142.E45221@citusc17.usc.edu> References: <00d301c08668$a0426340$e5a1f4cc@office.uniserve.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="y2zxS2PfCDLh6JVG" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <00d301c08668$a0426340$e5a1f4cc@office.uniserve.ca>; from dfuchs@beastie.net on Wed, Jan 24, 2001 at 04:48:15PM -0800 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --y2zxS2PfCDLh6JVG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 24, 2001 at 04:48:15PM -0800, David Fuchs wrote: > We're running the Cyrus IMAP server v1.5.24 on FreeBSD 4.1. After a > power-failure crashed the server a few weeks ago, the system has > continued to crash every 16-20hrs - like it's a religious ceremony or > something. The problem is somehow related to Cyrus, but we don't know > how to fix it. We can't just delete all the mailboxes because it's the > main server for an ISP, and many customers rely on it. Following is the > error message that keeps popping up - there has not been any variation > in the message except the process (either cyrus' "quota" or "deliver") > that causes the crash. The system crashes immediately upon a quota > check. We've removed the quotas and headers, and then reconstructed the > headers, but that didn't help. >=20 > Any ideas would be appreciated! Try upgrading to 4.2-STABLE; there have been quite a few stability fixes in the kernel since 4.1-R. It could also be bad hardware which is failing under load. Kris --=20 NOTE: To fetch an updated copy of my GPG key which has not expired, finger kris@FreeBSD.org --y2zxS2PfCDLh6JVG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6b5JlWry0BWjoQKURAlZTAJ9PzfHp3BgZENq4FqAWaM3CfzKHFACg74oq zhYDQMtexlw4nM9YVukEvBo= =LL0F -----END PGP SIGNATURE----- --y2zxS2PfCDLh6JVG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message