Hi,
We are using couchbase for one of our application (https://www.skolrup.com) but suddenly it stopped working. We tried to check the connectivity check with sdk-doctor-linux and got invalid bucket name/password. We can use the same credentials from Admin portal. Can you please suggest what could be the issue here?
Logs from SDK -
|====================================================================|
|          ___ ___  _  __   ___   ___   ___ _____ ___  ___           |
|         / |   | |/ /|   \ / _ \ / |   / _ | _ \          |
|         _ \ |) | ’ <| |) | () | (_  | || () |   /          |
|         |//||_\  |/ _/ _| |_| __/||\          |
|                                                                    |
|====================================================================|
Note: Diagnostics can only provide accurate results when your cluster
is in a stable state.  Active rebalancing and other cluster configuration
changes can cause the output of the doctor to be inconsistent or in the
worst cases, completely incorrect.
13:14:27.992 INFO  Parsing connection string
 Parsing connection string couchbase://{IP-ADDRESS}/skolr
13:14:27.992 INFO  Connection string identifies the following CCCP endpoints:
 Connection string identifies the following CCCP endpoints:
13:14:27.992 INFO  1. {IP-ADDRESS}:11210
   1. {IP-ADDRESS}:11210
13:14:27.992 INFO  Connection string identifies the following HTTP endpoints:
 Connection string identifies the following HTTP endpoints:
13:14:27.992 INFO  1. {IP-ADDRESS}:8091
   1. {IP-ADDRESS}:8091
13:14:27.992 INFO  Connection string specifies bucket
 Connection string specifies bucket skolr
13:14:27.992 WARN  Your connection string specifies only a single host.  You should consider adding additional static nodes from your cluster to this list to improve your applications fault-tolerance
 Your connection string specifies only a single host.  You should consider adding additional static nodes from your cluster to this list to improve your applications fault-tolerance
13:14:27.992 INFO  Performing DNS lookup for host
 Performing DNS lookup for host {IP-ADDRESS}
13:14:27.992 INFO  Attempting to connect to cluster via CCCP
 Attempting to connect to cluster via CCCP
13:14:27.992 INFO  Attempting to fetch config via cccp from
 Attempting to fetch config via cccp from {IP-ADDRESS}:11210
13:14:27.997 ERRO  Failed to fetch configuration via cccp from
 Failed to fetch configuration via cccp from 1{IP-ADDRESS}:11210 (error: invalid bucket name/password)
13:14:27.997 INFO  Attempting to connect to cluster via HTTP (Terse)
 Attempting to connect to cluster via HTTP (Terse)
13:14:27.997 INFO  Attempting to fetch terse config via http from
 Attempting to fetch terse config via http from {IP-ADDRESS}:8091
13:14:28.002 ERRO  Failed to fetch terse configuration via http from
 Failed to fetch terse configuration via http from {IP-ADDRESS}:8091 (error: incorrect bucket/password)
13:14:28.002 INFO  Attempting to connect to cluster via HTTP (Full)
 Attempting to connect to cluster via HTTP (Full)
13:14:28.002 INFO  Failed to connect via HTTP (Full), as it is not yet supported by the doctor
 Failed to connect via HTTP (Full), as it is not yet supported by the doctor
13:14:28.002 INFO  Selected the following network type:
 Selected the following network type:
13:14:28.002 ERRO  All endpoints specified by your connection string were unreachable, further cluster diagnostics are not possible
 All endpoints specified by your connection string were unreachable, further cluster diagnostics are not possible
13:14:28.002 INFO  Diagnostics completed
 Diagnostics completed
Summary:
[WARN] Your connection string specifies only a single host.  You should consider adding additional static nodes from your cluster to this list to improve your applications fault-tolerance
[ERRO] Failed to fetch configuration via cccp from {IP-ADDRESS}:11210 (error: invalid bucket name/password)
[ERRO] Failed to fetch terse configuration via http from {IP-ADDRESS}:8091 (error: incorrect bucket/password)
[ERRO] All endpoints specified by your connection string were unreachable, further cluster diagnostics are not possible
