jessie: help debugging NFS shares not mounted at boot, double mounts with mount -a, and @reboot cronjobs

[Michael Biebl]

Am 09.02.2016 um 22:11 schrieb Sandro Tosi:
>> Another idea: maybe it's related to name resolution. How is that
>> configured? Does it help if you use IP adresses in /etc/fstab?
> 
> # cat /etc/resolv.conf
> search OUR-DOMAIN.com
> nameserver 127.0.0.1
> nameserver XXX.YYY.32.33
> nameserver XXX.YYY.32.22
> options no_tld_query
> 
> on localhost we have unbound as dns cache with this config
> 
> # cat /etc/unbound/unbound.conf
> server:
>        val-permissive-mode: yes
>        local-zone: "10.in-addr.arpa" nodefault
> forward-zone:
>        name: .
>        forward-addr: XXX.YYY.32.33
>        forward-addr: XXX.YYY.32.22
> remote-control:
>        control-enable: yes
> 
> the NFS storage appliance we are using is configured to have a
> multiple ip addresses to resolve to the same domain name, and it
> automatically balances connections between clients providing different
> ip addresses, so we cannot change that.

For testing purposes, it should be possible to configure one client to
use a fixed IP address in /etc/fstab. If the mount then doesn't fail,
you have narrowed down the problem then at least.

As a next step, I would remove the caching server from /etc/resolv.conf
and let the system talk directly to your name server(s) which are
responsible for resolving the name of the NFS server and retry with a
FQDN in /etc/fstab.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160209/d47ab778/attachment-0002.sig>