-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[v0.9.6] Nomad client panics after alloc exec #6728
Comments
Hi again I am able to reproduce it.
if I try to exec in this stopped task it crash nomad-client
If you need more info do not hesitate to contact me. BR |
Thanks for reaching out. It's indeed a bug that was fixed in 0.10.0 by #6065 . Let me know if you have any questions. |
Thank you for your answer. We are going to backport this change to our current version before upgrade to 0.10. Only one question. It is normal that client tried to kill a dead allocation twice? Thanks again |
Anytime!
It's not typical, but possible specially in tight races to kill an allocation. Once it's dead for awhile, I don't expect it to be killed again. Would love to have logs to provide better guidance. |
Yeah, I will open a new issue with all the information that I have. Thanks! |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
v0.9.6
Operating system and Environment details
Amazon Linux 2 - 4.14.146-119.123.amzn2.x86_64
Issue
Panic after alloc exec. This occurs in several nodes and this Issue #6332 kicks in making our services to go to critical state.
Reproduction steps
I can't reproduce it.
Nomad Client logs (if appropriate)
This was the alloc that panics nomad-client.
It is weird that clients tried to kill this alloc several hours after this alloc was Killed.
Can this be related with #6461 ?
BR
The text was updated successfully, but these errors were encountered: