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

[Felipe Sateler]

On 25 January 2016 at 09:04, Sandro Tosi <morph at debian.org> wrote:
> Hello,
> we are converting our installations to jessie and we are facing some
> issues, which we believe is somehow related to how systemd boots the
> system, and that they can be summarized as (more details below):
>
> 1. some NFS shares are not mounted at boot
> 2. using 'mount -a' as @reboot cronjob (to workaround 1.) duplicates mounts
> 3. @reboot jobs for programs on NFS mountpoints are started too early
> (when the share is not yet mounted)

I'll try to focus on the original problem first (failed mounts).

>
>
> (1.) we believe that the NFS shares not mounted at boot is also
> causing the other problems, so let's start from this one.
>
> we define our NFS mounts in /etc/fstab like this:
>
> NFS_SERVER:VOLUME    MOUNTPOINT      nfs
> rw,intr,tcp,bg,rdirplus,noatime,_netdev
>
> the mount options are always the same, and we have several of these
> mounts (from different servers), even up to 20 on some hosts.
>
> some of those (not always the same and not on all the machines), are
> not mounted during the boot.

Logs would be helpful (`journalctl -axb` would get you the current boot's logs).

Also, what are you using for networking? Ifupdown? Does `systemctl
status` print failed units?

Without more information on how this is failing (ie, logs), it is very
hard to help.

BTW, be sure to order cron.service after remote-fs.target if your
@reboot commands need those paths available, otherwise cron might run
before they are mounted. This should solve problem 3.


-- 

Saludos,
Felipe Sateler