Skip to contentSkip to conversation

2.4(.16) kernel logs messages in the wrong order

DISCUSSION Jordan Russell 2 participants 2 messages Nov 27, 2001

lore
Share & tools
lore
#0 lore raw

Hi,
Here's an excerpt from my /var/log/messages. Notice how messages from two different times are strangely mixed together. What's going on? Is there some way to fix it? This does not happen when a 2.2.x kernel is used.

Nov 27 11:38:54 webby sysctl: net.ipv4.conf.default.rp_filter = 1
Nov 27 11:39:15 webby kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Nov 27 11:38:54 webby sysctl: kernel.sysrq = 1
Nov 27 11:39:15 webby kernel: IP Protocols: ICMP, UDP, TCP
Nov 27 11:38:54 webby sysctl: net.ipv4.ip_forward = 1
Nov 27 11:39:15 webby kernel: IP: routing cache hash table of 4096 buckets,
32Kbytes
Nov 27 11:38:54 webby rc.sysinit: Configuring kernel parameters:  succeeded

I'm using Red Hat 7.2 if it matters.

Thanks,

Jordan Russell

#1 lore raw

----- Original Message -----
From: "Jordan Russell" <[email protected]>
To: <[email protected]>
Sent: Tuesday, November 27, 2001 6:55 PM
Subject: 2.4(.16) kernel logs messages in the wrong order

Quoted 3 lines

Hi,
Here's an excerpt from my /var/log/messages. Notice how messages from two different times are strangely mixed together. What's going on? Is there

some

Quoted 8 lines

way to fix it? This does not happen when a 2.2.x kernel is used.

Nov 27 11:38:54 webby sysctl: net.ipv4.conf.default.rp_filter = 1
Nov 27 11:39:15 webby kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Nov 27 11:38:54 webby sysctl: kernel.sysrq = 1
Nov 27 11:39:15 webby kernel: IP Protocols: ICMP, UDP, TCP
Nov 27 11:38:54 webby sysctl: net.ipv4.ip_forward = 1
Nov 27 11:39:15 webby kernel: IP: routing cache hash table of 4096

buckets,

Quoted 2 lines

32Kbytes

Nov 27 11:38:54 webby rc.sysinit: Configuring kernel parameters:

succeeded

Quoted 2 lines

I'm using Red Hat 7.2 if it matters.

Just use "dmesg" instead, that will give you a correct order if you are looking for bootup messages.

Problem is that /var/log/messages is not ordered according to the time when messages were contrieved, instead it is ordered in any order depending on when syslog wants to write the message to the file. The mess you are seeing propably has something to do with the fact that /var/log/messages isn't mounted immediately at boot, and thus cannot be written before syslog starts and has access to the file.

_____________________________________________________

|  Martin Eriksson <[email protected]>
|  MSc CSE student, department of Computing Science
|  Umeå University, Sweden