Date: Fri, 29 Aug 2003 14:36:01 +0200 From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= <sten.daniel.sorsdal@wan.no> To: <freebsd-questions@freebsd.org> Subject: Syslogd dying often on different hardware - hackers? Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DF27@exchange.wanglobal.net>
next in thread | raw e-mail | index | archive | help
Many of my servers tend to have their syslogd die on them. In dmesg i could see the signal number on one of them; 11 But kill -l doesnt reveal which that is: pid 17263 (syslogd), uid 0: exited on signal 11 pid 87264 (syslogd), uid 0: exited on signal 11 /var/log has lots of space, newsyslog does it's job regularly. The versions vary from 4.7 to 4.9-prerelease. Lots of memory available. Hardware ranges from 1ghz celerons, 400mhz p3's, 1.6ghz p4's. The command lines are either; -nccvvs -ccvvs (but mostly) -vvs They log to remote host that is currently unavailable.=20 (router emites destination host unreachable). The reason i mention this is that many types of software misbehave=20 when they receive this message. When i ran syslogd -dvvs in 'screen' it started logging to remote = 'loghost'.=20 For a -long- time it kept repeating "Host is down" and tried to log to = 'loghost'=20 'loghost' is a local alias. I'm finding it hard to reproduce. -- Sten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0AF1BBDF1218F14E9B4CCE414744E70F07DF27>