Date: Wed, 24 Jan 2001 19:06:36 +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: <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> In-Reply-To: <20010121021039.A442@hal9000.bsdonline.org> References: <20010121021039.A442@hal9000.bsdonline.org>
next in thread | previous in thread | raw e-mail | index | archive | help
=46olks, 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, Tony. On Sun, 21 Jan 2001 02:10:40 -0500, you wrote: >Folks, > >After the last of a very long line of trouble free updates in the >prescribed manner, this last update has left me with a perfectly working >system except for a posessed syslogd. > >The symptoms are that when I start syslogd, either during normal system >startup or manually, it rapidly starts issuing reams of malformed >kern.crit (and a few other) messages, not stopping until I kill syslogd, >which isn't easy since *.crit messages go to all terminals. > >Here's a small sample. Note that these are not cut-n-paste errors. The >messages really do look like this. > ><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 > > >Sources were cvsup'ed from cvsup11 around midday EST yesterday (Jan = 20th). > >The version of syslogd from /usr/src/usr.sbin/syslogd/syslogd.c is > >$FreeBSD: src/usr.sbin/syslogd/syslogd.c,v 1.59.2.4 2001/01/09 06:51:37 >phk Exp $ > >CVSweb shows one change to syslogd.c since my last update: > > Revision 1.59.2.4 / (download) - annotate - [select for diffs], Tue = Jan 9 06:51:37 2001 UTC (12 days ago) by phk > Branch: RELENG_4 > Changes since 1.59.2.3: +3 -1 lines > Diff to previous 1.59.2.3 (colored) to branchpoint 1.59 (colored) > next main 1.60 (colored) > > MFC: Add LOG_CONSOLE and make sure it doesn't end up on > /dev/console. > >After mergemaster, I performed the requested MAKEDEV update and ran into= a >small problem with /dev/null losing go=3Drw, which I fixed manually. > >While I'm not sure how it's supposed to be, /dev/log is symlinked to >/var/run/log, which does not exist. Is it supposed be be created by >syslogd on startup? > >As another data point, dmesg does this: > ># dmesg >:05 <consol: /kernel:=20 > >This is even wierder: > ># truss dmesg >:05 <consol: /kernel:=20 > >Here's some extra system info. I'll happily provide more on request. > ># uname -a >FreeBSD hal9000.bsdonline.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Sat Jan = 20 18:32 > ># egrep syslogd /etc/rc.conf # Usually YES, of course >syslogd_enable=3D"NO" # Run syslog daemon (or NO). >syslogd_flags=3D"-s -vv -a 127.0.0.1:*" # Flags to syslogd (if = enabled). > ># ls -l /dev/*log /var/run/*log >ls: /var/run/*log: No such file or directory >crw------- 1 root wheel 7, 0 Jan 21 00:10 /dev/klog >lrwxr-xr-x 1 root wheel 12 Sep 9 15:16 /dev/log -> = /var/run/log > ># df >Filesystem 1K-blocks Used Avail Capacity Mounted on >/dev/ad0s1a 63503 32353 26070 55% / >procfs 4 4 0 100% /proc >/dev/ad0s1f 508143 429630 37862 92% /usr >/dev/ad0s1e 127023 18513 98349 16% /var >/dev/ad0s1g 5081581 3609120 1065935 77% /usr/local >/dev/da0s1 1990876 532873 1298733 29% /home >/dev/da1s1 1984735 244184 1581773 13% /.disk >mfs:33 15847 6 14574 0% /tmp >mfs:35 959 68 815 8% /var/run > >For further information, I've put various files - boot massages, kernel >config, rc.conf, make.conf, etc. -on my site to give extra information. >See <http://hal9000.bsdonline.org/tmp/>. > > >I cvsup'ed a short time ago, but none of the few files which have been >updated appeared relevant. > > >-Andrew- 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?7q9u6t0tkj5ktplad6k8468koar3j8jvi9>