Panic: unambiguous timeout | {"InnerError":{"InnerError":{"InnerError":{},"Message":"unambiguous

Hi we are getting below exceptions, Could you please help fix this.

===
panic: unambiguous timeout | {“InnerError”:{“InnerError”:{“InnerError”:{},“Message”:"unambiguous

{“level”:“error”,“msg”:“unambiguous timeout | {“InnerError”:{“InnerError”:{“InnerError”:{},“Message”:“unambiguous timeout”}},“OperationID”:“WaitUntilR │
│ panic: unambiguous timeout | {“InnerError”:{“InnerError”:{“InnerError”:{},“Message”:“unambiguous timeout”}},“OperationID”:“WaitUntilReady”,“Opaque”:””,"TimeObserve │
│ goroutine 1 [running]: │
│ [git.devops.quickplay.com/edge-service-bot/stream-service/pkg/repository.NewCbRepository(0x1a8ef80](http://git.devops.quickplay.com/edge-service-bot/stream-service/pkg/repository.NewCbRepository(0x1a8ef80), 0xc0005300b0, 0xc0001c9dd0) │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/stream-service/pkg/repository/repository_couchbase.go:108 +0x3da │
│ main.initDatabase(0x1a8ef80, 0xc0005300b0, 0xc0001c9ec8, 0x1) │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/stream-service/main.go:96 +0x123 │
│ main.initService() │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/stream-service/main.go:70 +0x333 │
│ main.main() │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/stream-service/main.go:40 +0x76 │
│ stream closed

Hi @prasanpd it looks like the WaitUntilReady command is timing out which means that the SDK cannot connect to the cluster for some reason. If you enable logging (https://docs.couchbase.com/go-sdk/current/howtos/collecting-information-and-logging.html - gocb.VerboseStdioLogger() will give you the most information) then it should give you more information about what’s happening and why the SDK can’t connect.

Hi @chvck , Our go version is 2.1.6. Is WaitUntilReady applicable for this version as well ?

Also, in th UI i see this message.

image

Does it mean something ?

WaitUntilReady was introduced in version 2.1.0 so is applicable to 2.1.6. It’s an operation which you are calling in your code for the above error to contain “OperationID”:“WaitUntilReady”.

Hi @chvck . We enabled the logging you suggested but there is no change in the error logs and dont see any other information pointing to something.

Below is the snippet from logfile :

{“level”:“error”,“msg”:“Error occurred when retrieving username from vault.”,“time”:“2020-10-08T09:36:32Z”} │
│ panic: ErrCbUsernameKeyFailure │
│ goroutine 1 [running]: │
│ [git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository.getUserName(0xaabfa0](http://git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository.getUserName(0xaabfa0), 0xc0000ee0e8, 0xc00026a000, 0x0) │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository/repository_couchbase.go:149 +0x2af │
│ [git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository.NewCbRepository(0xaabfa0](http://git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository.NewCbRepository(0xaabfa0), 0xc0000ee0e8, 0xc0001b7e08) │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/config-service/pkg/repository/repository_couchbase.go:112 +0x169 │
│ main.initDatabase(0xaabfa0, 0xc0000ee0e8, 0xc00002604c, 0x6) │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/config-service/main.go:88 +0x123 │
│ main.initService() │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/config-service/main.go:65 +0x274 │
│ main.main() │
│ /home/jenkins/go/src/git.devops.quickplay.com/edge-service-bot/config-service/main.go:38 +0x76 │
│ stream closed

Hi @prasanpd could you share a code snippet of how you setup the connection with the SDK and enabling logging? The logging output should appear in your stdout, how do you run your application?