Date: Tue, 26 Mar 2002 13:49:45 +0100 (CET) From: Michal Mertl <mime@traveller.cz> To: stable@freebsd.org Subject: syslogd stopping to work Message-ID: <Pine.BSF.4.41.0203150838290.32500-100000@prg.traveller.cz>
next in thread | raw e-mail | index | archive | help
After upgrade from 4.2-REL to 4.4-SECURITY syslogd stops logging after
several days of operation. I use it to log routers and such and it's
pretty important for me. I don't want to use some different syslogd unless
absolutelly necessary. It has happened already several times.
'ps axO wchan' gives '49083 sbwait ?? Is 0:06.07 /usr/sbin/syslogd -a
....'. CPU usage is 0% and the daemon stays like this forever. I have
built the binary with debug information and have the
coredump. The backtrace (I sent the daemon ABORT signal) is:
#0 0x280a7674 in recvfrom () from /usr/lib/libc.so.4
#1 0x280b4cb4 in res_send () from /usr/lib/libc.so.4
#2 0x280b7e7d in res_query () from /usr/lib/libc.so.4
#3 0x280b7bd3 in freehostent () from /usr/lib/libc.so.4
#4 0x280b5d91 in getipnodebyaddr () from /usr/lib/libc.so.4
#5 0x280b5494 in getnameinfo () from /usr/lib/libc.so.4
#6 0x804b4e2 in cvthname (f=0xbfbff9e0)
at /data/src/usr.sbin/syslogd/syslogd.c:1215
#7 0x804a18d in main (argc=9, argv=0xbfbffb8c)
at /data/src/usr.sbin/syslogd/syslogd.c:546
#8 0x8049745 in _start ()
From my reading of it it seems syslogd tries to do reverse DNS loookup
(will be disabled by -n ?) and hangs in it. It's quite possible that there
was interminent problem with DNS. May be the problem isn't in syslogd but
in resolver.
Any suggestion as to what else to check? What to do when next time I catch
syslogd frozen?
I installed cron script which checks the syslog state and for about 14
days it didn't happen :-(.
--
Michal Mertl
mime@traveller.cz
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.41.0203150838290.32500-100000>