-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
invalid memory address or nil pointer dereference #9566
Comments
Thank you for the bug report! We had another report of this in #9482. I've closed that issue so we can track it here. It sounds like this bug exists in 1.9.0 as well. We don't have much of a lead on this yet, we'll need to do some more investigation. Can you tell me more about how you use Consul (ex: for kv, service discovery and/or, connect service mesh) ? |
Greetings 👋 !
We're using the cluster for a mix of SD and Mesh with around ~60 nodes. Let me know if we can help you with more debugging information 🙏 ! Thanks a lot. |
Running in a three node cluster with connect service mesh, ACL disabled, TLS enabled and service discovery. |
Thank you everyone who has reported and provided information about this panic! We have identified the problem and have a couple patches to fix it. There should be a 1.9.2 release very soon which will include the fix. Unfortunately we haven't found any workarounds yet. The bug is triggered when a node is deleted, but it is probably hard to avoid that. Any time an agent is restarted it will perform a node delete. |
We receicently had [a panic in Consul](hashicorp/consul#9566) that was caused by incorrect usage of a ResultIterator. A minimal reproduction of this panic can be seen [here](https://github.com/hashicorp/go-memdb/compare/panic-delete-inside-iter). Many of us learned that there are undocumented rules for using a ResultIterator correct with a write transaction. This commit attempts to document that safe use of a ResultIterator.
We receicently had [a panic in Consul](hashicorp/consul#9566) that was caused by incorrect usage of a ResultIterator. A minimal reproduction of this panic can be seen [here](https://github.com/hashicorp/go-memdb/compare/panic-delete-inside-iter). Many of us learned that there are undocumented rules for using a ResultIterator correct with a write transaction. This commit attempts to document that safe use of a ResultIterator.
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
I want to upgrade from 1.8.6 to 1.9.1 and running into this nil pointer dereference.
Consul info for both Client and Server
OS: Debian 10
Consul: 1.9.1
Log Fragments
Any idea on which data it freaks out?
Cheers,
bert
The text was updated successfully, but these errors were encountered: