I've had 3 different servers ASR Lockup /ASR this month and last month and I need to find out why. CIM just tells me the time and the fact that it happened. How can i find out exactly WHAT happened ? Can i configure AS 2.1 to core dump or something like that? Does it by default ? Any logs I should check? I've checked dmesg and messages, nothing just the reboot. No errors.
I had the same problem, turns out it was the new 7.0 Insight Manager agents causing the problem.. I went back to ver. 6.40 and haven't had a problem since..
Also, this is a good article on troubleshooting server crashes..
Compaq has suggested i enter the BIOS and disable the software ASR(ASM) to see whether the reboot is hardware or software related. I cant mess with a production box like that and just wait for it to fall over again. I expected a much better answer than that. Is there no way to determine what is happening on the box? Whats the point of running the agents if they cannot tell me anything, I can tell when my box rebooted by typing "uptime" when i login, i dont need a fancy web page and ages to tell me that. I need them to tell me WHY the box rebooted, or at least give me a clue.
Anyone from HP/Compaq assist in determining whats rebooting my boxes? I dont mind enabling some software to trap things etc etc, but i cant afford down time/reboot to mess with the bios right now.
Please run with verbosity level 5. Please send the output to enterprise.ecs@hp.com and indicate your name and itrc in the subject.
About the agents:
The health driver and agents are not designed to troubleshoot complex operation system issues. They are specifically designed to warn of or prevent against server downtime by notifying the Systems Admin of hardware issues, such as, inevitable hard drive and memory failures. They also enable HP to provide its customers with a pre-failure warranty (replacing parts before they actually fail). The ASR feature in particular, will reboot the server if a lockup period exceeds the timer set in the BIOS instead of leaving the machine in a permanently hung state. Sometimes, however, it is necessary to disable this feature to capture information from the screen before the server is rebooted. In addition, some of our servers have NMI buttons that can cause the HP health driver to dump the stack on which it is running. Also, the SysReq keys can be used to collect information while the server is locked, but before the ASR feature reboots it.
