Date: Tue, 30 Jan 2001 15:17:57 +0000 From: Tony Byrne <tony@nua.ie> To: Andrew J Caines <A.J.Caines@altavista.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: syslogd throwing a hissy fit Message-ID: <4mmd7tkja6j4j8qfhmidddi108eg188t2h@4ax.com> In-Reply-To: <20010129180459.D372@hal9000.bsdonline.org> References: <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <5qou6tkiba9jk6nbjepe9hn2g45hq560ep@4ax.com> <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <20010128162429.A412@hal9000.bsdonline.org> <alma7t4noj9u417v4t026fuuffkoflhf75@4ax.com> <20010129180459.D372@hal9000.bsdonline.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>Thanks for submitting the PR. I'd like to see it if you don't mind = digging >up the reference. Here you go: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D24704 or raw: >Number: 24704 >Category: bin >Synopsis: syslog produces repeated corrupt messages to = /dev/console under certain circumstances >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: =20 >Keywords: =20 >Date-Required: =20 >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 28 13:20:01 PST 2001 >Closed-Date: =20 >Last-Modified: =20 >Originator: Tony Byrne >Release: 4.2-STABLE >Organization: Nua Ltd. >Environment: =46reeBSD cerberus.merrion.nua.net 4.2-STABLE FreeBSD 4.2-STABLE #0: Wed Jan 24 15:45:09 GMT 2001 tony@cerberus.merrion.nua.net:/usr/obj/usr/src/sys/CERBERUS i386 >Description: Under certain circumstances, syslogd will quickly and repeatedly fill /dev/console with corrupt log output. Messages are output at a rate of tens per second. Whenever syslogd exhibits this behaviour, it consumes a large slice of CPU time. An example of this output is: 4 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus /kernel: Jan 24 23:17:23 cerberus syslogd: restart These messsages appear on the console without line breaks and without any meaningful log content. The problem seems to be connected with the newly added LOG_CONSOLE facility (MFC'd recently from CURRENT). It occurs whenever /etc/syslog.conf contains an entry that causes log messages with the LOG_CONSOLE facility to be directed to /dev/console. A typical example of a triggering syslog.conf entry would be: *.* /dev/console >How-To-Repeat: 1) Edit /etc/syslog.conf 2) Insert the line: *.* /dev/console near the top of the file. 3) Restart syslogd >Fix: Ensure that syslog.conf does not use wildcards in such a way that messages with the LOG_CONSOLE facility are directed to /dev/console. The syslogd.c source file seems to include code to prevent this particular problem from arising, but it appears to be broken. >Release-Note: >Audit-Trail: >Unformatted: Regards, Tony. 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?4mmd7tkja6j4j8qfhmidddi108eg188t2h>