From owner-freebsd-questions@FreeBSD.ORG Fri Aug 26 19:30:33 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 59E8A16A41F for ; Fri, 26 Aug 2005 19:30:33 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from vjofn.tucs-beachin-obx-house.com (vjofn.tucs-beachin-obx-house.com [204.107.90.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id D177943D48 for ; Fri, 26 Aug 2005 19:30:32 +0000 (GMT) (envelope-from ml@t-b-o-h.net) Received: from himinbjorg.tucs-beachin-obx-house.com (ool-44c511d8.dyn.optonline.net [68.197.17.216]) (authenticated bits=128) by vjofn.tucs-beachin-obx-house.com (8.12.9/8.12.9) with ESMTP id j7QJUW7f054704; Fri, 26 Aug 2005 15:30:32 -0400 (EDT) Received: from himinbjorg.tucs-beachin-obx-house.com (localhost.tucs-beachin-obx-house.com [127.0.0.1]) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.12.10) with ESMTP id j7QJUQtW073022; Fri, 26 Aug 2005 15:30:27 -0400 (EDT) (envelope-from ml@t-b-o-h.net) Received: (from tbohml@localhost) by himinbjorg.tucs-beachin-obx-house.com (8.13.3/8.13.1/Submit) id j7QJUQx0073021; Fri, 26 Aug 2005 15:30:26 -0400 (EDT) (envelope-from tbohml) From: Tuc at T-B-O-H Message-Id: <200508261930.j7QJUQx0073021@himinbjorg.tucs-beachin-obx-house.com> To: cswiger@mac.com (Chuck Swiger) Date: Fri, 26 Aug 2005 15:30:26 -0400 (EDT) In-Reply-To: <430F6828.2070109@mac.com> from "Chuck Swiger" at Aug 26, 2005 03:06:16 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Why would mountd die? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Aug 2005 19:30:33 -0000 > > Tuc at Beach House wrote: > > We are having a problem on a 5.4 NFS server where at times > > mountd seems to be just "disappearing". Is there a good way to track > > that this happens, or to find out what causes it to die? > > DJB's daemontools come to mind, also Big Brother (www.bb4.org) can monitor a > system, keeping track of the running processes, and yell (ie, email you, page > you, etc) if something bad happens. > Ok, thanks. > > The first step is to look for log messages (see mountd's "-d" flag), > :-/ Logs to sysout, so can't be run from the /etc/rc.d/mountd. Was hoping to have it log to syslog. I guess I could wrap a shell around it. > > and to > unlimit coredumpsize (see /etc/login.conf and the shell environment) and see > whether you can get a coredump for gdb. > If its run as root, isn't coredumpsize already unlimited? > > It'll help to rebuild mountd with -g for debugging purposes... > If I can get it to do the core, might be the best idea. I decided to run it in a screen to see if I can see maybe something that way. If it gives a clue, maybe won't have to increase coredumpsize and compile with debug for gdb. Thanks, Tuc