GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Lookup-node-by-name failed
Operating System - HP-UX
1848633
Members
4241
Online
104033
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
Forums
Discussions
back
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
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
02-13-2005 09:02 PM
02-13-2005 09:02 PM
Lookup-node-by-name failed
Hi
#cmruncl
syslog:
Feb 14 10:39:23 hprx1 cmclconfd[3898]: Request from root on node hprx1 to start the cluster on this node.
Feb 14 10:39:23 hprx1 cmclconfd[3898]: Executing "/usr/lbin/cmcld" for node hprx1.mayak.ru
Feb 14 10:39:23 hprx1 cmcld: Logging level changed to level 0.
Feb 14 10:39:23 hprx1 cmcld: Daemon Initialization - Maximum number of packages supported for this incarnation is 0.
Feb 14 10:39:23 hprx1 cmcld: Global Cluster Information:
Feb 14 10:39:23 hprx1 cmcld: Heartbeat Interval is 1 seconds.
Feb 14 10:39:23 hprx1 cmcld: Logging level changed to level 0.
Feb 14 10:39:23 hprx1 cmcld: Node Timeout is 2 seconds.
Feb 14 10:39:23 hprx1 cmcld: Network Polling Interval is 2 seconds.
Feb 14 10:39:23 hprx1 cmcld: Auto Start Timeout is 600 seconds.
Feb 14 10:39:23 hprx1 cmcld: Information Specific to node hprx1:
Feb 14 10:39:23 hprx1 cmcld: Cluster lock disk: /dev/dsk/c12t0d0.
Feb 14 10:39:23 hprx1 cmcld: lan0 0x00306e4a109b 192.168.85.8 bridged net:1
Feb 14 10:39:24 hprx1 cmcld: lan1 0x00306e2bef9f 192.1.1.1 bridged net:2
Feb 14 10:39:24 hprx1 cmcld: Heartbeat Subnet: 192.168.85.0
Feb 14 10:39:24 hprx1 cmcld: Heartbeat Subnet: 192.1.1.0
Feb 14 10:39:24 hprx1 cmcld: The maximum # of concurrent local connections to the daemon that will be supported is 2018.
Feb 14 10:39:24 hprx1 cmcld: Lookup-node-by-name failed.
Feb 14 10:39:24 hprx1 cmsrvassistd[3902]: The cluster daemon aborted our connection.
Feb 14 10:39:24 hprx1 cmsrvassistd[3902]: Lost connection with ServiceGuard cluster daemon (cmcld): Software caused connection abort
Feb 14 10:39:24 hprx1 cmlogd: Unable to communicate with ServiceGuard cluster daemon (cmcld): Connection refused
Feb 14 10:39:54 hprx1 cmclconfd[3898]: The ServiceGuard daemon, /usr/lbin/cmcld[3899], exited with a status of 1.
Help, me
#cmruncl
syslog:
Feb 14 10:39:23 hprx1 cmclconfd[3898]: Request from root on node hprx1 to start the cluster on this node.
Feb 14 10:39:23 hprx1 cmclconfd[3898]: Executing "/usr/lbin/cmcld" for node hprx1.mayak.ru
Feb 14 10:39:23 hprx1 cmcld: Logging level changed to level 0.
Feb 14 10:39:23 hprx1 cmcld: Daemon Initialization - Maximum number of packages supported for this incarnation is 0.
Feb 14 10:39:23 hprx1 cmcld: Global Cluster Information:
Feb 14 10:39:23 hprx1 cmcld: Heartbeat Interval is 1 seconds.
Feb 14 10:39:23 hprx1 cmcld: Logging level changed to level 0.
Feb 14 10:39:23 hprx1 cmcld: Node Timeout is 2 seconds.
Feb 14 10:39:23 hprx1 cmcld: Network Polling Interval is 2 seconds.
Feb 14 10:39:23 hprx1 cmcld: Auto Start Timeout is 600 seconds.
Feb 14 10:39:23 hprx1 cmcld: Information Specific to node hprx1:
Feb 14 10:39:23 hprx1 cmcld: Cluster lock disk: /dev/dsk/c12t0d0.
Feb 14 10:39:23 hprx1 cmcld: lan0 0x00306e4a109b 192.168.85.8 bridged net:1
Feb 14 10:39:24 hprx1 cmcld: lan1 0x00306e2bef9f 192.1.1.1 bridged net:2
Feb 14 10:39:24 hprx1 cmcld: Heartbeat Subnet: 192.168.85.0
Feb 14 10:39:24 hprx1 cmcld: Heartbeat Subnet: 192.1.1.0
Feb 14 10:39:24 hprx1 cmcld: The maximum # of concurrent local connections to the daemon that will be supported is 2018.
Feb 14 10:39:24 hprx1 cmcld: Lookup-node-by-name failed.
Feb 14 10:39:24 hprx1 cmsrvassistd[3902]: The cluster daemon aborted our connection.
Feb 14 10:39:24 hprx1 cmsrvassistd[3902]: Lost connection with ServiceGuard cluster daemon (cmcld): Software caused connection abort
Feb 14 10:39:24 hprx1 cmlogd: Unable to communicate with ServiceGuard cluster daemon (cmcld): Connection refused
Feb 14 10:39:54 hprx1 cmclconfd[3898]: The ServiceGuard daemon, /usr/lbin/cmcld[3899], exited with a status of 1.
Help, me
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2005 09:13 PM
02-13-2005 09:13 PM
Re: Lookup-node-by-name failed
Hi,
Check this doc,
http://www4.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=cmcld+Lookup-node-by-name+failed&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
Document description: cmcld: Lookup-node-by-name failed.
Document id: UMCSGKBRC00010751
Regards,
Robert-Jan
Check this doc,
http://www4.itrc.hp.com/service/cki/search.do?category=c0&mode=text&searchString=cmcld+Lookup-node-by-name+failed&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty
Document description: cmcld: Lookup-node-by-name failed.
Document id: UMCSGKBRC00010751
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2005 01:19 AM
02-14-2005 01:19 AM
Re: Lookup-node-by-name failed
In a reported case, a server hostname was changed and ~/.rhosts was updated
on only one of the 2 nodes in the cluster. cmcheckconf and cmapplyconf
worked, but cmruncl failed with the error message listed in the heading.
The remedy was to add the new hostname to the ~/.rhosts file.
on only one of the 2 nodes in the cluster. cmcheckconf and cmapplyconf
worked, but cmruncl failed with the error message listed in the heading.
The remedy was to add the new hostname to the ~/.rhosts file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2005 02:42 PM
02-14-2005 02:42 PM
Re: Lookup-node-by-name failed
Hi,
In /etc/rc.config.d/netconf:
HOSTNAME=hprx1.mayak.ru -> hprx1
Problem solved
Thank all
In /etc/rc.config.d/netconf:
HOSTNAME=hprx1.mayak.ru -> hprx1
Problem solved
Thank all
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP