Subject: Re: syslogd restart triggers a kernel trap?
To: Tom Haapanen <tomh@metrics.com>
From: Charles M. Hannum <root@ihack.net>
List: port-alpha
Date: 03/03/2001 10:32:27
On Sat, Mar 03, 2001 at 11:51:03AM -0500, Tom Haapanen wrote:
> Since upgrading one of our servers to 1.5 a few weeks ago, we are now seeing
> occasional kernel traps, apparently (and usually) triggered by a syslogd
> restart:
> 
> Mar  3 01:40:06 omega /usr/local/sbin/named[5128]: lame server on
> '52.33.32.209.
> in-addr.arpa' (in '33.32.209.in-addr.arpa'?): 209.23.180.2#53
> Mar  3 01:44:18 omega syslogd: restart
> Mar  3 01:44:18 omega /netbsd:
> Mar  3 01:44:18 omega /netbsd: fatal kernel trap:
...
> Mar  3 01:44:19 omega /netbsd: dumping to dev 4,1 offset 263023
> Mar  3 01:44:19 omega /netbsd: dump 128 127 126 125 124 123 122 121 120 119
> 118

Since it dumped, you should be able to inspect the core dump and find
out where it crashed.  A stack trace would be most helpful.