- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Serviceguard for Linux support of the DL585 an...
Operating System - Linux
1753721
Members
4841
Online
108799
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
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
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
08-11-2004 11:31 AM
08-11-2004 11:31 AM
Serviceguard for Linux support of the DL585 and cmresmond
During Serviceguard for Linux certification testing of the DL585 with RedHat EL 3 U2, a seldom seen problem was discovered. This only affects the disk monitor (cmresmond) and is not specific to the DL585. If this problem is encountered cmresmond will exit with a 'core dump'. This would cause a failover of any package that uses the monitor.
While a patch to address this issue will be available soon, we wanted to allow customers to build Serviceguard clusters with the DL585 immediately. A workaround for this issue is to install and activate a new version of cmresmond.
1. To activate the new version of cmresmond make sure there are no packages running on the node that use it (either halt the packages or move them to another node).
2. Check the PID of cmresmond
#cmresmond --status
3. Relocate the existing cmresmond:
# cd /usr/local/cmcluster/bin
# mv cmresmond cmresmond.orig
4. Download the attached file named cmresmond put it in /usr/local/cmcluster/bin
5. Check the build date of the new cmresmond by running the command
# strings cmresmond | grep 'Build date'
And see that the build date is July 30, 2004
6. Restart cmresmond:
# cmresmond --restart
7. Check that the PID of cmresmond is different than displayed in step #2
#cmresmond --status
8. Restart (or relocate) any packages.
9. Repeat steps 1-8 for all nodes in the cluster.
Note: the options shown for cmresmond (status and restart) have a space and two dashes before them. It may not be clear on the screen.
Regards,
The Serviceguard for Linux Team
While a patch to address this issue will be available soon, we wanted to allow customers to build Serviceguard clusters with the DL585 immediately. A workaround for this issue is to install and activate a new version of cmresmond.
1. To activate the new version of cmresmond make sure there are no packages running on the node that use it (either halt the packages or move them to another node).
2. Check the PID of cmresmond
#cmresmond --status
3. Relocate the existing cmresmond:
# cd /usr/local/cmcluster/bin
# mv cmresmond cmresmond.orig
4. Download the attached file named cmresmond put it in /usr/local/cmcluster/bin
5. Check the build date of the new cmresmond by running the command
# strings cmresmond | grep 'Build date'
And see that the build date is July 30, 2004
6. Restart cmresmond:
# cmresmond --restart
7. Check that the PID of cmresmond is different than displayed in step #2
#cmresmond --status
8. Restart (or relocate) any packages.
9. Repeat steps 1-8 for all nodes in the cluster.
Note: the options shown for cmresmond (status and restart) have a space and two dashes before them. It may not be clear on the screen.
Regards,
The Serviceguard for Linux Team
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-30-2004 10:09 AM
09-30-2004 10:09 AM
Re: Serviceguard for Linux support of the DL585 and cmresmond
The DL585 is now supported with SUSE SLES8 (and UnitedLinux 1.0). The configuration guide (ftp://ftp.compaq.com/pub/solutions/enterprise/ha/linux/svcguard-certmatrix.pdf) will have the supported errata details. There is a DIFFERENT version of cmresmond for SUSE/UL. It is attached to THIS part of the posting. The instructions are the same except for the directory noted in steps 3 and 4. In this case the directory is /opt/cmcluster/bin
Regards,
The Serviceguard for Linux Team
Regards,
The Serviceguard for Linux Team
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP