- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Failed to connect to object manager
Operating System - Linux
1752815
Members
4387
Online
108789
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
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО10-20-2005 07:16 AM
тАО10-20-2005 07:16 AM
Hi,
Just installed SG A.11.16 on SLES 9 SP2. I was able to connect with SGManager until I reboot the server. Now, I got a Failed to connect to object manager in SGManager.
I suspect something not starting at the boot but I can't figure what.
Identd is started and listen on port 113...
Also, if I enable XINETD, I can now connect but nowhere in the doc it say we need XINETD and by default it's disabled in SLES...
Any idea where to look?
Thank you very much...
Eric Bellavance
Ministere des Finances
Just installed SG A.11.16 on SLES 9 SP2. I was able to connect with SGManager until I reboot the server. Now, I got a Failed to connect to object manager in SGManager.
I suspect something not starting at the boot but I can't figure what.
Identd is started and listen on port 113...
Also, if I enable XINETD, I can now connect but nowhere in the doc it say we need XINETD and by default it's disabled in SLES...
Any idea where to look?
Thank you very much...
Eric Bellavance
Ministere des Finances
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-20-2005 06:12 PM
тАО10-20-2005 06:12 PM
Solution
Chapter 3 - page 34-35
http://docs.hp.com/en/B9903-90046/B9903-90046.pdf
Many times these things are difficult to find but I believe this section explains the need for cmomd by Serviceguard Manager. XINETD starts cmomd.
I'm trying to be brief - it is very late here.
"Cluster Object Manager Daemon: cmomd
This daemon is responsible for providing information about the cluster to
clients├в external products or tools such as Serviceguard Manager that
depend on knowledge of the state of cluster objects. Clients send queries
to cmomd and receive responses from it. This daemon may not be running
on your system; it is used only by clients of the object manager.
cmomd accepts connections from clients, and examines queries. The
queries are decomposed into categories (of classes) which are serviced by
various providers. The providers gather data from various sources,
including, commonly, the cmclconfd daemons on all connected nodes,
returning data to a central assimilation point where it is filtered to meet
the needs of the exact client query. This daemon is started by xinetd.
Relevant parameters are found in the /etc/xinetd.d/hacl-probe file.
The path for this daemon is: $SGLBIN/cmomd."
http://docs.hp.com/en/B9903-90046/B9903-90046.pdf
Many times these things are difficult to find but I believe this section explains the need for cmomd by Serviceguard Manager. XINETD starts cmomd.
I'm trying to be brief - it is very late here.
"Cluster Object Manager Daemon: cmomd
This daemon is responsible for providing information about the cluster to
clients├в external products or tools such as Serviceguard Manager that
depend on knowledge of the state of cluster objects. Clients send queries
to cmomd and receive responses from it. This daemon may not be running
on your system; it is used only by clients of the object manager.
cmomd accepts connections from clients, and examines queries. The
queries are decomposed into categories (of classes) which are serviced by
various providers. The providers gather data from various sources,
including, commonly, the cmclconfd daemons on all connected nodes,
returning data to a central assimilation point where it is filtered to meet
the needs of the exact client query. This daemon is started by xinetd.
Relevant parameters are found in the /etc/xinetd.d/hacl-probe file.
The path for this daemon is: $SGLBIN/cmomd."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2005 05:48 AM
тАО10-21-2005 05:48 AM
Re: Failed to connect to object manager
thank's for your answer.
We will enable xinetd on our SLES 9.
Eric
We will enable xinetd on our SLES 9.
Eric
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