- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Problem ServiceGuard in a MSA500 Cluster Pack
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-13-2007 09:47 AM
05-13-2007 09:47 AM
I`m installing ServiceGuard over two DL380, with a MSA500 array disk. With a 4 SCSI-ports controller.
The OS is RedHat 4 AS U4 for 32 bits technology.
The ServiceGuard version is 11.6.02
I have a message wich appears in the startup time. Says something like:
- Process 'cmviewconf' is using obsolete setsockopt SO_BSDCOMPAT
- Process 'cmclconfd' is using obsolete setsockopt SO_BSDCOMPAT
- Process 'cmviewconfd' is using obsolete setsockopt SO_BSDCOMPAT is using obsolete setsockopt SO_BSDCOMPAT
- Process 'cmviewconf' is using obsolete setsockopt SO_BSDCOMPAT
- Process 'cmrunmode' is using obsolete setsockopt SO_BSDCOMPAT
When I turn on one of the servers, stops the startup of the OS in the 'cmrunmode' message. The startup still stoped till the second server displays the same message. In this moment both servers starts normally. So I can start only one server at a time.
Do yo know something about this?
Thanks a lot.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2007 06:27 PM
05-13-2007 06:27 PM
SolutionSo the cluster is non-functional until both nodes get the message?
Have you conducted any failover tests? I'm wondering if the SG is doing you any good here.
My search turned up nothing, but if the messages are meaningful as a group I'd say there is a softwware problem. I'd look into patching and seeing if this install is clean.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2007 05:28 AM
05-15-2007 05:28 AM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
I don't think that the hang is related to this message.
I am confused about your description. As I understand it, you boot one server, it hangs after those messages. Then you boot the other server, those messages are displayed and both servers start. If this is correct I cannot understand the statement "So I can start only one server at a time."
But the first thing to do is get the latest patch version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2007 08:59 PM
05-15-2007 08:59 PM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
I`m looking for a patch in this site: http://haweb.cup.hp.com/Support/Linux/RecmdPatches.html
I usually apply SGLX_00113. But now I have two DL380 with 64bits processor. But we have installed RedHat4-AS u4 for 32bits technology. Because the customer ask for 32bits.
Any ide for the patch to apply? Because the SGLX_00111 or SGLX_00046 is for IA32.
SG works well, when the two nodes are up. The same text appears but, the cluster starts.
Thanks a lot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2007 01:35 AM
05-16-2007 01:35 AM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2007 02:57 AM
05-16-2007 02:57 AM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
I found in the SAW some problem similar, and sais the same. Install the SGLX_00111 patch. But nothing about SGLX_0046 patch. ¿What is exactly the purpose for this patch?
The monday I`ll go to the customer, to install another SG. So I`ll tell you the results.
Thanks a lot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2007 05:08 AM
05-16-2007 05:08 AM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-16-2007 10:58 PM
05-16-2007 10:58 PM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
Because, I see the RPM of the patches and I think the can overwrite some other files.
Tomorrow is the day of the installation...
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2007 01:16 AM
05-17-2007 01:16 AM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-23-2007 10:45 PM
05-23-2007 10:45 PM
Re: Problem ServiceGuard in a MSA500 Cluster Pack
But now I have notice another problem:
When I have my two nodes down. I switch on one node and everithing starts well. The cluster waits for one minute because I put in the configuration file AUTO_START_TIMEOUT to one minute.
But after this, after the login screen. I do cmviewcl and I found the cluster in "unknown" state.
If I try to make a cmruncl, sais that the cluster is waiting for the other node to start.
There is another parameter to say to the cluster, not to wait to the other node?
If the cluster and both nodes are up and runing, and I switch off one node... everithing works OK... so I don`t know if ther is a locklun problem. I don`t thing so.
Thanks a lot another time.