Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infinite restart loop for service when some required mount points are not available on the server #15

Open
loraine-gueguen opened this issue Oct 31, 2022 · 0 comments

Comments

@loraine-gueguen
Copy link
Member

Maybe can be fixed with the following:

The sequenceserver-* services are defined as depending only on network.target:

After=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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant