You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@dcarbone Very sorry that this occurred in your cluster. We have identified the cause being that the monitor http endpoint not handling running on client and causing the panic. The bug exists in both 0.10.2 and 0.10.3. I would recommend avoiding hitting /v1/agent/monitor endpoint on clients for now.
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.
Nomad version
1.10.3
Operating system and Environment details
Issue
We are reliably seeing panics from nomad clients on boot, unsure of specific root cause.
Will add more details once we finish rollback to 10.2.
Reproduction steps
Unclear at this time
Nomad Client logs
The panic is seen across all 3 clients, and afterwards they may become unresponsive.
The text was updated successfully, but these errors were encountered: