I have Zoneminder writing to /home/zoneminder and /home is a ZFS mount. If /home/zoneminder doesn't exist, Zoneminder creates it. If anything exists in /home, zfs-mount refuses to mount it. So I want Zoneminder to start after zfs-mount.
I have tried:
After=network.target mysql.service zfs.target
and
After=network.target mysql.service zfs-mount.service
SystemD doesn't seem to take any notice of this, Zoneminder starts before zfs-mount and so /home/ doesn't get mounted.
Requires=zfs-mount.service
SystemD very much takes notice of this. This change causes the system to boot in emergency mode, but I've no idea why. Is there a way to see why emergency mode was chosen?
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[Solved] Start Zoneminder after zfs-mount.service
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Start Zoneminder after zfs-mount.service
Try Wants= and use the journal to investigate.
deadbang
Re: Start Zoneminder after zfs-mount.service
Problem here is actually a bind mount appearing to create the directories, not Zoneminder itself. Bind mounts don't play well with ZFS during boot so special handling is needed. I added "x-systemd.requires=zfs-mount.service" to the bind mount entries in /etc/fstab and now everything is peachy!
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 132 times
Re: Start Zoneminder after zfs-mount.service
OK, good, please add [SOLVED] to the thread title to help others with this problem.
deadbang