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

[Sandro Tosi]

On Thu, Mar 17, 2016 at 10:38 AM, Sandro Tosi <morph at debian.org> wrote:
> Hey Felipe,
> thanks for keep looking into this!
>
> On Wed, Mar 16, 2016 at 1:23 PM, Felipe Sateler <fsateler at debian.org> wrote:
>> On 4 March 2016 at 18:13, Sandro Tosi <morph at debian.org> wrote:
>>>> Could you attach one? Or mail me privately if you prefer, and I can
>>>> take a look to see if there is anything else that may be fishy.
>>>
>>> we are extremely protective of what we do on our system, so i am not
>>> able to provide a pristine boot log. I am attaching an anonymized
>>> version of the first minutes of boot, hope that's good enough.
>>
>> I see this that looks possibly interesting:
>>
>> Feb 23 06:50:43 SERVER systemd[1]: Reached target Network is Online.
>> Feb 23 06:50:43 SERVER systemd[1]: Mounting /mnt/NFSSERVER12_VOL...
>> <snip>
>> Feb 23 06:50:43 SERVER systemd[1]: Starting LSB: RPC portmapper replacement...
>> <snip>
>> Feb 23 06:50:43 SERVER systemd[1]: Starting LSB: NFS support files
>> common to client and server...
>> <snip>
>>
>> So it looks like systemd is starting the mounts in parallel to
>> starting the nfs support infrastructure.
>
> uh nice catch!!
>
>> What happens if you add the following content:
>>
>> [Unit]
>> Wants=remote-fs-pre.target
>> Before=remote-fs-pre.target
>>
>> To snippets for nfs-common and rpcbind ? That would be
>> /etc/systemd/system/{nfs-common,rpcbind}.service.d/00-remote-fs-ordering.conf
>>
>> Ensure systemd is picking up the files by issuing a systemctl
>> daemon-reload, and then doing systemctl cat rpcbind nfs-common and
>> making sure the output includes the snippets.
>
> so I created the dirs
> /etc/systemd/system/{nfs-common,rpcbind}.service.d/ , added
> 00-remote-fs-ordering.conf in each of them with the the config you
> suggested, then systemctl daemon-reload then
>
> # systemctl cat rpcbind
> ...
> # /etc/systemd/system/rpcbind.service.d/00-remote-fs-ordering.conf
> [Unit]
> Wants=remote-fs-pre.target
> Before=remote-fs-pre.target
>
> # systemctl cat nfs-common.service
> ...
> # /etc/systemd/system/nfs-common.service.d/00-remote-fs-ordering.conf
> [Unit]
> Wants=remote-fs-pre.target
> Before=remote-fs-pre.target
>
> and I've now set the test machine in a reboot loop until it detects an
> error, I'll let you know what happens

sadly it didnt take long to fail :( (that change still makes sense, so
I'm going to apply it to our systems anyway)

attached is the boot log (anonymized)

thanks for your help!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot.log.2.gz
Type: application/x-gzip
Size: 34733 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160317/54667a51/attachment-0001.bin>