Re: How do I trouble shoot or investigate a hung system

- Configure netdump so that you capture crash files. 
        Capturing the memory dump is the best way but involves some kernel 
debugging knowledge or vendor support.
- enable the system request key in the /etc/sysctl.conf (kernel.sysrq = 
1). and capture the: Alt-SysRq +  T /  P / M  data on the frozen system,
        - I only have been able to get this to work from the CLI console. 
No luck when the system has X running and locks..
- configure your syslog to log kernel logs to your syslog server. 
        I have captured errors on the syslog server that never got logged 
on the problem system before...

Here is a link that may provide more info:
http://kbase.redhat.com/faq/FAQ_85_7662.shtm


Enjoy,
David Knight




d.qureshi-7yFXA2EciJlaa/[email protected] 
Sent by: [email protected]
05/14/2007 10:07 AM
Please respond to
"Discussion of Red Hat Enterprise Linux 3 (Taroon)" 
<[email protected]>


To
[email protected]
cc

Subject
How do I trouble shoot or investigate a hung system






I have a HP Proliant DL740 G1 system running RHEL AS 3 update 4.
System is running on kernel 2.4.21-27.ELsmp.

I was having problems logging into the above system. I could get as far as 
typing the password but after I was unable 
to get to the shell prompt. There were disk problems and the front of the 
system panel was all fine.

I had to do a cold reboot to get round the hung system.

I have looked in the messages log file but no indication of any errors or 
problems. The disk space
is just fine.

Can anyone give me any tips on how to trouble shoot a system after 
rebooting it?

Thanks

--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list

--
Taroon-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/taroon-list