search

couchbaselabs / sdk-doctor

Application-server-side cluster connection diagnostics.
https://couchbase.com/
Apache License 2.0
18 stars 12 forks source link

not working with IPv6 address #19

Closed ingenthr closed 5 years ago

ingenthr commented 5 years ago

Failed with: diagnose couchbase://2620:100:10:2024:10:20:30:40/default -u

See more at https://forums.couchbase.com/t/couchbase-5-5-with-ipv6-protocol-family-unavailable/17756/9

 ./sdk-doctor diagnose couchbase://2620:100:10
:2024:10:20:30:40/default
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.

18:13:05.443 INFO ▶ Parsing connection string `couchbase://2620:100:10:2024:10:20:30:40/default`
18:13:05.443 INFO ▶ Connection string identifies the following CCCP endpoints:
18:13:05.443 INFO ▶   1. 2620:100
18:13:05.443 INFO ▶   2. 10:2024
18:13:05.443 INFO ▶   3. 10:20
18:13:05.443 INFO ▶   4. 30:40
18:13:05.443 INFO ▶ Connection string identifies the following HTTP endpoints:
18:13:05.443 INFO ▶ Connection string specifies bucket `default`
18:13:05.443 INFO ▶ Performing DNS lookup for host `2620`
18:13:05.443 INFO ▶ Bootstrap host `2620` refers to a server with the address `0.0.10.60`
18:13:05.443 INFO ▶ Performing DNS lookup for host `10`
18:13:05.443 INFO ▶ Bootstrap host `10` refers to a server with the address `0.0.0.10`
18:13:05.443 INFO ▶ Performing DNS lookup for host `10`
18:13:05.443 INFO ▶ Bootstrap host `10` refers to a server with the address `0.0.0.10`
18:13:05.443 INFO ▶ Performing DNS lookup for host `30`
18:13:05.443 INFO ▶ Bootstrap host `30` refers to a server with the address `0.0.0.30`
18:13:05.443 INFO ▶ Attempting to connect to cluster via CCCP
18:13:05.443 INFO ▶ Attempting to fetch config via cccp from `2620:100`
18:13:05.444 ERRO ▶ Failed to fetch configuration via cccp from `2620:100` (error: dial tcp 0.0.10.60:100: connect: no route to host)
18:13:05.444 INFO ▶ Attempting to fetch config via cccp from `10:2024`
18:13:05.444 ERRO ▶ Failed to fetch configuration via cccp from `10:2024` (error: dial tcp 0.0.0.10:2024: connect: no route to host)
18:13:05.444 INFO ▶ Attempting to fetch config via cccp from `10:20`
18:13:05.444 ERRO ▶ Failed to fetch configuration via cccp from `10:20` (error: dial tcp 0.0.0.10:20: connect: no route to host)
18:13:05.444 INFO ▶ Attempting to fetch config via cccp from `30:40`
18:13:05.444 ERRO ▶ Failed to fetch configuration via cccp from `30:40` (error: dial tcp 0.0.0.30:40: connect: no route to host)
18:13:05.444 INFO ▶ Not attempting HTTP (Terse), as the connection string does not support it
18:13:05.444 INFO ▶ Not attempting HTTP (Full), as the connection string does not support it
18:13:05.444 ERRO ▶ All endpoints specified by your connection string were unreachable, further cluster diagnostics are not possible
18:13:05.444 INFO ▶ Diagnostics completed

Summary:
[ERRO] Failed to fetch configuration via cccp from `2620:100` (error: dial tcp 0.0.10.60:100: connect: no route to host)
[ERRO] Failed to fetch configuration via cccp from `10:2024` (error: dial tcp 0.0.0.10:2024: connect: no route to host)
[ERRO] Failed to fetch configuration via cccp from `10:20` (error: dial tcp 0.0.0.10:20: connect: no route to host)
[ERRO] Failed to fetch configuration via cccp from `30:40` (error: dial tcp 0.0.0.30:40: connect: no route to host)
[ERRO] All endpoints specified by your connection string were unreachable, further cluster diagnostics are not possible
brett19 commented 5 years ago

Should be fixed by #20