From owner-freebsd-isp Sun May 5 11:44:21 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA01820 for isp-outgoing; Sun, 5 May 1996 11:44:21 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA01815 for ; Sun, 5 May 1996 11:44:19 -0700 (PDT) Received: from zot.io.org (taob@zot.io.org [198.133.36.82]) by post.io.org (8.7.5/8.7.3) with SMTP id OAA25251 for ; Sun, 5 May 1996 14:45:52 -0400 (EDT) Date: Sun, 5 May 1996 14:43:22 -0400 (EDT) From: Brian Tao To: FREEBSD-ISP-L Subject: Any inn1.4unoff4 on 2.1R caveats? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For some reason, innd core dumped three times so far today (and it's only early afternoon). It was behaving fairly well up until recently when two kernel panics caused reboots. Is there any way of tracking down the cause of the core dumps? Could it be a corrupt history file (how do I check)? I remember something about a bad cancel control message a couple months ago causing innd's all over the place to spew. I've turned off our outgoing feeds for now to narrow down the problem. I'm also upgrading from unoff3 to unoff4 to see if that will help. Have others noticed any unusual instabilities with their FreeBSD servers recently? Mine's a 2.1R box. Thanks. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"