[ale] server crash

[Chris Coleman]

Whether or not core dump files will be created is determined by the ulimit command in /etc/profile. In RH9 it appears the core files are disabled by default. The command used in /etc/profile is ulimit -S -c 0 > /dev/null 2>&1. By changing 0 to a size or the keyword unlimited should create a dump file. This dump file should survive a system reboot.


Chris Coleman

-----Original Message-----
From: Keith Hopkins [mailto:hne at hopnet.net]
Sent: Monday, November 17, 2003 11:45 AM
To: Atlanta Linux Enthusiasts
Subject: Re: [ale] server crash


James P. Kinney III wrote:
> On Mon, 2003-11-17 at 09:57, Stuffed Crust wrote:
> 
>>On Mon, Nov 17, 2003 at 09:58:26AM -0500, Jeff Hubbs wrote:
>>
>>>Speaking only academically, I don't see how it could!
>>>
>>>On Mon, 2003-11-17 at 09:32, James P. Kinney III wrote:
>>>
>>>>When a linux box drops core into /proc/kcore, will that file survive a
>>>>reboot? I was _looking_ at /proc when the coredump happened!
>>
>>/proc/kcore is a "live" image of the kernel, in the form of a coredump 
>>file.  It's used in conjuction with gdb to debug a running system.
>>
>>The file isn't preserved across reboots, it's simply always there. :)
> 
> arrggghhhh!
> I really needed that core file to try and decode the what is happening.
> This machine has a history of being cranky. There is a kernel patch for
> making tombstones but it is not available for the kernel version being
> used.
> 

Have you considered something like the Kernel State Tracer http://sourceforge.net/projects/lkst/ or,
( Core Dumps http://oss.missioncriticallinux.com/projects/mcore/ or Crash Dumps http://oss.sgi.com/projects/lkcd/ ) and Core Analysis http://oss.missioncriticallinux.com/projects/crash/

-- 
Lost in Tokyo,
  Keith


_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale