Details
-
Bug
-
Resolution: Fixed
-
Critical
-
7.2.2
-
Untriaged
-
0
-
Unknown
Description
When using cbauth in external mode, if you attempt to initialize cbauth again when the node that was already connected goes away, you will receive errors persistently, making it impossible to reconnect.
{"level":"debug","ts":"2023-12-13T13:34:09.951-0800","logger":"gateway.cbauth","caller":"auth/cbauthauthenticator.go:111","msg":"attempting to establish new cbauth connection","address":"192.168.107.130:8091"}
|
{"level":"debug","ts":"2023-12-13T13:34:09.951-0800","logger":"gateway.cbauth","caller":"auth/cbauthauthenticator.go:131","msg":"successfully connected cbauth to new host","address":"192.168.107.130:8091"}
|
... then later we see the following during/after the rebalance
|
{"level":"debug","ts":"2023-12-13T13:36:00.098-0800","logger":"gateway.cbauth","caller":"auth/cbauthauthenticator.go:111","msg":"attempting to establish new cbauth connection","address":"192.168.107.128:8091"}
|
{"level":"warn","ts":"2023-12-13T13:36:00.098-0800","logger":"gateway.cbauth","caller":"auth/cbauthauthenticator.go:118","msg":"failed to initialize cbauth","error":"close tcp 192.168.107.1:61287->192.168.107.130:8091: use of closed network connection"}
|
It's interesting to note that the error relates to the original node, not the new one we are trying to connect to.
More info is also available here: https://couchbasecloud.atlassian.net/browse/ING-703
Attachments
Issue Links
- relates to
-
ING-701 Loading...