Error messages in syslog from cmclconfd

[BEULAYGUE Berenice]

Hi all,
In my itanium cluster configuration :
MC/SG 11.18
HPUX 11.23
/etc/hosts is set with both names of
cluster servers and theirs backups interfaces


I'm getting this messages :
cmclconfd Client provided hostname xxxx which does not match resolved name xxx.yyy.zzz.com

Do you have an idea of what is the problem???

I have two packages running and they have no problems.
I have 3 lan interfaces, the working one, the
backup one and the heart beat one. All tree
are working normally.

Thanks for your help

Berenice

[melvyn burnard]

it appears that somewhere you have a networking information mismatch. The server has issues resolving names vs fqdn's.

I suggest yopu look at your hostname/ip address resolution using things like nslookup etc.
Also, use cmviewconf to see what the binaryu sees for hostnames etc.

[BEULAYGUE Berenice]

Hi, thanks for your answer,

Servers seems to resolve normally server
names, but most of the servers listed are
not in the "cluster configuration", but
those in cluster configuration appears also.
Cluster works normally, that's why I thought
it was probably no problem whith hosts file.

Berenice

[Aashique]

Hi,
please check your Node entry in the pkg.conf file and also /etc/cmclnodelist file.

Thanks

[BEULAYGUE Berenice]

Hi,

All package have NODE_NAME set to "*"
and cmclnodelist has the two servers that
makes the cluster.
I have 3 clusters with this problem all
of them are Itanium servers, HPUX 11.23
and MC/SG 11.18, all of them have theses
messages ...

Thanks

Berenice

[skt_skt]

are you able to resolve the xxx.yyy.zzz.com from host xxxx ?

is xxx.yyy.zzz.com on a pkg or independant of package?

[BEULAYGUE Berenice]

Hi,
Yes all names that are not in cluster, are
resolvable by DNS (nslookup), and those
in cluster by hosts files.
Strange, doesn't it?

Berenice

[Turgay Cavdar]

cmclconfd Client provided hostname xxxx which does not match resolved name xxx.yyy.zzz.com

Hi,
I see this problem on my system as well.The problem was one of the interface subnet mask and the packet ip /subnet mask on that interface was different.So i took the above message. When i correct the subnet mask values, the problem was solved. You can ckeck if this can be applied to your situation...

[Deepak Kr]

Can you provide following:


cat /etc/cmclnodelist
cat /etc/hosts

[skt_skt]

could u post the o/p of ifconfig lanx before and after the change u did. If you have not kept a note then chnage the o/p to accordingly and reply. I nened to chek mine too.