[olug] kernel panics

[Ryan O'Rourke]

On Tue, 2003-06-03 at 13:14, Trent Melcher wrote:
> Check your syslog.conf, make sure the line kern.* is going to your messages
> file instead of the console, or have it go to both, plus a remote logging
> machine.

The example in the syslog.conf man page shows logging kernel messages to
a remote machine like this:
kern.* 		@remote-host
So if I want to log kernel messages from linux1 to
/var/log/remote/kernel/ on linux2 where would I specify the directory in
syslog.conf?

I'm guessing the syslog.conf for linux1 read:
kern.*		@linux2:/var/log/remote/kernel

Is that correct?


> -----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 1:03 PM
> To: Omaha Linux User Group
> Subject: Re: [olug] kernel panics
> 
> 
> On Tue, 2003-06-03 at 10:20, Vincent wrote:
> > You may want to modify syslog to also log to a remote system so you can
> get a copy of the error messages.
> 
> So, just by making syslog log to a remote system I should end up with
> kernel panic messages in /var/log/messages? Becuase I don't think I see
> any my current messages log.
> 
> 
> > ----- Original Message -----
> > From: "Ryan O'Rourke" <ryano at ch-gifts.com>
> > To: "Omaha Linux User Group" <olug at olug.org>
> > Sent: Tuesday, June 03, 2003 10:00 AM
> > Subject: Re: [olug] kernel panics
> >
> >
> > > On Tue, 2003-06-03 at 09:50, Vincent wrote:
> > > > That isn't much info to go on, but here are a couple standard things
> to try if you still have trouble after replacing the disk:
> > > >
> > > > First, make sure it reboots after a panic.  Add this to
> /etc/sysctl.conf:
> > > > kernel.panic = 3    # System will reboot 3 seconds after a kernel
> panic
> > > > To enable this now:
> > > > echo "3" > /proc/sys/kernel/panic
> > > >
> > > > Next, try booting with each of these lilo (or grub) boot options and
> see if either helps:
> > > >
> > > > Disable machine checking.  This tells the kernel not to check the
> cpu's data structures.  The BIOS is probably already doing
> > this
> > > > anyway and two simultaneous checks can cause problems.
> > > > append="root=LABEL=/ nomce"
> > > >
> > > > Disable apic.  This disables the use of IRQs above 15 (SMP or not).
> Some hardware has trouble with APIC (Advanced Programmable
> > > > Interrupt Control/ler)
> > > > append="root=LABEL=/ noapic"
> > > >
> > > > Run a memory tester:  http://www.memtest86.com/
> > >
> > >
> > > Thanks, Vincent. That's pretty much what I was looking for - some advice
> > > on what to do when a panic happens and what to keep an eye out for to
> > > solve the problem.
> > > This one seemed particularly scary to me because of the numerous panics
> > > at different times during boot, fsck, and uptime.
> > >
> > > I did find this little gem on O'Reilly's ONLamp.com about preparing a
> > > FreeBSB machine to do a backtrace after a kernel panic to effectively
> > > debug the problem.
> > > Is there some way to do this in RedHat?
> > > http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html?page=1
> > >
> > > _______________________________________________
> > > OLUG mailing list
> > > OLUG at olug.org
> > > http://lists.olug.org/mailman/listinfo/olug
> > >
> >
> > _______________________________________________
> > OLUG mailing list
> > OLUG at olug.org
> > http://lists.olug.org/mailman/listinfo/olug
> 
> 
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug
> 
> 
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> http://lists.olug.org/mailman/listinfo/olug