Infinite restart loop for service when some required mount points are not available on the server #15
Description
Maybe can be fixed with the following:
The sequenceserver-* services are defined as depending only on network.target:
However, if these services use data in directories mounted by NFS and these have a certain latency, in the best case, these services will wait. But in the worst case they will crash and eventually try to restart.
I'm not sure, but by changing the configuration of the services by replacing the After by a RequiresMountsFor and indicating the mount point(s), it could avoid that they try to start when NFS is not operational.