Date: Thu, 5 Aug 1999 15:42:30 -0700 From: "Jan B. Koum " <jkb@best.com> To: hackers@freebsd.org Subject: possible syslogd bug? Message-ID: <19990805154230.A23245@best.com>
next in thread | raw e-mail | index | archive | help
I have a dedicated syslog machine runnign 3.2 and vanilla syslogd
(started with -vv flags). After running for a few day the file would grow
(this time file was ~40MB) and syslogd would stop writing to a file and
go into a weird state. Here is the ktrace of "hang" syslogd before I did
'reboot'
dlog# kdump
93 syslogd PSIG SIGALRM caught handler=0x804afb8 mask=0x1 code=0x0
93 syslogd RET poll -1 errno 4 Interrupted system call
93 syslogd CALL gettimeofday(0xefbfc84c,0)
93 syslogd RET gettimeofday 0
93 syslogd CALL setitimer(0,0xefbfc844,0xefbfc834)
93 syslogd RET setitimer 0
93 syslogd CALL sigreturn(0xefbfc880)
93 syslogd RET sigreturn JUSTRETURN
93 syslogd CALL poll(0xefbfc94c,0x1,0x9c40)
93 syslogd PSIG SIGALRM caught handler=0x804afb8 mask=0x1 code=0x0
93 syslogd RET poll -1 errno 4 Interrupted system call
93 syslogd CALL gettimeofday(0xefbfc84c,0)
93 syslogd RET gettimeofday 0
93 syslogd CALL setitimer(0,0xefbfc844,0xefbfc834)
93 syslogd RET setitimer 0
93 syslogd CALL sigreturn(0xefbfc880)
93 syslogd RET sigreturn JUSTRETURN
93 syslogd CALL poll(0xefbfc94c,0x1,0x9c40)
93 syslogd PSIG SIGTERM caught handler=0x804b178 mask=0x1 code=0x0
93 syslogd RET poll -1 errno 4 Interrupted system call
93 syslogd CALL sigprocmask(0x1,0x2001)
93 syslogd RET sigprocmask 16385/0x4001
93 syslogd CALL gettimeofday(0xefbfc08c,0)
93 syslogd RET gettimeofday 0
93 syslogd CALL writev(0x12,0xefbfc04c,0x7)
93 syslogd GIO fd 18 wrote 64 bytes
"Aug 3 21:52:25 <syslog.err> dlog syslogd: exiting on signal 15
"
93 syslogd RET writev 64/0x40
93 syslogd CALL writev(0x1d,0xefbfc04c,0x7)
93 syslogd GIO fd 29 wrote 64 bytes
"Aug 3 21:52:25 <syslog.err> dlog syslogd: exiting on signal 15
"
93 syslogd RET writev 64/0x40
93 syslogd CALL sigprocmask(0x3,0x4001)
93 syslogd RET sigprocmask 24577/0x6001
93 syslogd CALL unlink(0x804c9e5)
93 syslogd NAMI "/var/run/log"
93 syslogd RET unlink 0
93 syslogd CALL exit(0x1)
System also shows syslogd is in poll() state when it hangs .. I did
not see anything wrong with syslogd.c when I looked.
The file is now at 62MB, I see if I can debug this further next time
syslogd hangs.
-- yan
P.S. -- Yes, *.* is going into that file ;)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990805154230.A23245>