Nil Pointer exception on consul restart #160
Comments
|
Looks like a nil dereference during a shutdown. Thanks for the report! |
duckhan
pushed a commit
to duckhan/consul
that referenced
this issue
Oct 24, 2021
…corp#160) * When true, sync catalog process will append k8s namespace of services it's syncing to Consul, separated by a dash. E.g. for a service 'foo' in the 'default' namespace, it will register a Consul service called 'foo-default'. A dash delimiter doesn't eliminate name collisions completely (e.g. `foo-bar-baz` could be service `foo` in the `bar-baz` namespace or service `foo-bar` in the `baz` namespace), but it provides sufficient protection against the most common/obvious naming collisions. * True by default * Add tests for the sync-catalog command and separate common test helper functions into a shared package.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Link to logs: https://gist.github.com/tarrant/fbc52bdef3583b1c77be
While restarting our consul servers one by one I had a consul server fail to come up. I've attached a copy of the logs. A subsequent start worked fine.
Consul is built with commit baa831d
The text was updated successfully, but these errors were encountered: