System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

match_addr: getaddrinfo failed: host nor service provided, or not known

 
Highlighted
Regular Advisor

match_addr: getaddrinfo failed: host nor service provided, or not known

Hi,

Please some one help me to identify the following error message

automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known

automountd is running . Alos this is a cluster machine and the hanfs is also running
ps -ef | grep -i auto
root 78 0 0 Jan 9 ? 0:03 autofskd
root 3877 1 0 Jan 9 ? 28:51 /usr/sbin/automountd -L
root 20965 20915 0 15:48:20 pts/0 0:00 grep -i auto

cat /etc/auto_master
/net -hosts -nosuid,soft,nobrowse
/- /etc/auto.direct

also under /net directory nothing is there
Under /etc/auto.direct filesystems are mentioned which need to share with hsnfs

But I could not identify the error message , Its repeating daily

7 REPLIES 7
Highlighted
Acclaimed Contributor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

Since you have /net in auto_master, that means that anyone can do:
ll /net/IP-address or /net/machine-name

So does "ll /net/foobar2" cause one of these errors?

So do you have an automated process that is referring to an unknown machine?
I've had symlinks to /net/machine which had been long since decommissioned and would temporarily hang on them when doing "ls -F".
Highlighted
Regular Advisor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

Hi Dennis,

There is no machine name or IP defined under /net . Also the ls -F is not hung
root@:/net>
ls -F
root@:/net> ll /net
total 0
root@:/net>

Highlighted
Acclaimed Contributor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

>There is no machine name or IP defined under /net. Also the ls -F is not hung

There won't be because that machine doesn't exist to mount and still be there to see.
That "ls -F" hang could be hidden anywhere in any filesystem.

So you may need to find a connection between when the error occurs and some automatic (cron) or manual process.
Highlighted
Regular Advisor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

But , Could you please tell me how to find this
Becasue the errro is repeating every second

Feb 5 20:00:40 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:01:11 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:01:11 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:02:20 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:02:20 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:16:11 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 20:16:11 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 23:07:53 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 23:07:53 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Feb 5 23:14:22 automountd[3877]: match_addr: getaddrinfo failed: host nor service provided, or not known
Highlighted
Acclaimed Contributor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

>Because the error is repeating every second

Hmm. You may have to restart the automounter.
Do you have your networking set up correctly? Any recent changes there?
Highlighted
Regular Advisor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

No change happened recently
Highlighted
Honored Contributor

Re: match_addr: getaddrinfo failed: host nor service provided, or not known

Might be a good idea to fire-up the support contract and file a defect against the automounter - at the least it should be including *which* name it is unable to lookup.

In the meantime, you might be able to gather a clue as to the name involved with either a rather verbose tusc trace, or perhaps a tcpdump trace of port 53 traffic from the machine, correlated back with the timestamps of the error messages.
there is no rest for the wicked yet the virtuous have no pillows