Subject: Re: Strange problem with syslogd on NetBSD-release-1-5
To: None <netbsd-users@netbsd.org>
From: Jim Breton <jamesb-netbsd@alongtheway.com>
List: netbsd-users
Date: 07/10/2001 19:05:37
On Tue, Jul 10, 2001 at 10:46:22AM +0100, David Brownlee wrote:
> No insights, but have you tried 'ktrace'ing syslogd to see what
> it is doing when things stop working?
Yes, to some extent; what I mean is, I have a ktrace of the syslogd
process which I started _after_ the failure occurred; unfortunately I do
not have one that runs from before the failure, straight through until
after the failure. Here is a snippet, it actually began way before
this, but this is what it was doing before I finally sent it the
SIGTERM. Looks normal afaict. :-\
110 syslogd EMUL "netbsd"
110 syslogd RET poll 1
110 syslogd CALL poll(0x804f180,0x4,0xffffffff)
110 syslogd RET poll 1
[..snipped..]
110 syslogd CALL poll(0x804f180,0x4,0xffffffff)
110 syslogd RET poll 1
110 syslogd CALL poll(0x804f180,0x4,0xffffffff)
110 syslogd RET poll 1
110 syslogd CALL poll(0x804f180,0x4,0xffffffff)
110 syslogd RET poll 1
110 syslogd CALL poll(0x804f180,0x4,0xffffffff)
110 syslogd PSIG SIGTERM caught handler=0x804ac48 mask=() code=0x0
110 syslogd RET poll 1
110 syslogd CALL __sigprocmask14(0x1,0xbfbfd5f4,0xbfbfd5e4)
110 syslogd RET __sigprocmask14 0
110 syslogd CALL gettimeofday(0xbfbfd5fc,0)
110 syslogd RET gettimeofday 0
110 syslogd CALL writev(0x5,0xbfbfd5c4,0x6)
110 syslogd GIO fd 5 wrote 15 bytes
"Jul 10 04:58:57"
110 syslogd GIO fd 5 wrote 1 bytes
" "
110 syslogd GIO fd 5 wrote 4 bytes
"lead"
110 syslogd GIO fd 5 wrote 1 bytes
" "
110 syslogd GIO fd 5 wrote 29 bytes
"syslogd: exiting on signal 15"
110 syslogd GIO fd 5 wrote 2 bytes
"\r
"
110 syslogd RET writev 52/0x34
110 syslogd CALL writev(0x6,0xbfbfd5c4,0x6)
110 syslogd GIO fd 6 wrote 15 bytes
"Jul 10 04:58:57"
110 syslogd GIO fd 6 wrote 1 bytes
" "
110 syslogd GIO fd 6 wrote 4 bytes
"lead"
110 syslogd GIO fd 6 wrote 1 bytes
" "
110 syslogd GIO fd 6 wrote 29 bytes
"syslogd: exiting on signal 15"
110 syslogd GIO fd 6 wrote 1 bytes
"
"
110 syslogd RET writev 51/0x33
110 syslogd CALL open(0x804bd6a,0,0x1b6)
110 syslogd NAMI "/var/run/utmp"
110 syslogd RET open 14/0xe
110 syslogd CALL __fstat13(0xe,0xbfbfcf50)
110 syslogd RET __fstat13 0
110 syslogd CALL read(0xe,0x8055000,0x2000)
110 syslogd GIO fd 14 read 540 bytes
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\
\0\0\0\0\0\0\0\0\0\0\0\0\0\0ttyp0\0\0\0jamesb\0\0.alongtheway.com'\M^K\
J;"
110 syslogd RET read 540/0x21c
110 syslogd CALL read(0xe,0x8055000,0x2000)
110 syslogd RET read 0
110 syslogd CALL close(0xe)
110 syslogd RET close 0
110 syslogd CALL __sigprocmask14(0x3,0xbfbfd5f4,0xbfbfd5e4)
110 syslogd RET __sigprocmask14 0
110 syslogd CALL unlink(0x804b97f)
110 syslogd NAMI "/var/run/log"
110 syslogd RET unlink 0
110 syslogd CALL unlink(0x804f160)
110 syslogd NAMI "/var/run/syslogd.pid"
110 syslogd RET unlink 0
110 syslogd CALL exit(0)