Unsolved
This post is more than 5 years old
9 Posts
0
1482
What does this mean (Failed to find matching hostname. Comparing cached IPs)
Hello together,
getting this error message in the server_log "Failed to find matching hostname. Comparing cached IPs"
After raising the NFS log level!!
What cache, is talked about? ARP Cache?
Does any know anything about this message?
Thanks so far.
Kind regards
Andreas
Rainer_EMC
8.6K Posts
0
April 6th, 2011 06:00
Complete message line and a few messages before and after please
AURcrazy2_087b99
9 Posts
0
April 6th, 2011 06:00
1302093776: NFS: 5: Failed to find matching hostname. Comparing cached IPs
1302093776: NFS: 5: last message repeated 3 times
1302093776: NFS: 5: findMatchByIP: Returning on subnet lookup for dxm_FFM and type 0x5.
1302093776: NFS: 5: checkAccess: Netgroup names all_unix,all_FERT,all_anwend,FERT,ICTR_2,ICTR,ICT,rbg_5,rbg,ecad_lic,all_unix,all_FERT,all_anwend,FERT,ICTR_2,ICTR,ICT,rbg_5,rbg,ecad_lic,all_unix,all_FERT,all_anwend,FERT,ICTR_2,ICTR,ICT,rbg_5,rbg,ecad_lic,FERT,ICT,all_anwend,all_FERT,rbg,rbg_5,ICTR,ICTR_2,all_unix,FERT,ICT,all_anwend,all_FERT,rbg,rbg_5,ICTR,ICTR_2,all_unix,FERT,ICT,all_anwend,all_FERT,rbg,rbg_5,ICTR,ICTR_2,all_unix
1302093776: NFS: 5: Got RW access for client 10.215.115.103
1302093776: NFS: 5: Failed to find matching hostname. Comparing cached IPs
1302093776: NFS: 5: findMatchByIP: Returning on subnet lookup for r_mnt and type 0x5.
1302093776: NFS: 5: Failed to find matching hostname. Comparing cached IPs
1302093776: NFS: 5: findMatchByIP: Returning on subnet lookup for cl_rbg and type 0x5.
1302093776: NFS: 5: Failed to find matching hostname. Comparing cached IPs
1302093776: NFS: 5: findMatchByIP: Returning on subnet lookup for TE and type 0x5.
1302093776: NFS: 5: Failed to find matching hostname. Comparing cached IPs
1302093776: NFS: 5: findMatchByIP: Returning on subnet lookup for all_FERT and type 0x5.
nandas
1.5K Posts
0
April 6th, 2011 09:00
It seems to me that NFS access request coming from some hosts which does not have a matching name. Is DNS configured on the data movers? If so, please check whether the host is configured on DNS or not.
On the NFS export Hosts lists, all hosts may be configured with their names - and while validating the hosts for access Celerra logs these messages. You may also specify the IP address of the host instead of the name in the relevant host field and check.
My 2 cents
Sandip
AURcrazy2_087b99
9 Posts
0
April 6th, 2011 22:00
nsswitch.conf --> nis dns files
Helpfull will be, when a hostname or IP adress was displayed in the log.
Only see one, and this host looks fine ( Got RW access for client 10.215.115.103)
So, how can i find out what host have the problem?
Forgot the host access, this is done by netgroups (NIS). And a lot of host access this export, about 1000 hosts.
Thanks so far Sandip.
Kind regards from Germany
Andreas
AURcrazy2_087b99
9 Posts
0
April 7th, 2011 02:00
Thanks Rainer,
for analyse the netstat and showmount helped me to see detailed information.
I have opend a service request.
Thanks to all involved person.
Kind regards Andi
Rainer_EMC
8.6K Posts
1
April 7th, 2011 02:00
Yes – it does look like its coming from a mount or NFS request where the data mover cannot do a reverse lookup to get the hostname from the IP to compare it with the export options
You could try working with support if there is a way to temp. increase the debug level
Or use showmount / netstat / tcpdump to see which clients are connected and then work your way up the exports options and name resolution
Rainer
nandas
1.5K Posts
0
April 7th, 2011 08:00
Hi Andreas,
Thanks for your comments, sorry I could not reply earlier and glad that Rainer also helped you out as much possible.
See you next time ... happy posting
Sandip
Rainer_EMC
8.6K Posts
0
July 7th, 2011 10:00
Hi Andy,
can you share what the service request turned up?
Rainer