 | | | How do I trouble shoot or investigate a hung system | How do I trouble shoot or investigate a hung system 2007-05-14 - By David.Knight@(protected)
Back
- 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@(protected)
Sent by: taroon-list-bounces@(protected)
05/14/2007 10:07 AM
Please respond to
"Discussion of Red Hat Enterprise Linux 3 (Taroon)"
<taroon-list@(protected)>
To
TAROON-LIST@(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
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
<br><font size=2 face="sans-serif">- Configure netdump so that you capture
crash files. </font>
<br><font size=2 face="sans-serif"> Capturing
the memory dump is the best way but involves some kernel debugging knowledge
or vendor support.</font>
<br><font size=2 face="sans-serif">- 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,</font>
<br><font size=2 face="sans-serif"> -
I only have been able to get this to work from the CLI console. No luck
when the system has X running and locks..</font>
<br><font size=2 face="sans-serif">- configure your syslog to log kernel
logs to your syslog server. </font>
<br><font size=2 face="sans-serif"> I
have captured errors on the syslog server that never got logged on the
problem system before...</font>
<br>
<br><font size=2 face="sans-serif">Here is a link that may provide more
info:</font>
<br><font size=2 face="sans-serif">http://kbase.redhat.com/faq/FAQ_85_7662.shtm
</font>
<br>
<br>
<br><font size=2 face="sans-serif">Enjoy,</font>
<br><font size=2 face="sans-serif">David Knight</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>d.qureshi@(protected)</b>
</font>
<br><font size=1 face="sans-serif">Sent by: taroon-list-bounces@(protected)<
/font>
<p><font size=1 face="sans-serif">05/14/2007 10:07 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
"Discussion of Red Hat Enterprise Linux 3 (Taroon)" <taroon-list
@(protected)></font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">TAROON-LIST@(protected)</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">How do I trouble shoot or investigate
a hung system</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>I have a HP Proliant DL740 G1 system running RHEL
AS 3 update 4.<br>
System is running on kernel 2.4.21-27.ELsmp.<br>
<br>
I was having problems logging into the above system. I could get as far
as typing the password but after I was unable <br>
to get to the shell prompt. There were disk problems and the front of the
system panel was all fine.<br>
<br>
I had to do a cold reboot to get round the hung system.<br>
<br>
I have looked in the messages log file but no indication of any errors
or problems. The disk space<br>
is just fine.<br>
<br>
Can anyone give me any tips on how to trouble shoot a system after rebooting
it?<br>
<br>
Thanks<br>
<br>
--<br>
Taroon-list mailing list<br>
Taroon-list@(protected)<br>
https://www.redhat.com/mailman/listinfo/taroon-list<br>
</tt></font>
<br>
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|