From owner-freebsd-hackers Tue Jul 13 16:19: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134]) by hub.freebsd.org (Postfix) with ESMTP id 5C58D14DF9 for ; Tue, 13 Jul 1999 16:19:01 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id QAA18703; Tue, 13 Jul 1999 16:18:55 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 13 Jul 1999 16:18:55 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: more amd hangs: problem really in syslog? In-Reply-To: <199907132256.PAA81648@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 13 Jul 1999, Matthew Dillon wrote: > Comment the whole thing out, kill -HUP the syslogd (or kill and restart > it), and see if amd still locks up. Ok, now I think I get it. You want me to enable syslog'ing in amd, then do what you're talking about here. I will try this first thing tomorrow morning. We're about to put the box into production to make sure that the bug is really licked, then I'm about to go home. :) We have multiple machines in this configuration, so taking this one down tomorrow should be no problem. > If it does not, add the file lines > (/var/*) back in, restart, and see if amd locks up. If it does not, > add the /dev/console line back in, restart, and see if amd locks up. > If it does not, add the "root" and "*" entries back in and see if amd > locks up. And so forth. Gotcha. > We may find that there is something inherently broken with syslogd > that is causing the lockup even with all entries commented out, or > we may well find that it is a certain line, such as the /dev/console, > root, or "*" line for emergency messages that is causing amd to lockup. I think that Mike Smith is on the right track in suspecting that the serial console is involved (due to the siobi state that amd was hanging in). However, which line of the syslog.conf that was causing that is a darn good question, given that none of them *should* have been involved. Thanks for all the great suggestions, Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message