Closed suikast42 closed 1 year ago
Hi @suikast42! This is a known issue and is being tracked in https://github.com/hashicorp/nomad/issues/16616. I'm going to close this issue as a duplicate and link to it from #16616 so the folks working on that are aware of your logs, just in case that helps. Thanks for reporting this!
After I restart the nomad cluster consul tries to make healthchecks on not existing services.
As I can see in the nomad log, nomad kills an allocation during start and does not deregister it in consul.
The UUID of the dead allocation is df9c5c6e-a682-9014-f2b6-c4dad387b33.
The snippet of nomad log
Restart of the nomad systemd service solves the problem. Then the dead allocations disappears.
This issue comes with the version 1.5.2 a downgrade to 1.5.1 solves the issue as well
Nomad version
Consul version
Nomad and Consul logs
Dead Allocation: df9c5c6e-a682-9014-f2b6-c4dad387b330 New Allocation: 0cafa163-5810-a78e-28dc-e081ebfcded6