Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jan 2001 21:43:59 +0000
From:      Tony Byrne <tony@nua.ie>
To:        Tony Byrne <tony@nua.ie>
Cc:        Andrew J Caines <A.J.Caines@altavista.net>, freebsd-stable@freebsd.org
Subject:   Re: syslogd throwing a hissy fit
Message-ID:  <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com>
In-Reply-To: <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com>
References:  <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Andrew,

I believe that I've narrowed down the problem to the point where someone
with a better knowledge of the internal workings of syslogd should be
able to pinpoint it:

My last CVSup & build world pulled in the same MFC that your's did.  Now
I'm seeing the same strange behavior after the usual build and install.
Regarding the MFC change to syslogd since our last CVSup:  The comment
by the committer seems to suggest that the changes introduced a new
syslog facility called LOG_CONSOLE.  They also mention that the change
includes code to prevent messages with the LOG_CONSOLE facility from
being sent to /dev/console.

My investigations using "syslogd -v" show that the all of the looped and
corrupt log lines that I am seeing are of the LOG_CONSOLE facility with
the 'info' priority.  (console.info) (14.6)

It's my guess that syslogd is entering a tight loop whenever syslog.conf
is configured so that a log message with facility LOG_CONSOLE is
directed to /dev/console.  The committer seems to have been aware of the
problem, but maybe an incorrectly configured syslog.conf would
circumvent the checks within the code?

The work around to the problem is to ensure that syslog.conf does not
send console.* to /dev/console.  For me that involved replacing my local
syslog.conf line:

*.*			/dev/console

with something a little bit more conservative.

Regards,

Tony.

On Wed, 24 Jan 2001 19:06:36 +0000, you wrote:

>Folks,
>
>I'm seeing this behaviour too, as of my make world of today (using up to
>date CVSup'd sources).  Has anyone found the source of the problem.
>It's bloody annoying.  I've had to kill syslogd.
>
>Regards,
>

<SNIP>

>><console.info> hal9000 /kernel: Jan 21 01:21:56 <console.info> halo> =
hal9000 /kernel: Jan 21 01:22:01 <console.info> hal9000 /kernel: Jan 21 =
01:22:00 <console.info> hal9000 /kernel: Jan 21 01 21 01:22:01 =
<console.info> hal9000 /kernel: Jan 21 01:22:00 <console.info> hal9000 =
/kernel: Jan 21 01:22:00 <cokernel: Jan 21 01:21:56 <console.info> =
hal9000 /kernel: Jan 21 01:21:56 <console.info> hal9000 /kernkernel: Jan =
21 01:21:54sole.info> hal9000 /kernel: Jan 21 01:21:54 <console.info> =
hal9000 /kernel: Jan 21 01:21:53 <console.info> hal9000 /kernel: Jan 21 =
01:21:53 <console.info> hal9000 /kernel: Jan 21 01:21:52 <console.info> =
hal9000 /kernel: Jan 21 01:21:52 <console.info> hal9000 /kernel: Jan 21 =
01:21:51 <console.info> hal9000 /kernel: Jan 21 01:21:51 <console.info> =
hal9000 /k
>>Jan 21 01:22:06 <kern.crit> hal9000 /kernel: nfo> hal9000 /kernel: Jan =
21 01:21:57 <conse.
>>Jan 21 01:22:06 <kern.crit> hal9000 /kernel: :21:51 <console.info> =
hal9000 /kernel:=20
>>Jan 21 01:22:06 <kern.crit> hal9000 /kernel: :04 <console.info> hal9000=
 /kernel: :48 <console.info> hal9000 /kernel: Jan 21 01:21:48 =
<console.info> hal9000 /kernel: Jan 21 0




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?s7hu6torq3c79usoqpgig3b56gg9d5n6jr>