Re: Failure when setting up cassandra in cluster

[Raimund Klein]

Hi Ricardo,

Thank you, the nodes are indeed configured like this. /etc/hosts contains
both the line you mention AND another one with the general IP. But both
with the nodes' names. Guess it's time to ask our responsible guys why this
is the case.

At least now I know what to look for. I'll play around with this
configuration line and see if I can get it to work.

Again, thank you for the help.

Cheers
Raimund

2016-08-22 17:32 GMT+01:00 Riccardo Ferrari :

> Hi that's very likely because of:
>>
>> empty the listen_address entry
>
> and
>
> # Leaving it blank leaves it up to InetAddress.getLocalHost(). This
>
> # will always do the Right Thing _if_ the node is properly configured
>
> # (hostname, name resolution, etc), and the Right Thing is to use the
> # address associated with the hostname (it might not be).
>
> You probably have na /etc/hosts line that is
> 127.0.1.1 myhostname
>
>  Nodes can not communicate if bound to loopback interface
> Best,
>
> On Mon, Aug 22, 2016 at 6:22 PM, Raimund Klein 
> wrote:
>
>> Hi guys,
>>
>> Thanks for the responses. I'm running the cqlsh commands directly on one
>> of the nodes, so should that really make a difference?
>>
>> Anyway, as for Carlos' questions:
>>
>> - We're using Cassandra 2.2.6.
>> - nodetool status on first node:
>>
>> Datacenter: datacenter1
>>
>> ===
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   Owns (effective)  Host ID
>>   Rack
>>
>> UN  127.0.1.1  168.6 KB   256  100.0%
>> 7217530d-1db4-4208-b181-f627546ed386  rack1
>>
>> - nodetool status on second node:
>>
>> Datacenter: datacenter1
>>
>> ===
>>
>> Status=Up/Down
>>
>> |/ State=Normal/Leaving/Joining/Moving
>>
>> --  AddressLoad   Tokens   Owns (effective)  Host ID
>>   Rack
>>
>> UN  127.0.1.1  128.35 KB  256  100.0%
>> 46917945-6f5d-4f94-b48a-d7cbbd94110f  rack1
>>
>>
>> Cheers
>>
>> Riamund
>>
>> 2016-08-22 16:23 GMT+01:00 Carlos Rolo :
>>
>>> If Ryan answer doesn't help, post Cassandra version. There is a bug with
>>> cql and some python version that would lead to that error.
>>>
>>> Also, please post "nodetool status".
>>>
>>> Regards,
>>>
>>> Carlos Juzarte Rolo
>>> Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
>>>
>>> Pythian - Love your data
>>>
>>> rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
>>> *linkedin.com/in/carlosjuzarterolo
>>> *
>>> Mobile: +351 918 918 100
>>> www.pythian.com
>>>
>>> On Mon, Aug 22, 2016 at 4:08 PM, Ryan Svihla  wrote:
>>>
 instead of 127.0.0.1 have you tried just passing the IP of the one of
 the nodes.

 On Mon, Aug 22, 2016 at 9:45 AM Raimund Klein 
 wrote:

