question

igor.rmarinho_185445 avatar image
igor.rmarinho_185445 asked Erick Ramirez edited

Why am I getting authentication errors with DSBulk?

Hi,

I'm running Dsbulk as below and I'm getting a lot authentication errors/Warns as below. Is some config missing?

dsbulk count -u  cassandra  -p cassandra -k keyspace -t table
Username and password provided but auth provider not specified, inferring PlainTextAuthProvider
Operation directory: /etc/logs/COUNT_20201019-182047-849687
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /127.0.0.1:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.4:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
[driver] /10.15.25.3:9042 did not send an authentication challenge; This is suspicious because the driver expects authentication
dsbulk
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

2 Answers

Erick Ramirez avatar image
Erick Ramirez answered Erick Ramirez edited

As the messages suggest, you have provided a username and password but the cluster you connected to does not have authentication enabled.

The embedded Java driver in DSBulk is reporting those messages because it was expecting the nodes in the cluster to challenge it with authentication credentials but it wasn't the case. Another way of putting it is that it was expecting the nodes to request a username and password since you provided them but the driver didn't get challenged for the credentials.

Interestingly, I've noted messages from both localhost (127.0.0.1) and nodes in the 10.15.25.x subnet. I suspect you didn't intend to connect to localhost.

I would suggest that you specify the contact list (nodes to connect to) using the -h option. You will need to specify at least one node as an array of comma-delimited strings. For example:

$ dsbulk count -h '["10.15.25.1:9042", "10.15.25.2:9042"]' -k ks_name -t table_name

For more information, see the DSBulk Driver options page. Cheers!

Share
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

smadhavan avatar image
smadhavan answered smadhavan commented

@igor.rmarinho_185445, could you post the output of running ./dsbulk --version?

Here is what you need instead,

dsbulk count -h hostname_or_ip -k keyspace_name -t table_name -u user_name -p user_password

Other Resources:

p/s: If you still end up getting the warning, please add --dsbulk.log.verbosity 2 to the same command and upload the results from the files that are available in the Operation directory: /path/to/logs/COUNT_* directory.

4 comments Share
10 |1000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 8 attachments (including images) can be used with a maximum of 1.0 MiB each and 10.0 MiB total.

igor.rmarinho_185445 avatar image igor.rmarinho_185445 commented ·

it still happening even using -h


dsbulk.txt

0 Likes 0 ·
dsbulk.txt (13.3 KiB)
smadhavan avatar image smadhavan ♦ igor.rmarinho_185445 commented ·

@igor.rmarinho_185445, first this is just a warning message and the output of the count operation completes successfully. Also, as Erik already stated above in his response, does this cluster not have any authentication enabled and you're still supplying the credentials via the DSBulk count command?

As messages suggest, you have provided a username and password but the cluster you connected to does not have authentication enabled.

Did you check what you have in the dse.yaml file under authentication_options section for the three nodes of this cluster?

1 Like 1 ·
igor.rmarinho_185445 avatar image igor.rmarinho_185445 smadhavan ♦ commented ·

True! I environment was rebuilt and the authentication was missing in dse.yaml

Thanks!

0 Likes 0 ·
Show more comments