[olug] kernel panics

[Trent Melcher]

Make sure you have the -r option in the syslog startup script, so it knows
to listen for logging from remote machines.

If the 7.3 startup is the same, just add it to the line "daemon syslogd -m
0 -r"

Trent

-----Original Message-----
From: olug-bounces at olug.org [mailto:olug-bounces at olug.org]On Behalf Of
Ryan O'Rourke
Sent: Tuesday, June 03, 2003 2:36 PM
To: Omaha Linux User Group
Subject: RE: [olug] kernel panics


On Tue, 2003-06-03 at 14:23, Trent Melcher wrote:
> I have never tried that,  All I do is on the remote machine (logger) I
send
> all kern.*      /var/log/kernel.log
> I dont break out each box to a specific file, since logger tags the
specific
> messages from each box with the hostname it came from.

Great. Thanks for all your help everyone. This should make things easier
in the future whenever kernel panics occur.

As a summary:

I have not yet run memtest-86 on the machine, (I'm kind of afraid to
reboot the thing right now) but I am guessing there is a memory module
error causing the kernel panics.

The 'locate' errors I was getting somehow fixed themselves and are not
reoccurring.

I have edited /etc/syslog.conf on linux1 to log all kernel messages
remotely to linux2 like so:
kern.*			@linux1

I have edited /etc/syslog.conf on linux2 to take all kernel messages
from linux1 and log them like so:
kern.*			/var/log/kernel.log

-- Ryan

_______________________________________________
OLUG mailing list
OLUG at olug.org
http://lists.olug.org/mailman/listinfo/olug