> Hello all,
>
> Sorry for reposting this, but I didn't receive any response. Can
> someone help please?
>
> -- Forwarded message --
> From: Raimund Klein 
> Date: 2016-08-15 12:07 GMT+01:00
> Subject: Failure when setting up cassandra in cluster
> To: user@cassandra.apache.org
>
>
> Hi all,
>
> Sorry if this is a fairly stupid question, but we've all only been
> exposed to Cassandra very recently.
>
> We're trying to configure a 2-node cluster with non-default
> credentials. Here's what I've been doing so far based on my understanding
> of the documentation. The platform is RHEL 7:
>
>
>1. Use an RPM I found with Datastax to perform a basic cassandra
>installation.
>2. Change the temporary directory in cassandra-env.sh, because
>nobody is allowed to execute anything in /tmp.
>3. In cassandra.yaml,
>- change the cluster_name
>- empty the listen_address entry
>- define both VMs as seeds
>4. Open port 7000 in the firewall.
>5. Start cassandra.
>6. In the cassandra.yaml, change to PasswordAuthenticator.
>7. Run cqlsh -u cassandra -p cassandra -e "ALTER KEYSPACE
>system_auth WITH REPLICATION = { 'class' : 'SimpleStrategy',
>'replication_factor' : 2 };"
>8. Restart cassandra
>9. Perform 1-8 on the second node
>10. To create a new user, run cqlsh -u cassandra -p cassandra
>-e "CREATE USER ${CASSANDRA_USERNAME} WITH PASSWORD 
> '${CASSANDRA_PASSWORD}'
>SUPERUSER;"
>
> Step 10 fails with this error:
>
> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> AuthenticationFailed(u'Failed to authenticate to 127.0.0.1: code=0100
> [Bad credentials] message="org.apache.cassandra.
> exceptions.UnavailableException: Cannot achieve consistency level
> QUORUM"',)})
>
>
> What am I missing?
>
>
> 

Re: Failure when setting up cassandra in cluster

[Riccardo Ferrari]

Hi that's very likely because of:
>
> empty the listen_address entry

and

# Leaving it blank leaves it up to InetAddress.getLocalHost(). This

# will always do the Right Thing _if_ the node is properly configured

# (hostname, name resolution, etc), and the Right Thing is to use the
# address associated with the hostname (it might not be).

You probably have na /etc/hosts line that is
127.0.1.1 myhostname

 Nodes can not communicate if bound to loopback interface
Best,

On Mon, Aug 22, 2016 at 6:22 PM, Raimund Klein  wrote:

> Hi guys,
>
> Thanks for the responses. I'm running the cqlsh commands directly on one
> of the nodes, so should that really make a difference?
>
> Anyway, as for Carlos' questions:
>
> - We're using Cassandra 2.2.6.
> - nodetool status on first node:
>
> Datacenter: datacenter1
>
> ===
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   Owns (effective)  Host ID
> Rack
>
> UN  127.0.1.1  168.6 KB   256  100.0%
> 7217530d-1db4-4208-b181-f627546ed386  rack1
>
> - nodetool status on second node:
>
> Datacenter: datacenter1
>
> ===
>
> Status=Up/Down
>
> |/ State=Normal/Leaving/Joining/Moving
>
> --  AddressLoad   Tokens   Owns (effective)  Host ID
> Rack
>
> UN  127.0.1.1  128.35 KB  256  100.0%
> 46917945-6f5d-4f94-b48a-d7cbbd94110f  rack1
>
>
> Cheers
>
> Riamund
>
> 2016-08-22 16:23 GMT+01:00 Carlos Rolo :
>
>> If Ryan answer doesn't help, post Cassandra version. There is a bug with
>> cql and some python version that would lead to that error.
>>
>> Also, please post "nodetool status".
>>
>> Regards,
>>
>> Carlos Juzarte Rolo
>> Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
>>
>> Pythian - Love your data
>>
>> rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
>> *linkedin.com/in/carlosjuzarterolo
>> *
>> Mobile: +351 918 918 100
>> www.pythian.com
>>
>> On Mon, Aug 22, 2016 at 4:08 PM, Ryan Svihla  wrote:
>>
>>> instead of 127.0.0.1 have you tried just passing the IP of the one of
>>> the nodes.
>>>
>>> On Mon, Aug 22, 2016 at 9:45 AM Raimund Klein 
>>> wrote:
>>>
 Hello all,

 Sorry for reposting this, but I didn't receive any response. Can
 someone help please?

 -- Forwarded message --
 From: Raimund Klein 
 Date: 2016-08-15 12:07 GMT+01:00
 Subject: Failure when setting up cassandra in cluster
 To: user@cassandra.apache.org


 Hi all,

 Sorry if this is a fairly stupid question, but we've all only been
 exposed to Cassandra very recently.

 We're trying to configure a 2-node cluster with non-default
 credentials. Here's what I've been doing so far based on my understanding
 of the documentation. The platform is RHEL 7:


1. Use an RPM I found with Datastax to perform a basic cassandra
installation.
2. Change the temporary directory in cassandra-env.sh, because
nobody is allowed to execute anything in /tmp.
3. In cassandra.yaml,
- change the cluster_name
- empty the listen_address entry
- define both VMs as seeds
4. Open port 7000 in the firewall.
5. Start cassandra.
6. In the cassandra.yaml, change to PasswordAuthenticator.
7. Run cqlsh -u cassandra -p cassandra -e "ALTER KEYSPACE
system_auth WITH REPLICATION = { 'class' : 'SimpleStrategy',
'replication_factor' : 2 };"
8. Restart cassandra
9. Perform 1-8 on the second node
10. To create a new user, run cqlsh -u cassandra -p cassandra
-e "CREATE USER ${CASSANDRA_USERNAME} WITH PASSWORD 
 '${CASSANDRA_PASSWORD}'
SUPERUSER;"

 Step 10 fails with this error:

 Connection error: ('Unable to connect to any servers', {'127.0.0.1':
 AuthenticationFailed(u'Failed to authenticate to 127.0.0.1: code=0100
 [Bad credentials] message="org.apache.cassandra.
 exceptions.UnavailableException: Cannot achieve consistency level
 QUORUM"',)})


 What am I missing?


 Cheers

 Raimund


 --
>>> Regards,
>>>
>>> Ryan Svihla
>>>
>>
>>
>> --
>>
>>
>>
>>
>

Re: Failure when setting up cassandra in cluster

[Raimund Klein]

Hi guys,

Thanks for the responses. I'm running the cqlsh commands directly on one of
the nodes, so should that really make a difference?

Anyway, as for Carlos' questions:

- We're using Cassandra 2.2.6.
- nodetool status on first node:

Datacenter: datacenter1

===

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  AddressLoad   Tokens   Owns (effective)  Host ID
Rack

UN  127.0.1.1  168.6 KB   256  100.0%
7217530d-1db4-4208-b181-f627546ed386  rack1

- nodetool status on second node:

Datacenter: datacenter1

===

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  AddressLoad   Tokens   Owns (effective)  Host ID
Rack

UN  127.0.1.1  128.35 KB  256  100.0%
46917945-6f5d-4f94-b48a-d7cbbd94110f  rack1


Cheers

Riamund

2016-08-22 16:23 GMT+01:00 Carlos Rolo :

> If Ryan answer doesn't help, post Cassandra version. There is a bug with
> cql and some python version that would lead to that error.
>
> Also, please post "nodetool status".
>
> Regards,
>
> Carlos Juzarte Rolo
> Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
>
> Pythian - Love your data
>
> rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
> *linkedin.com/in/carlosjuzarterolo
> *
> Mobile: +351 918 918 100
> www.pythian.com
>
> On Mon, Aug 22, 2016 at 4:08 PM, Ryan Svihla  wrote:
>
>> instead of 127.0.0.1 have you tried just passing the IP of the one of the
>> nodes.
>>
>> On Mon, Aug 22, 2016 at 9:45 AM Raimund Klein 
>> wrote:
>>
>>> Hello all,
>>>
>>> Sorry for reposting this, but I didn't receive any response. Can someone
>>> help please?
>>>
>>> -- Forwarded message --
>>> From: Raimund Klein 
>>> Date: 2016-08-15 12:07 GMT+01:00
>>> Subject: Failure when setting up cassandra in cluster
>>> To: user@cassandra.apache.org
>>>
>>>
>>> Hi all,
>>>
>>> Sorry if this is a fairly stupid question, but we've all only been
>>> exposed to Cassandra very recently.
>>>
>>> We're trying to configure a 2-node cluster with non-default credentials.
>>> Here's what I've been doing so far based on my understanding of the
>>> documentation. The platform is RHEL 7:
>>>
>>>
>>>1. Use an RPM I found with Datastax to perform a basic cassandra
>>>installation.
>>>2. Change the temporary directory in cassandra-env.sh, because
>>>nobody is allowed to execute anything in /tmp.
>>>3. In cassandra.yaml,
>>>- change the cluster_name
>>>- empty the listen_address entry
>>>- define both VMs as seeds
>>>4. Open port 7000 in the firewall.
>>>5. Start cassandra.
>>>6. In the cassandra.yaml, change to PasswordAuthenticator.
>>>7. Run cqlsh -u cassandra -p cassandra -e "ALTER KEYSPACE
>>>system_auth WITH REPLICATION = { 'class' : 'SimpleStrategy',
>>>'replication_factor' : 2 };"
>>>8. Restart cassandra
>>>9. Perform 1-8 on the second node
>>>10. To create a new user, run cqlsh -u cassandra -p cassandra
>>>-e "CREATE USER ${CASSANDRA_USERNAME} WITH PASSWORD 
>>> '${CASSANDRA_PASSWORD}'
>>>SUPERUSER;"
>>>
>>> Step 10 fails with this error:
>>>
>>> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
>>> AuthenticationFailed(u'Failed to authenticate to 127.0.0.1: code=0100
>>> [Bad credentials] message="org.apache.cassandra.
>>> exceptions.UnavailableException: Cannot achieve consistency level
>>> QUORUM"',)})
>>>
>>>
>>> What am I missing?
>>>
>>>
>>> Cheers
>>>
>>> Raimund
>>>
>>>
>>> --
>> Regards,
>>
>> Ryan Svihla
>>
>
>
> --
>
>
>
>

Re: Failure when setting up cassandra in cluster

[Carlos Rolo]

If Ryan answer doesn't help, post Cassandra version. There is a bug with
cql and some python version that would lead to that error.

Also, please post "nodetool status".

Regards,

Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP

Pythian - Love your data

rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
*linkedin.com/in/carlosjuzarterolo
*
Mobile: +351 918 918 100
www.pythian.com

On Mon, Aug 22, 2016 at 4:08 PM, Ryan Svihla  wrote:

> instead of 127.0.0.1 have you tried just passing the IP of the one of the
> nodes.
>
> On Mon, Aug 22, 2016 at 9:45 AM Raimund Klein 
> wrote:
>
>> Hello all,
>>
>> Sorry for reposting this, but I didn't receive any response. Can someone
>> help please?
>>
>> -- Forwarded message --
>> From: Raimund Klein 
>> Date: 2016-08-15 12:07 GMT+01:00
>> Subject: Failure when setting up cassandra in cluster
>> To: user@cassandra.apache.org
>>
>>
>> Hi all,
>>
>> Sorry if this is a fairly stupid question, but we've all only been
>> exposed to Cassandra very recently.
>>
>> We're trying to configure a 2-node cluster with non-default credentials.
>> Here's what I've been doing so far based on my understanding of the
>> documentation. The platform is RHEL 7:
>>
>>
>>1. Use an RPM I found with Datastax to perform a basic cassandra
>>installation.
>>2. Change the temporary directory in cassandra-env.sh, because nobody
>>is allowed to execute anything in /tmp.
>>3. In cassandra.yaml,
>>- change the cluster_name
>>- empty the listen_address entry
>>- define both VMs as seeds
>>4. Open port 7000 in the firewall.
>>5. Start cassandra.
>>6. In the cassandra.yaml, change to PasswordAuthenticator.
>>7. Run cqlsh -u cassandra -p cassandra -e "ALTER KEYSPACE system_auth
>>WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 2
>>};"
>>8. Restart cassandra
>>9. Perform 1-8 on the second node
>>10. To create a new user, run cqlsh -u cassandra -p cassandra
>>-e "CREATE USER ${CASSANDRA_USERNAME} WITH PASSWORD 
>> '${CASSANDRA_PASSWORD}'
>>SUPERUSER;"
>>
>> Step 10 fails with this error:
>>
>> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
>> AuthenticationFailed(u'Failed to authenticate to 127.0.0.1: code=0100
>> [Bad credentials] 
>> message="org.apache.cassandra.exceptions.UnavailableException:
>> Cannot achieve consistency level QUORUM"',)})
>>
>>
>> What am I missing?
>>
>>
>> Cheers
>>
>> Raimund
>>
>>
>> --
> Regards,
>
> Ryan Svihla
>

-- 


--

Re: Failure when setting up cassandra in cluster

[Ryan Svihla]

 instead of 127.0.0.1 have you tried just passing the IP of the one of the
nodes.

On Mon, Aug 22, 2016 at 9:45 AM Raimund Klein  wrote:

> Hello all,
>
> Sorry for reposting this, but I didn't receive any response. Can someone
> help please?
>
> -- Forwarded message --
> From: Raimund Klein 
> Date: 2016-08-15 12:07 GMT+01:00
> Subject: Failure when setting up cassandra in cluster
> To: user@cassandra.apache.org
>
>
> Hi all,
>
> Sorry if this is a fairly stupid question, but we've all only been exposed
> to Cassandra very recently.
>
> We're trying to configure a 2-node cluster with non-default credentials.
> Here's what I've been doing so far based on my understanding of the
> documentation. The platform is RHEL 7:
>
>
>1. Use an RPM I found with Datastax to perform a basic cassandra
>installation.
>2. Change the temporary directory in cassandra-env.sh, because nobody
>is allowed to execute anything in /tmp.
>3. In cassandra.yaml,
>- change the cluster_name
>- empty the listen_address entry
>- define both VMs as seeds
>4. Open port 7000 in the firewall.
>5. Start cassandra.
>6. In the cassandra.yaml, change to PasswordAuthenticator.
>7. Run cqlsh -u cassandra -p cassandra -e "ALTER KEYSPACE system_auth
>WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 2
>};"
>8. Restart cassandra
>9. Perform 1-8 on the second node
>10. To create a new user, run cqlsh -u cassandra -p cassandra
>-e "CREATE USER ${CASSANDRA_USERNAME} WITH PASSWORD '${CASSANDRA_PASSWORD}'
>SUPERUSER;"
>
> Step 10 fails with this error:
>
> Connection error: ('Unable to connect to any servers', {'127.0.0.1':
> AuthenticationFailed(u'Failed to authenticate to 127.0.0.1: code=0100
> [Bad credentials]
> message="org.apache.cassandra.exceptions.UnavailableException: Cannot
> achieve consistency level QUORUM"',)})
>
>
> What am I missing?
>
>
> Cheers
>
> Raimund
>
>
> --
Regards,

Ryan Svihla