topic Re: Failed communications in Operating System - HP-UX

Failed communications

Vladimir Coca — Tue, 14 Jun 2005 13:02:52 GMT

Hi all,

I'm trying to create first cluster, have read (I think) all the posts here, and still have no idea how to avoid this error:

Node is refusing ServiceGuard communication

in cmquerycl command

I have th cmclnodelist, I have checked all the ports, the inetd entries (that was the thread I thought was like me, but still with the same problem after checking inetd in yast tool).

I think te problem should be name resolution, because host or nslookup NODE_NAME outs timeout. I don't see inetd.conf file, this also should be the problem.

Any ideas?????

Thanks

Re: Failed communications

RAC_1 — Tue, 14 Jun 2005 13:15:36 GMT

What is the exact error message that you get?? Which version is this??

cmclnodelist is applicable upto certain version. After those versions, you need to specify it in pkg config file itself.

Anil

Re: Failed communications

Mel Burslan — Tue, 14 Jun 2005 14:23:08 GMT

First obstacle you need to tackle before anything else is the name resolution. DO NOT even trust on DNS resolution. Place the names of the each host in both nodes' /etc/hosts file in both simple and fully qualified forms.

If you are still experiencing the problem after that time, please post the exact error message as well as your hpux version and MCSG version for further help.

Re: Failed communications

Vladimir Coca — Tue, 14 Jun 2005 14:24:08 GMT

Version A11.16, and the error message is exactly...

When trying to generate template config list

cmquerycl -v -L /dev/ccis/c0d1p1 -n node1 -n node2 -C $SGCONF/clust1.config

with cmclnodelist

node1 root
node2 root

and two entries in the /etc/hosts file

192.168.1.1 node1
192.168.1.2 node2

Just connected with a crossover cable, and isolated from any other conection, a SLES 9.0 in a DL380 Packaged Cluster.

Re: Failed communications

Vladimir Coca — Tue, 14 Jun 2005 14:27:11 GMT

Sorry, I saw it was th UX forum after I posted the question... The OS is SuSe ES 9.0.

I've already posted the same in the Linux forum

Re: Failed communications

Vladimir Coca — Wed, 15 Jun 2005 05:56:36 GMT

exact error
cmquerycl -v -n node2 -n node1

Begin checking the nodes....
Error:Permision denied to 127.0.0.1
Warning:Unable to determine local domain name for node2
Error:Node node2 is refusing ServiceGuard communication.
Please make sure that the proper etc. etc............and/or the host name lookup resolves th IP adress correctly.
Failed to gather configuration information.

Re: Failed communications

Stephen Doud — Thu, 16 Jun 2005 14:05:05 GMT

This document describes several causes for "permission denied" issues with Serviceguard:
UMCSGKBRC00008185
TITLE: Cluster Configuration Commands Fail with "permission denied"

The section that mentions issues with 127.0.0.1:

CAUSE 6.1: The content of /etc/cmcluster/cmclnodelist is
inaccurate on one or more of the servers in the cluster.
cmclnodelist is formatted just like .rhosts and MUST give root
permission to EVERY node in the cluster (including the local
hostname).

If this file is not in use, Serviceguard will look at
~/.rhosts.

If the one of the cluster nodenames is not in the cmclnodelist file,
this results:
cmrunnode : Unable to determine the nodes on the current cluster
cmrunnode : Either no cluster configuration file exists, or the
file is corrupted, or cmclconfd is unable to run
and this is in syslog.log:
inetd[4095]: hacl-cfg/udp: Connection from unknown (127.0.0.1)

SOLUTION: Recreate either file in this format on each server:

hostA root
hostB root
hostC root

NOTE: non-root users may encounter this message message when attempting to
use cmviewcl. Use /etc/cmcluster/cmclnodelist to authorize non-root
users to operate cmviewcl command.

CAUSE 6.2: Non-cluster hostnames in cmclnodelist has produced the
message: error: permission denied to 127.0.0.1

SOLUTION: See Solution for 5.1

CAUSE 6.3: An invalid (old) /etc/cmcluster/cmclconfig file was restored
from ignite, producing this error when cmquerycl was executed:
error: permission denied to 127.0.0.1

SOLUTION: If there is no cluster built, remove cmclconfig on all
nodes in the intended cluster.

CAUSE 6.4:The October 2004 Serviceguard patch for A.11.14, 11.15 and
11.16 cannot deal with IP addresses in cmclnodelist. The result is:

error: permission denied to 127.0.0.1 (loopback)

SOLUTION: Change the IP statements to hostnames (simple preferred).