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

Daemon fails to start after being killed #1865

Closed
greschd opened this issue Aug 10, 2018 · 0 comments · Fixed by #2795
Closed

Daemon fails to start after being killed #1865

greschd opened this issue Aug 10, 2018 · 0 comments · Fixed by #2795

Comments

@greschd
Copy link
Member

greschd commented Aug 10, 2018

When killing the daemon and removing the sockets directory given in circus-*.sockets, the damon can no longer start:

$ verdi daemon start
Starting the daemon... FAILED
Try to run 'verdi daemon start --foreground' to potentially see the exception

When called with --foreground it hangs at

$ verdi daemon start --foreground
Starting the daemon... 2018-08-10 02:13:53 circus[17615] [INFO] Starting master on pid 17615
2018-08-10 02:13:53 circus[17615] [INFO] Arbiter now waiting for commands
2018-08-10 02:13:53 circus[17615] [INFO] aiida-default started
2018-08-10 02:13:53 circus[17615] [INFO] circusd-stats started
2018-08-10 02:13:53 circus[17628] [INFO] Starting the stats streamer

I would guess the reason is that the daemon tries to connect on the inexisting sockets, which obviously doesn't work anymore.

It's not a big issue, since obviously it shouldn't happen too often that the daemon is manually SIGKILLed. However, maybe there's an easy solution to prevent this issue? When starting the daemon, can we make a sanity check whether the socket directory exists?

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

Successfully merging a pull request may close this issue.

4 participants