NFS mounts - temporary failure in name resolution [solved]

[Steve Searle]

Around 04:30pm on Saturday, June 19, 2010 (UK time), Tom Horsley scrawled:

> On Sat, 19 Jun 2010 16:03:44 +0100
> Steve Searle wrote:
> 
> > Does anyone have any ideas?
> 
> Does this machine also run bind as a local nameserver?
> I found that the first lookups I do during boot always
> fail. I assume because bind takes "too long" to get
> started and prime the cache (or something :-).

No - it uses another machine as a nameserver. However editing /etc/fstab
to use ip addresses produces "mount.nfs: Failed to resolve server
192.168.126.151: Address family for hostname not supported" messages.
Again these usually happen on bootup, but not always.


Around 04:45pm on Saturday, June 19, 2010 (UK time), Doron Bar Zeev scrawled:

> Are you using NetworkManager?

Yes.

> I switched to using the network service instead which fixed the problem.

Good call. I tried this and it seems to have solved the problem. But
because I wanted to keep using NetworkManager (I occiasionally use
wireless on these) I changed back to NetworkManager and added a "sleep
10" to the end of the start part of the init.d script. A bit of a kludge
but it seems to have sorted it.

Cheers

Steve

-- 
 
(o<     www.stevesearle.com
//\     Powered by Fedora
V_/_    No MS products were used in the creation of this message

 17:07:54 up 32 days, 20:16,  1 user,  load average: 0.07, 0.02, 0.00
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20100619/2f7234a9/attachment.bin