topic Re: Reboot after panic: in Operating System - HP-UX

Reboot after panic:

Ashwin_4 — Thu, 14 Oct 2004 02:51:39 GMT

Hi Masters,
We have HP L-CLass Server with hp-ux 11.x, which is rebooting frequently with following message in shutdownlog:

13:06 Mon Oct 11 2004. Reboot after panic: SafetyTimer expired, isr.ior = 0'92
27ffff.c0000000'e83b1030

How to resolve this issue?

Thanks.

Re: Reboot after panic:

Sunil Sharma_1 — Thu, 14 Oct 2004 02:59:10 GMT

have a look on this thread.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?admit=716493758+1097740689233+28353475&threadId=301388

Sunil

Re: Reboot after panic:

Sridhar Bhaskarla — Thu, 14 Oct 2004 03:02:40 GMT

Hi,

"Safety Timer" is associated with serviceguard daemon cmcld. If you are running Serviceguard, set your NODE_TIMEOUT value to atleast 8 seconds with HEARTBEAT_INTERVAL to 2 seconds. That should cover any intermittent network issues.

Also try installing latest ServiceGuard patches. Go to itrc.hp.com -> patches and search for 'cmcld' to find the patch.

If these systems are not setup with serviceguard, ignore this message. It's better to open a call with HP after runnign Q4 analysis.

-Sri

Re: Reboot after panic:

Ashwin_4 — Thu, 14 Oct 2004 03:36:34 GMT

Hi, Parameter setting is as below:
# Cluster Timing Parmeters (microseconds).
HEARTBEAT_INTERVAL 1000000
NODE_TIMEOUT 2000000

# Configuration/Reconfiguration Timing Parameters (microseconds).

AUTO_START_TIMEOUT 600000000
NETWORK_POLLING_INTERVAL 2000000

Re: Reboot after panic:

Ashwin_4 — Thu, 14 Oct 2004 04:01:26 GMT

The output of Q4 is paste below:

q4> trace event 0
stack trace for event 0
crash event was a TOC
Send_Monarch_TOC+0x58
safety_time_check+0x190
per_spu_hardclock+0x3c
clock_int+0x58
mp_ext_interrupt+0x150
ivti_patch_to_nop3+0x0
idle+0xcbc
swidle_exit+0x0

Re: Reboot after panic:

Sridhar Bhaskarla — Thu, 14 Oct 2004 04:19:38 GMT

Hi Ashwin,

Any errors in OLDsyslog.log prior to crash?.

Crash event was a "TOC". So, there is a great possibility that the node TOC'ed due to heartbeat timeouts. See if there are any errors in OLDsyslog.log.

Heartbeat interval of 1 sec and Node timeout for 2 seconds, means if the node doesn't receive two successful heartbeats in 2 seconds then it will consider the other node as down.

This can happen if there are any 'intermittent freezes' on the system. They could be due to heavily set buffer cache (50%), a known bug with ident (in inetd.conf) etc., You can turn of ident in inetd.conf.

Do not forget latest serviceguard patches.

-Sri

Re: Reboot after panic:

Kent Ostby — Thu, 14 Oct 2004 10:47:07 GMT

Ashwin --

Update your NODE TIMEOUT to 8 seconds and that will likely take care of the problem.

This is fairly common for people running SG with the default NODE TIMEOUT setting.

Best regards,

Kent M. Ostby