Date: Sat, 5 Feb 2000 11:25:09 +1100 From: aunty <aunty@comcen.com.au> To: Gene Harris <zeus@tetronsoftware.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Syslog Stops Logging Message-ID: <20000205112509.A77294@comcen.com.au> In-Reply-To: <Pine.BSF.4.10.10002032022010.15369-100000@tetron02.tetronsoftware.com> References: <Pine.BSF.4.10.10002032022010.15369-100000@tetron02.tetronsoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 03, 2000 at 08:26:43PM -0600, Gene Harris wrote:
> I have noticed, that on occasion, syslog seems to stop
> logging, for no apparent reason.
That's right, it does.
> My primary evidence is that ipfw and tcp_wrappers logging
> just stops, for no apparent reason. When I look at the ipfw
> counters, they are full, yet my ipfw logs aren't showing
> anything.
>
> Is there an issue with logging and syslog? I am running
> 3.4-STABLE, just made world on Jan 25. No other problems
> are noticed.
A few of us have noticed this with 3.3-RELEASE and 3.4-STABLE and
possibly other versions. You can look up the thread from a couple of
weeks ago when the freebsd-questions archive becomes available for
searching again in a few days.
The problem was described, a few of us sent data and compared notes and
the same thing seemed to be happening. As yet we have no explanation
and no real fix.
A quick manual workaround is to kill syslogd stone dead ('ps waux | grep
syslog' find the PID number and then as root 'kill PID' where PID is
that number) then restart it. Sending a SIGHUP to syslogd _should_ make
it re-read its config files and start behaving, but it does not help us
in this case. I suppose you could get fancy and set up a cron job to do
it. Another way should be to tweak newsyslog.conf, but since
newsyslog looks like an important player in the original problem
it's hard to be sure that that would work and keep working.
I'm getting around to setting up a non-freebsd unix machine for remote
logging in case that's a more reliable way of getting the essential
logs for the important systems. Not a pleasant solution.
Soon I guess one of the clever folk will step in and help us work out
the cause enough that we can submit a problem report and get it fixed
for good. Reproducing it on someone else's system will be hard, though,
because it doesn't happen all the time. When logging keeps working, the
problem might still exist and be waiting to pop up in the future.
That's why the cause must be found, not just a fix.
--
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?20000205112509.A77294>