-
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
panic in os/user.Lookup
CGO call
#12342
Comments
Hi @jwz-ecust and thanks for raising this issue. Could you provide any additional details regarding the exact steps you took (commands, APIs etc) to hit this panic? This will help us reproduce the error and fix it up quickly. |
@jrasell v1/jobs and v1/jobs/parse. We request these APIs on the same node (mgt01) in a concurrent way. mgt01 is also the nomad server node. During requests, the nomad collapsed and would recover after. |
Hi @jwz-ecust! @shoenig and I have looked at the stack trace, and it looks like the panic happened while the Nomad node was creating an allocation. The API calls you sent just happened to be sent when that happened and don't look to be related to the problem... just bad luck. The panic happened when the go runtime was making a Linux syscall to lookup the This might be a bug in go, or it might be an unexpected issue in your environment. A few questions:
|
I think we've done what we can with this issue without more information. I'm going to close this out but please feel free to re-open if you have answers to the questions I've asked above. 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
Nomad v1.2.6
Operating system and Environment details
x86 ubuntu
Issue
Nomad collapsed when concurrently requesting nomad API on the same node.
Expected Result
The first request returned 200 and the second returned 200 too.
Actual Result
The first request returned 200 but the second returned 500.
Job file (if appropriate)
Nomad Server logs (if appropriate)
The text was updated successfully, but these errors were encountered: