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

Nomad 0.9.3 multiple panics #6063

Closed
scalp42 opened this issue Aug 1, 2019 · 4 comments · Fixed by #6065
Closed

Nomad 0.9.3 multiple panics #6063

scalp42 opened this issue Aug 1, 2019 · 4 comments · Fixed by #6065

Comments

@scalp42
Copy link
Contributor

scalp42 commented Aug 1, 2019

Nomad version

Output from nomad version

Operating system and Environment details

Ubuntu 18.04

Issue

I saw the symptom live: the deployment (1 container) was in progress in the UI, reporting the one container unhealthy but Consul service checks were passing.

Reproduction steps

Apparently, the container was unhealthy during the deployment and one of our engineers clicked restart during the deployment itself. Might not be related.

Job file (if appropriate)

https://gist.github.com/scalp42/4c3cec1149be1612f82e385ea3433f0e

Nomad Client logs (if appropriate)

https://gist.github.com/scalp42/70ca6217e96982dd574c188f3829c93c

Nomad Server logs (if appropriate)

Could not find anything on servers.

@endocrimes
Copy link
Contributor

@scalp42 Thanks for reporting - If I'm reading the logs correctly, it look like the panic occured while somebody was trying to nomad alloc exec a command while it was starting up?

@scalp42
Copy link
Contributor Author

scalp42 commented Aug 2, 2019

Hi @endocrimes, I'm asking the engineer, trying to gather as much info as I can.

@scalp42
Copy link
Contributor Author

scalp42 commented Aug 2, 2019

Per the engineer, they didn't 🤷‍♂

@github-actions
Copy link

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants