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

Locks are not properly cleaned up when a flow is interrupted with Ctrl-C #116

Open
mpickering opened this issue Sep 21, 2018 · 4 comments
Open

Comments

@mpickering
Copy link
Contributor

I have observed several times that after interrupting a flow that restarting it will lead to no output and the process hanging. I noticed that there were still some lock files which hadn't been deleted in store/lock so I deleted those and things started working again.

@aherrmann
Copy link
Member

@mpickering Did you build your executable with the threaded runtime? As I recall that is necessary for proper Ctrl-C handling.

@mpickering
Copy link
Contributor Author

I wasn't. I will try that now.

@mpickering
Copy link
Contributor Author

Still seems that there are situations when the locks are not cleaned up when compiling with -threaded.

@mpickering
Copy link
Contributor Author

Perhaps there is also a problem with the pending-* files not being cleaned, I found about 400 of these in the store after exiting a run. It seems that these should be cleaned as well? I haven't studied the store model in detail though.

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

No branches or pull requests

3 participants