HP System Crashes!! Reboots!!

[Vijay Appani]

Hi All,

I have been facing a strange scenario.My System (J Class Machine -J2240) reboots automatically for the reasons unknows.

I am herewith enclosign the /etc/shudownlog

12:05 Tue Nov 19, 2002. Reboot:
12:39 Tue Nov 19, 2002. Reboot:
12:55 Tue Nov 19, 2002. Reboot:
10:11 Sun Nov 24 2002. Reboot after panic: , isr.ior = 0'82400e3.40000000'b2f0e4ac
11:01 Sun Nov 24 2002. Reboot after panic: , isr.ior = 0'183400d2.80000000'ee1d2040
10:05 Wed Dec 04 2002. Reboot after panic: , isr.ior = 0'10340074.40000000'469db78

And it boots again but last 3 times it stucked up at booting and throwing an error with
Booting...
Cannot find ENTRY_TEST.
Failed to initialize.
ENTRY_INIT
Status = -3
And after hardboot its working fine.

Can anybody suggest the reason for Crash???

Thanks
Vijay Appani

[Stefan Farrelly]

PATCHES. your server is crashing due to an HP-UX OS problem which can simply be fixed by installing patches. The best thing to do is use the latest QPK bundle which you can download from software.hp.com, which will fix your panics/crashes.

[melvyn burnard]

Well when you see the entries looking like this in shutdownlog:
Reboot after panic: , isr.ior =

Then you are looking at ethter a ServiceGuard TOC (if running ServiceGuard), a manually performed TOC, or an HPMC which is a hardware problem.
I suggest you log a call with your local HP response Centre, and get the dump analysed.

A software panic would normally look something like:
Reboot after panic: Data Page Fault, isr.ior =

[BFA6]

Hi,

Have a look for chassis codes in /var/tombstone/tsxx where xx is a number.

Regards,

Hilary

[Stefan Farrelly]

I dont think it is necessarily a hardware problem. We had a server crashing a lot recently and it looked like this in the shutdownlog;

12:01 Fri Jun 21 2002. Reboot after panic: , isr.ior = 0'10340003.0'701d490
02:23 Thu Aug 22 2002. Reboot after panic: , isr.ior = 0'102401e0.0'a8ea2020
01:29 Sat Oct 12 2002. Reboot after panic: , isr.ior = 0'240030.0'1148

And it was NOT a hardware problem but a patch issue. We installed a single patch for a driver from HP and it fixed it.