4

autofs hostname lookup failed: Name or service not known

view full story
linux-howto

http://www.linuxquestions.org – I am banging my head against the wall on this one. I am running a debian squeeze server, and have autofs 5.0.4 installed. One of my scripts (autofs executable files) is trying to mount some of my LAN hosts. The host mount fine at start, but when unmounted automatically, it will not mount again. (At least unless I wait for 2-3 minutes). The problem is, maybe, that I get these messages in the log: add_host_addrs: hostname lookup failed: Name or service not known mount(nfs): no hosts available failed to mount {myshare} If I wait a couple of minutes, the share is mounting fine, but that is n (HowTos)

robot1's picture
Submitted by robot1 on 10/26/2010 – Made popular on 10/26/2010

Stories similar to autofs hostname lookup failed: Name or service not known

how to mount nfs using autofs 3 years 36 weeks ago

i just create a nfs server and share a /123 directory , i can successfully mount this share using mount command , but i cant be mount using auto.master (autofs) , so plz guys tell me how can i mount this share using autofs .

thanks In Advance

I have a desktop, server and laptop and NFS4 working fine on all, can mount between one another no prob.

fedora 17 autofs not working 48 weeks 5 days ago

I upgraded from Fedora 16 to Fedora 17 and everything is fine except autofs does not seem to work with nfs drives.

What ports are being used with autofs and nfs? If I have the firewall enable, autofs is not able to mount exported filesystems. With the firewall enabled, I am able to mount the filesystems manually fine. If I disable the firewall, autofs works as expected. When the firewall is enabled, I have nfs set as a trusted service. What other ports do I need to open up?

Started noticing an issues with autofs and don't know when it showed up but it is on both F16 and F17 systems. Have multiple autofs mounts that have been working for years... Literally set them up with FC1.

I have a nfs server (unfortunately v3 but I am working on that), a centos 6.3, a osx 10.7, and a ubuntu 12.10 boxes. I was setting up these machines to access the nfs server. The centos box works fine and I have autofs working on it. I went so far on the osx box to nfs mount the share; still need to do the autofs bit. But, on the 12.10 desktop I seem to have a few issues.

I installed the package nfs-utils and tried it via:

# mount -t nfs server:/mnt /mnt mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified

Ok, probably need to start that - via systemd - right?

# systemctl start nfs-lock.service Job failed.

I have an nfs server running Solaris. It works fine and a large number of clients happily mount directories from it. But only almost all clients.

All clients that have problem run CentOS (5.4 and 5.5). I've found one or two of each version that fail, but also a couple of each version that work.

The mounting is done via autofs but that doesn't seem to make any difference.

I used preupgrade to upgrade to fc17 from 16. All went well after manually installing grub2, yata yata. I've encountered an odd problem, though. I had been using autofs to mount my nfs shares since switching to fedora, since they'd never mount via fstab during bootup. After the upgrade to fc17, if I leave a nautilus window opened in one of the nfs shares managed by autofs, I get a lock up.