Re: Conection refuse

Thanks Akhil, I will follow your steps. Thanks for the links. Best, Amirali On Tue, Aug 29, 2017 at 8:19 PM, Akhil Mehra wrote: > To install make sure: > > Your cluster name on each node are the same. > You configure your seed nodes. Make one node the seed node and added

Re: Conection refuse

To install make sure: Your cluster name on each node are the same. You configure your seed nodes. Make one node the seed node and added seed configuration to all your yaml files. Ensure that intra-node communication is on the same port. By default this is on port 7000 Do not startup all nodes

Re: Conection refuse

Thanks Akhil, I will do it. For setting up my second node, do you have any good source that I can follow to make sure I am doing everything correct? I have been googling around and quite frankly all the source that I found in the Google were kind of different from each other and I guess that is

Re: Conection refuse

If the data is not important then stop all nodes. On each node empty your commitlog, data, hints and saved_cache directories. Start one node. Wait for it to boot up successfully i.e. logs have no errors and you can connect to it using cqlsh. Start your second node and make sure it bootstraps

Re: Conection refuse

Akhil, Commit log directory from yaml file is: /var/lib/cassandra/commitlog So basically I removed it. Can I copy a new one from another node? or somehow generate one? Yes, the rm -rf was on the original and the only node. I stopped the C* and ran the rm -rf /var/lib/cassandra/*. At this point,

Re: Conection refuse

What directory was the data and commit logs stored on the original working node. You can look up your cassandra.yaml to figure this out. Its good to confirm. Was the rm -rf run on the original working node? Cheers, Akhil > On 30/08/2017, at 9:37 AM, Amir Shahinpour

Re: Conection refuse

Yes both of the nodes are down. On Aug 29, 2017 2:30 PM, "Akhil Mehra" wrote: > Cassandra is doing a health check when it is starting up and failing due > to being unable to ready files in the system key space. Here is the comment > in the segment of the code that threw

Re: Conection refuse

Cassandra is doing a health check when it is starting up and failing due to being unable to ready files in the system key space. Here is the comment in the segment of the code that threw the exception.

Re: Conection refuse

Hi Lucas, Thanks for your response. So I checked the system.log and I found the following error at the end which I think is causing the problem. Fatal exception during initialization org.apache.cassandra.exceptions.ConfigurationException: Found system keyspace files, but they couldn't be loaded!

Re: Conection refuse

Hello Amir, You should see the log. If it was installed by the apt-get tool, it should be in /var/log/cassandra/system.log. It can occur when the schema of the node you are trying to connect is out of date with the cluster. How many nodes are there in you cluster? What is the output of "nodetool

Re: Conection refuse

Is this a local install? If so you can set your rpc_address to 127.0.0.1. The rpc_address are the IP addresses that will be allowed to make connections to Cassandra. I suspect the problem is that you have set your RPC address to your IP address with is different from 127.0.0.1. cqlsh by

Conection refuse

Hi, I am getting an error connecting to cqlsh. I am getting the following error. Connection error: ('Unable to connect to any servers', {'127.0.0.1': error(111, "Tried connecting to [('127.0.0.1', 9042)]. Last error: Connection refused")}) I change the Cassandra.yaml file setting for