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

Rebooting the computer may render the daemon unusable #2459

Closed
1 of 3 tasks
borellim opened this issue Feb 7, 2019 · 1 comment
Closed
1 of 3 tasks

Rebooting the computer may render the daemon unusable #2459

borellim opened this issue Feb 7, 2019 · 1 comment

Comments

@borellim
Copy link
Member

borellim commented Feb 7, 2019

When rebooting the machine while the daemon is running, the PID file of Circus may not be deleted (.aiida/daemon/circus-<profile>.pid). At the next restart, any "verdi daemon" command will see the PID file and assume that Circus is running, but will fail to connect. Deleting the PID file solves the issue, but we might think of ways to avoid this situation. For instance:

  • Try to catch kill signals sent to Circus during the shutdown process;
  • create an AiiDA system service, at least for popular linux distros (might be already done, see issue how to add aiida daemon system service? #1434);
  • if Circus is not responding when it should, inform the user that they might want to delete the PID file manually, if they are sure that Circus is really not running.
@sphuber
Copy link
Contributor

sphuber commented May 30, 2019

This should now be fixed by PR #2795 if there is a stale PID calling verdi daemon stop will fix it

@sphuber sphuber closed this as completed May 30, 2019
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

2 participants