Server Rebooting automatically

[susee]

Hi All

One of the N - Class server is rebooting automatically

So far it has rebooted twice in quick sessions

investigating the shutdown log i found the following
-------------------------------------------
11:38 Sat Apr 24, 2004. Reboot: (by norsapa600!emc)
11:03 Wed Oct 20, 2004. Reboot: (by norsapa600!chrisarn)
08:47 Fri Feb 17 2006. Reboot after panic: , isr.ior = 0'18340107.40000000'387392a8
09:21 Fri Feb 17 2006. Reboot after panic: , isr.ior = 0'10340005.0'3e0f91d8
--------------------------------------------
and the syslog shows
Feb 17 08:45:52 norsapa600 krsd[2771]: Delay time is 300 seconds
Feb 17 08:45:52 norsapa600 sfd[2772]: recovering from previous daemon crash.
Feb 17 08:45:54 norsapa600 syslogd: restart
--------------------------------------


I have attached the ts99 file for reference

pls suggest where the problem lies


Thanks & regards

[susee]

Hi all
Any Quick comments pls

[Rick Garland]

The tb99 file is not all 0
Is the a recent /var/adm/crash? If so, can you run q4 against it?

At the very least, submit these to HP for analysis. They have the tools to decipher these codes and get you an answer.

[Chan 007]

Hi,

Crashinfo is a better tool. So beter raise a call with HP, they will provide you that tool. Ensure that you have complete crash dump.

Chan

[Bharat Katkar]

Hi,
I would also check /etc/rc.log to see if any service/module is causing problem, not getting started and making system to crash and reboot.
And in case if you see any failed or hanged sevcies you can probably disable them from starting during bootup and then diagnose furtherr. Set appropriate varibale in files at /etc/rc.config.d.

Regards,

[Raj D.]

Hi Susee,

08:47 Fri Feb 17 2006. Reboot after panic: , isr.ior = 0'18340107.40000000'387392a8

1. Means it is a PANIC reboot and causng a system crash . Check /var/adm/crash/crash.* for any crash dump.

2. Run the HP Collection.sh utility along with crashinfo binary , to debug and you can send the result tar.gz file to HP to know the reason of the crash.

3. You can also log a call to HP, if you are under HP support Contract. Send ts99 file to HP . Hp can debug it quickly , though Q4 tool can be used for debug but time consuming. It seems it happened due to a Hardware error. (You can keep an eye on EMS events.)

Hope this will help,

Good luck ,

hth,
Raj.

[Yogeeraj_1]

hi,

also have a look at you GSP logs.

hope this helps too!

kind regards
yogeeraj

[Chauhan Amit]

Hi Susse,

There is a Valid Timestamp in the ts99 file
"Timestamp = Fri Feb 17 14:09:45 GMT 2006" , Suggests this is a HPMC ( High Priority Machine Check). Server got rebooted due to some hardware problem. Log a case with HP so that they can decode this ts99 file to point out the Specific Hardware.

-Amit

[Chauhan Amit]

Hi Susee,

There is a Valid Timestamp in the ts99 file
"Timestamp = Fri Feb 17 14:09:45 GMT 2006" , Suggests this is a HPMC ( High Priority Machine Check). Server got rebooted due to some hardware problem. Log a case with HP so that they can decode this ts99 file to point out the Specific Hardware.

-Amit

[Ajitkumar Rane]

Susee,

Since you have a valid timestamp in the ts99 file, it looks more of a H/W error. It would be wise to log a call with HP. Other case would be if you have recently installed any software product or made any changes to the system, which you can revert back and observe if the symptom vanishes.

do find some time to assign points to the members who spend their time to answer your queries

Regards,

Ajit