HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- hpasm registry crashes
ProLiant Servers (ML,DL,SL)
1825720
Members
3078
Online
109686
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
- Report Inappropriate Content
03-01-2008 04:11 PM
03-01-2008 04:11 PM
hpasm registry crashes
I am working with RHEL 3 on DL 360 Proliants. We are finding that certain registries are disappearing from the /var/spool/compaq/hpasm/registry directory without any apparent reason. The daemons still appear to be running, but SNMP can't find any OID instances since the registry is completely gone.
The cma.log sometimes states that it can't find a certain mib or file, but does not state why the mib or registry has failed.
For instance; I see the following error message in the cma.log:
Mar 01 16:01:34 vadvls07 cmafcad[####]: log_data: open failed, file = /var/spool/compaq/hpasm/registry/fca/phy.3.144
...and I often see problems such as:
Mar 01 15:34:01 vadvls07 cmaided[####]: log_data: open failed, file = mib
A service hpasm restart usually corrects the problem, but this is not an acceptible workaround.
Is there any way to observe any additional logging information, or any tools I can use to further diagnose the problem?
Thanks,
Mike
The cma.log sometimes states that it can't find a certain mib or file, but does not state why the mib or registry has failed.
For instance; I see the following error message in the cma.log:
Mar 01 16:01:34 vadvls07 cmafcad[####]: log_data: open failed, file = /var/spool/compaq/hpasm/registry/fca/phy.3.144
...and I often see problems such as:
Mar 01 15:34:01 vadvls07 cmaided[####]: log_data: open failed, file = mib
A service hpasm restart usually corrects the problem, but this is not an acceptible workaround.
Is there any way to observe any additional logging information, or any tools I can use to further diagnose the problem?
Thanks,
Mike
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP