Date: Fri, 7 Jan 2000 14:57:33 +1100 From: aunty <aunty@comcen.com.au> To: freebsd-questions@freebsd.org Subject: syslogd stops Message-ID: <20000107145733.B29088@comcen.com.au>
next in thread | raw e-mail | index | archive | help
Two 3.3-RELEASE machines are experiencing the same thing: logging stops
every so often, probably at a time that logs are rotated. Both machines
are used to receive logs from other machines as well, if that matters.
When logging stops, both local and remote origin log entries stop being
written, and there are no more of those pesky messages to root's
console either. It all just stops. Sending a sighup to syslogd doesn't
help. The only way is to completely kill it and restart syslogd.
I found a very similar problem in the archives written two years ago,
but there wasn't any response that I could see via threading.
> Date: Fri, 6 Feb 1998 13:06:39 +0200 (EET)
> From: Petri Helenius <pete@sms.fi>
> To: freebsd-questions@FreeBSD.ORG
> Subject: syslogd problem
> Message-ID: <199802061106.NAA07686@silver.sms.fi>
>
> I've a problem in 2.2-STABLE cvsupped about a week ago (but the
> problem existed earlier also) that syslogd stops logging messages
> received over network after a while, usually after when a router or
> similar device in the network has been reset. The only way to restore
> functionality is to kill and restart syslogd. This used not to happen
> about half a year ago.
>
> Any ideas what might be causing this?
>
> Pete
>
--
Regards,
-*Sue*-
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000107145733.B29088>