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

[Sandro Tosi]

On Tue, Feb 9, 2016 at 7:10 PM, Michael Biebl <biebl at debian.org> wrote:
> Am 09.02.2016 um 19:14 schrieb Sandro Tosi:
>> Hey Michael!
>>
>> On Tue, Feb 9, 2016 at 5:07 PM, Michael Biebl <biebl at debian.org> wrote:
>>> Am 09.02.2016 um 16:40 schrieb Sandro Tosi:
>>>> Hi guys! do you have any idea of what is going on on these machines?
>>>> can you help us fixing it? can we provide more information to pinpoint
>>>> the origin of the issue? thanks!!
>>>
>>> Can you post more details about your network configuration (like your
>>> /etc/network/interfaces).
>>
>> sure here it is:
>>
>> # The loopback network interface
>> auto lo
>> iface lo inet loopback
>>
>> # The primary network interface
>> # eth0 aka admin1
>> auto eth0
>> iface eth0 inet static
>>    address XXX.YYY.54.100
>>    netmask 255.255.252.0
>>    gateway XXX.YYY.52.1
>>    post-up /sbin/ip link set eth0 alias "admin1"
>>
>> can i provide more details? what do you think it would be interesting?
>
>>> Seems like ifplugd is used which is started after systemd has tried to
>>> mount the remote NFS shares.
>>
>> shouldnt that prevent all NFS shares to be mounted and not just one of them?
>
> No idea. Just wondering if ifplugd somehow interferes here. Have you
> tried disabling ifplugd.

I've just disabled it, I'll let the machine run its reboot-loop during
the night and will see in the morning if there is any (positive)
effect.

> 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.

During tests, i managed to let the NFS share mount fail for name
resolution, but it was evident in the log that was the case, with a
"fail to resolve name" (or the similar error message).

Thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi