HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Can't join node to cluster
Operating System - HP-UX
1831349
Members
3069
Online
110024
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
09-05-2004 03:34 PM
09-05-2004 03:34 PM
Can't join node to cluster
After I install patch PHSS_30723. I found some problem. First, I can't join that node to cluster. After I run 'cmrunnode -v msmp1', it's not success. I found some messages in syslog file:
Sep 6 10:00:50 msmp1 cmclconfd[8646]: FtoM - flat header info: magic_number=670
918047 format_version=7 data_version=1 length=15248 size=15248 crc=28753
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Local node msmp1 (B.11.00,11.09) is not r
unning in cluster clsmp (1088535314,1) as node 1
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Unable to connect to 127.0.0.1,5304: 239
Sep 6 10:00:50 msmp1 above message repeats 2 times
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Waiting for next TCP message
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Stopped receiving TCP messages (Software
caused connection abort)
Another problem: I found more problems, example,
-passwd file is changed(for some user).
-can't enter some menu in SAM
-can't use man command, it will return :
msmp1:/var/adm/syslog#man cmrunnode
man: Syntax error at line 1 : `(' is not expected.
Pls. feed back me 2 ways by email and this forrum. I can't online alltime
Thank You
Sep 6 10:00:50 msmp1 cmclconfd[8646]: FtoM - flat header info: magic_number=670
918047 format_version=7 data_version=1 length=15248 size=15248 crc=28753
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Local node msmp1 (B.11.00,11.09) is not r
unning in cluster clsmp (1088535314,1) as node 1
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Unable to connect to 127.0.0.1,5304: 239
Sep 6 10:00:50 msmp1 above message repeats 2 times
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Waiting for next TCP message
Sep 6 10:00:50 msmp1 cmclconfd[8646]: Stopped receiving TCP messages (Software
caused connection abort)
Another problem: I found more problems, example,
-passwd file is changed(for some user).
-can't enter some menu in SAM
-can't use man command, it will return :
msmp1:/var/adm/syslog#man cmrunnode
man: Syntax error at line 1 : `(' is not expected.
Pls. feed back me 2 ways by email and this forrum. I can't online alltime
Thank You
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2004 04:38 PM
09-05-2004 04:38 PM
Re: Can't join node to cluster
Hi,
Was the patch install successful?. Try
swlist -l patch -a state PHSS_30723
It should say configured|applied.
If not, then there might be some issues you may find in swagent.log file that you have to fix.
If the patch install was successful, then I suggest you try the following on msp1 itself.
1. Do
inetd -l (if -l is not already enabled)
remsh msp1 -l root
It should be successful if you are using .rhosts. Otherwise, look at /var/adm/syslog/syslog.log and see how msp1 is appearing as. It should list correct hostname/IP address.
2. Make sure you have all hacl* ports open on the system. 'grep hacl /etc/services' and the corresponding entries in /etc/inetd.conf. Ensure you are not blocking access to port 5304/hacl-cfg in /var/adm/inetd.sec
Your attached syslog.log doesn't show many details.
-Sri
Was the patch install successful?. Try
swlist -l patch -a state PHSS_30723
It should say configured|applied.
If not, then there might be some issues you may find in swagent.log file that you have to fix.
If the patch install was successful, then I suggest you try the following on msp1 itself.
1. Do
inetd -l (if -l is not already enabled)
remsh msp1 -l root
It should be successful if you are using .rhosts. Otherwise, look at /var/adm/syslog/syslog.log and see how msp1 is appearing as. It should list correct hostname/IP address.
2. Make sure you have all hacl* ports open on the system. 'grep hacl /etc/services' and the corresponding entries in /etc/inetd.conf. Ensure you are not blocking access to port 5304/hacl-cfg in /var/adm/inetd.sec
Your attached syslog.log doesn't show many details.
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
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 2025 Hewlett Packard Enterprise Development LP