Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - Linux
- >
- General
- >
- RH AS 2.1 and ASRs
General
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Latin America
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-02-2004 03:01 AM
02-02-2004 03:01 AM
RH AS 2.1 and ASRs
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.
Anything at all ?
Anything at all ?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-02-2004 03:28 AM
02-02-2004 03:28 AM
Re: RH AS 2.1 and ASRs
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..
http://www.linuxdevcenter.com/pub/a/linux/2001/11/01/postmortem.html
Also, this is a good article on troubleshooting server crashes..
http://www.linuxdevcenter.com/pub/a/linux/2001/11/01/postmortem.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-02-2004 03:54 AM
02-02-2004 03:54 AM
Re: RH AS 2.1 and ASRs
Thanks Don,
I am still using CIM 6.40 Agents though.
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.
I am still using CIM 6.40 Agents though.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-02-2004 07:00 AM
02-02-2004 07:00 AM
Re: RH AS 2.1 and ASRs
Please use the utility below to collect the necessary HW and SW details on the servers to which you are referring:
http://h18023.www1.hp.com/support/files/serve
r/us/download/16241.html
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.
http://h18023.www1.hp.com/support/files/serve
r/us/download/16241.html
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP