Re: bootlog on debian 2.0 missing: more people with problem
Benno Overeinder <bjo@wins.uva.nl> wrote:
>
>
> To: debian-user@lists.debian.org
> Subject: Re: bootlog on debian 2.0 missing in /var/log/messages
> From: Benno Overeinder <bjo@wins.uva.nl>
> Date: Wed, 06 Jan 1999 12:01:46 +0100
> cc: Jameson Burt <jameson@mnsinc.com>, dror@mcione.com, bjo@wins.uva.nl
> In-reply-to: Your message of "Wed, 06 Jan 1999 01:05:42 EST."
> <[🔎] m0zxm6C-000KAyC@rabbit.dynamic-ppp-has-no-domain>
>
>
>
> > >
> > >Where is it on the 2.0 version. the /var/log/messages is very abbreviated
> > >the /var/log/syslog is also very abbreviated
> >
> > ditto.
> [...]
> > I suspect that a line must now be missing from some /etc/init.d/* file, eg,
> > klogd -o -f /var/log/messages
> > However, such a line would need to be early in the boot: after /etc/rcS.d/*
> > files run but before most every other boot file since a permanent klogd
> > daemon runs in the file
> > /etc/rc2.d/S10sysklogd
> >
> > I could insert a "klogd -o" command in one of the boot files,
> > if that is what was used before, but I hate to do what should already
> > be done somehow.
> > Any ideas? For example, does your
> > grep klogd /etc/init.d/*
> > reveal a "klogd" with the "-o" option?
>
> I have two Debian installations. One of them is upgraded from 1.3 to 2.0. On
> this system the /var/log/messages contains the boot messages. On the other
> system, I installed a brand new Debain 2.0 distribution (no upgrade). On this
> system, I only see the minimal mark messages, but _no_ boot messages.
>
> Next thing I did is to compare the files in the init.d directory of both
> systems. Apart from the network numbers, the files were identical. So I am
> afraid the problem is more subtle (and I still don't have any clue).
>
I checked with a friend who runs Debian.
He recently installed Debian on a new computer, getting the same
missing boot-log messages in /var/log/messages.
Searching dejanews, I see many people being told they can see
their boot-log messages in /var/log/messages.
New users would not know that the trickle of messages now going
to /var/log/messages all come after booting has finished.
I tried Bennow Overeinder's possible unqualified hostname in /etc/hosts.
I also tried variations in resolv.conf, nsswitch.conf, and hostname.
None resulted in boot-log messages to /var/log/messages.
In the past, I would see the following log messages on booting,
Dec 13 12:41:33 rabbit syslogd 1.3-3#17.1: restart.
Dec 13 12:41:33 rabbit kernel: klogd 1.3-3, log source = /proc/kmsg started.
Dec 13 12:41:33 rabbit kernel: Loaded 4466 symbols from
/boot/System.map-2.0.33.
Dec 13 12:41:33 rabbit kernel: Symbols match kernel version 2.0.33.
Dec 13 12:41:33 rabbit kernel: No module symbols loaded.
Dec 13 12:41:33 rabbit kernel: Console: 16 point font, 400 scans
.
.
.
I now see only these messages on booting,
Jan 8 22:51:36 rabbit syslogd 1.3-3#26: restart.
Jan 8 22:51:40 rabbit kernel: eth0: Promiscuous mode enabled.
Jan 8 22:51:40 rabbit kernel: eth0: Promiscuous mode enabled.
Jan 8 23:09:43 rabbit kernel: IP fw-out deny lo UDP 192.168.1.1:1026
192.168.1.1:53 L=61 S=0x00 I=36 F=0x0000 T=64
Jan 8 23:09:43 rabbit kernel: IP fw-out deny lo UDP 192.168.1.1:1027
192.168.1.1:53 L=61 S=0x00 I=37 F=0x0000 T=64
Jan 8 23:09:46 rabbit kernel: IP fw-out deny lo UDP 192.168.1.1:1028
192.168.1.1:53 L=67 S=0x00 I=38 F=0x0000 T=64
Jan 8 23:09:46 rabbit kernel: IP fw-out deny lo UDP 192.168.1.1:1031
192.168.1.1:53 L=67 S=0x00 I=39 F=0x0000 T=64
Jan 8 23:09:47 rabbit kernel: registered device ppp0
Jan 8 23:09:47 rabbit pppd[710]: pppd 2.3.5 started by jameson, uid 1000
.
.
.
of which the last two messages come from an after boot ppp connection,
so you can see how brief the bootlog is.
I notice that /etc/rc2.d/S10sysklogd starts the syslogd and, in the good
case above, also the klogd daemon. In the good case, immediately
many messages are logged at the same time.
I have the latest sysklog package,
sysklogd_1.3-26.deb
I run under the hamm distribution.
I ran hamm for about 8 months with no boot logging problems,
then I finally finished my hamm installation by running dselect
several times [before I had only used "dpkg" additions to hamm].
Of course, when I upgrade I make other changes, so besides looking
at upgrade changes, I also try to remember my changes.
On writing this, I notice the System-map-2.0.33 in the good version,
so I'll try putting one corresponding to my current kernel in /boot.
This is taking a bit of sleuthing: this is a great hobby.
Any ideas why I and many others get no boot-log messages in /var/log/messages?
--
Jim Burt, NJ9L, Fairfax, Virginia, USA
jameson@mnsinc.com http://www.mnsinc.com/jameson
jameson@pressroom.com (703) 235-5213 ext. 132 (work)
"A poor man associating with a rich man will soon be too poor
to buy even a pair of breeches." --Chinese Proverb
Reply to: