This post is more than 5 years old
4 Posts
1
6888
Networker Client: A host address mismatch is detected
Hello,
We are currently in the process of installing 8.2.2.0 clients onto our centos 7 and Red Hat 7 boxes. We are at comfortable point but trying to figure out why we are running into a couple of issues. We are running an internal bind server which also happens to be the machine we are placing the client onto. First off we have client 'A' and nsr server 'B', client 'A' uses the internal dns while the nsr server 'B' does not and uses all /etc/hosts configs.
So here are the error logs produced on client 'A'.
03/17/2016 01:52:31 PM 2 1 13 1384093504 3855 0 client'A' nsrexecd SYSTEM warning Cannot resolve host nsrserver'B' to '10.18.1.17', the DNS or client may be misconfigured.
03/17/2016 01:52:31 PM 2 5 0 1056954112 3855 0 client'A' nsrexecd NSR warning A host address mismatch is detected for nsrserver'B''.
We have confirmed that dns works fine, when performing an nslookup on nsrserverB all resolves fine. When pinging all resolves fine. On the nsrserverB side where you have the /etc/hosts configured we have client 'A' within able to ping etc.
We did make a change in /etc/nsswitch.conf
#hosts: db files nisplus nis dns
hosts: dns files myhostname
which fails, so we reverted back to files dns myhostname
The issue is using this setup produces the above logs, however the momment we place 10.18.1.17 nsrserverB into client 'A's /etc/hosts file the issue instantly goes away and we are able to browse it's save set via NMC.
*Additional info*
rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
We have also disabled firewalld throughout these tests, also disabling selinux.
Although we technically have a working client here, can anyone provide any insight into why this implementation only works when Client 'A' has an /etc/hosts entry for nsrserver 'B' even though the dns resolves fine?
Also for reference when installing this we had to create the servers file located in /nsr/res/
Thanks,
Justin
ble1
14.3K Posts
0
March 21st, 2016 05:00
What is says is that gethostbyip() call fails (where IP is 10.18.1.17). So, in some way 10.18.1.17 can't be resolved by DNS (or some name back to it) or what is resolved does not match defined NSR hostname (or one of its aliases). I believe in recent versions DNS check has been added to nsradmin so you can run check there.
jmangino1
4 Posts
0
March 21st, 2016 06:00
Thank you I went back and did some double checks on the DNS and found a typo into the FQDN. Fixing this has fixed the issue. If it it was not for your reverse lookup hint I would not have double checked the reverse lookup thanks again!