-
Notifications
You must be signed in to change notification settings - Fork 880
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: runtime error: invalid memory address or nil pointer dereference (maybe when another cluster node is removed) #985
Comments
I hit something really similar while attempting to set up host discovery with UCP/Swarm. I was doing some crazy stuff to try and diagnose a problem with host discovery, so I'm not exactly sure what triggered it. It could be that I updated the clock, upgraded the engine or even messed around with the TLS certs. `panic: runtime error: invalid memory address or nil pointer dereference goroutine 1548 [running]: goroutine 1 [chan receive, 81 minutes]: goroutine 17 [syscall, 84 minutes, locked to thread]: |
Join & Leave Serf processing happens in a separate goroutine and there are cases as in moby#985, it can cause lookup failures when endpoint delete processing happens before Serf gets a chance to handle the leave processing. The fix is to avoid such lookups in this goroutine, but handle the endpoint and network objects directly. Signed-off-by: Madhu Venugopal <madhu@docker.com>
Join & Leave Serf processing happens in a separate goroutine and there are cases as in #985, it can cause lookup failures when endpoint delete processing happens before Serf gets a chance to handle the leave processing. The fix is to avoid such lookups in this goroutine, but handle the endpoint and network objects directly. Signed-off-by: Madhu Venugopal <madhu@docker.com>
- Fixes moby/libnetwork#1051 - Fixes moby/libnetwork#985 - Fixes moby/libnetwork#945 - Log time taken to set sandbox key - Limit number of concurrent DNS queries Signed-off-by: Madhu Venugopal <madhu@docker.com>
- Fixes moby/libnetwork#1051 - Fixes moby/libnetwork#985 - Fixes moby/libnetwork#945 - Log time taken to set sandbox key - Limit number of concurrent DNS queries Signed-off-by: Madhu Venugopal <madhu@docker.com> (cherry picked from commit 90bb530)
I just experienced the following crash of my engine.
It looks like this happens has I forcibly removed another node from the cluster (essentially I powercycled
node3
and noticed that I had lost my Swarm leader, even thoughnode3
was not leader at that time; then I noticed that I had lostnode2
: the Engine had crashed).Full log is attached. I'll add details if it happens again (I'm doing a lot of chaos-monkey style failures so maybe it'll happen again...)
docker.log.txt
The text was updated successfully, but these errors were encountered: