Systemd error ubuntu 16

I am currently unable to start seahub using systemd (and as such can’t get it to start on boot)

The error I get from journalctl -xe

Jun 16 12:37:18 SEAFILE systemd[1]: Starting Seafile hub...
-- Subject: Unit seahub.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit seahub.service has begun starting up.
Jun 16 12:37:18 SEAFILE seahub.sh[1969]: Starting seahub at port 8000 ...
Jun 16 12:37:24 SEAFILE seahub.sh[1969]: Seahub is started
Jun 16 12:37:24 SEAFILE seahub.sh[1969]: Done.
Jun 16 12:37:24 SEAFILE seahub.sh[1997]: Stopping seahub ...
Jun 16 12:37:25 SEAFILE seahub.sh[1997]: Done.
Jun 16 12:37:25 SEAFILE systemd[1]: Started Seafile hub.
-- Subject: Unit seahub.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit seahub.service has finished starting up.
--
-- The start-up result is done.

There are no other useful logs I can find. My systemd config is taken directly from the seafile manual.
Running 7.0.2 on ubuntu 16.

Anyone know how to fix this? I can start the server fine using the seahub.sh start command
service seafile start is also working fine too

edit : i did also get the below error but fixed this by making the directory it was looking for

Jun 16 12:36:45 SEAFILE python2.7[1908]: looking for plugins in '/usr/lib64/sasl2', failed to open directory, error: No such file or directory

/etc/systemd/system/seahub.service looks like:

[Unit]
Description=Seafile hub
After=network.target seafile.service

[Service]
# change start to start-fastcgi if you want to run fastcgi
Environment="LC_ALL=C"
ExecStart=/home/seafile/magic/seafile-server-latest/seahub.sh start
ExecStop=/home/seafile/magic/seafile-server-latest/seahub.sh stop
User=seafile
Group=seafile
Type=oneshot
# RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

Found the cause and fix. Firstly needed to reapply the permissions to the data directory
$ sudo chown -R seafile:seafile /path/to/data/dir

Then the unit files were not waiting for the NFS mount to be completed (ie NFS mount was slower than the startup of seafile which caused it to fail)
The fix for this is to add the below to the seafile unit file

After=network.target mnt-FreeNAS.mount

the name needs to be the name of the directory you are mounting (for me its FreeNAS)

Would be useful if someone could add this to the manual for people using NFS mounts?