From owner-freebsd-hackers Tue Jul 13 13:21:53 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 DE9D114FF2 for ; Tue, 13 Jul 1999 13:21:48 -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 NAA16769; Tue, 13 Jul 1999 13:20:55 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Tue, 13 Jul 1999 13:20:55 -0700 (PDT) From: Doug X-Sender: doug@dt054n86.san.rr.com To: freebsd-hackers@freebsd.org Cc: peter@netplex.com.au Subject: Re: more amd hangs: problem really in syslog? In-Reply-To: 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 After pounding on this some more with today's -current (prior to the MNT_ASYNC flag change) I got a lot more lockups that looked like this: On Mon, 12 Jul 1999, Doug wrote: > Ok, got another hang in "siobi" state (this time after it > successfully completed the script). Here is the trace: > > (gdb) file /usr/sbin/amd > Reading symbols from /usr/sbin/amd...done. > (gdb) attach 155 > Attaching to program: /usr/sbin/amd, process 155 > 0x8063dc4 in open () > (gdb) where > #0 0x8063dc4 in open () > #1 0x806b5c3 in vsyslog (pri=6, fmt=0x809279a "%s", ap=0xbfbfb240 "X") > at /usr/src/lib/libc/../libc/gen/syslog.c:262 > #2 0x806b2c2 in syslog (pri=6, fmt=0x809279a "%s") > at /usr/src/lib/libc/../libc/gen/syslog.c:130 > #3 0x805a3d8 in real_plog (lvl=6, > fmt=0x8091ea0 "recompute_portmap: NFS version %d", vargs=0xbfbfba7c > "\002") > at > /usr/src/usr.sbin/amd/libamu/../../../contrib/amd/libamu/xutil.c:443 > #4 0x805a2be in plog (lvl=16, > fmt=0x8091ea0 "recompute_portmap: NFS version %d") > at > /usr/src/usr.sbin/amd/libamu/../../../contrib/amd/libamu/xutil.c:383 So I started thinking that maybe the problem was actually in syslog (or amd's interface to it). So I disabled the following two options in my amd.conf file: log_file = syslog:local7 log_options = all And lo and behold, it worked like a charm. I was able to run my conf-building script for my web server 20 times in a row with no ill effects. Previously the best I could do was 3 times before it hung. After confirming that it worked with no logging, I tried enabling logging to a regular file, and that also worked like a charm. After turning syslog style logging back on, it locked up cold, with a very similar traceback. If anyone wants to work on this, let me know. 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