Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"panic: no valid connect address for host" when establishing a session #1769

Open
john-m-liu opened this issue Jun 10, 2024 · 1 comment
Open

Comments

@john-m-liu
Copy link

Please answer these questions before submitting your issue. Thanks!

What version of Cassandra are you using?

Scylla version 4.6.3

What version of Gocql are you using?

v1.11.0

What version of Go are you using?

1.22.4

What did you do?

call gocql.CreateSession() to connect to my cluster

What did you expect to see?

no error

What did you see instead?

the following panic:

panic: no valid connect address for host: . Is your cluster configured correctly?


If you are having connectivity related issues please share the following additional information

Describe your Cassandra cluster

please provide the following information

  • output of nodetool status
  • output of SELECT peer, rpc_address FROM system.peers
  • rebuild your application with the gocql_debug tag and post the output

On this line in host_source.go, nil is always being passed as the connection address param. That nil connection address will eventually get passed to here, which will panic.

To reproduce, I simply ran the hello world example in https://github.com/gocql/gocql/blob/master/example_test.go and get this panic if I'm on f42e40c or later. The hello world test passes if I'm on a commit earlier than that.

I suspect that I'm missing something obvious because if this is in fact an issue, it should prevent all users from being able to connect with the driver yet I don't see any mention of this issue. I'm encountering this when upgrading the scylla fork of the driver in my app from a version that does not contain this commit to a version that does

@OleksiienkoMykyta
Copy link
Contributor

@john-m-liu, as I understand from (scylladb#191) the issue is on the user's side. Can we close the issue, if it doesn't persist?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants