Re: RE: Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Subroto Barua
check firewall rules to/from .152 to seed nodes (telnet  <port#>


On Tuesday, July 4, 2017, 6:38:16 AM PDT, Jonathan Baynes 
<jonathan.bay...@tradeweb.com> wrote:

#yiv3228115995 #yiv3228115995 -- _filtered #yiv3228115995 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv3228115995 
{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv3228115995 
#yiv3228115995 p.yiv3228115995MsoNormal, #yiv3228115995 
li.yiv3228115995MsoNormal, #yiv3228115995 div.yiv3228115995MsoNormal 
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv3228115995 a:link, 
#yiv3228115995 span.yiv3228115995MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv3228115995 a:visited, #yiv3228115995 
span.yiv3228115995MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv3228115995 
span.yiv3228115995EmailStyle17 {color:windowtext;}#yiv3228115995 
span.yiv3228115995EmailStyle18 {color:#1F497D;}#yiv3228115995 
.yiv3228115995MsoChpDefault {font-size:10.0pt;} _filtered #yiv3228115995 
{margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv3228115995 
div.yiv3228115995WordSection1 {}#yiv3228115995 
Hi Bhargav
 
  
 
  
 
I had this recently when making changes to a cluster, and It was down to the 
Listen_address & broadcast_address. Check your cassandra.yaml and make sure 
that your listen_address/broadcast_address and "seeds" values match. Make sure 
the Data folder is empty as well.
 
  
 
I would go through your yaml, be diligent its there that is the problem.
 
  
 
Thanks
 
J
 
  
 
  
 
From: Mokkapati, Bhargav (Nokia - IN/Chennai) 
[mailto:bhargav.mokkap...@nokia.com]
Sent: 04 July 2017 14:00
To: user@cassandra.apache.org
Subject: Cassandra issue “Unable to gossip with any seeds”
 
  
 
Hi Team,
 
  
 
I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”
 
  
 

 
  
 
I am using Apache Cassandra 3.0.6 version.
 
  
 
I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155
 
  
 
Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155
 
  
 
All the nodes have same Cassandra.yaml configuration file
 
  
 
I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.
 
  
 

 
  
 
  
 
Also node2 is pinging from seed nodes and vice versa.
 
  
 

 
  
 
  
 
Please let me know if any of you have faced the same issue and found the 
solution.
 
  
 
Thank you very much
 
  
 
Regards,
 
Bhargav
 
  
 
  
 
  
 
  
 
  
 
  
 


This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy it. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly 
forbidden. Tradeweb reserves the right to monitor all e-mail communications 
through its networks. If you do not wish to receive marketing emails about our 
products / services, please let us know by contacting us, either by email at 
contac...@tradeweb.com or by writing to us at the registered office of Tradeweb 
in the UK, which is: Tradeweb Europe Limited (company number 3912826), 1 Fore 
Street Avenue London EC2Y 9DT. To see our privacy policy, visit our website @ 
www.tradeweb.com.

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

RE: Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Jonathan Baynes
Hi Bhargav


I had this recently when making changes to a cluster, and It was down to the 
Listen_address & broadcast_address. Check your cassandra.yaml and make sure 
that your listen_address/broadcast_address and "seeds" values match. Make sure 
the Data folder is empty as well.

I would go through your yaml, be diligent its there that is the problem.

Thanks
J


From: Mokkapati, Bhargav (Nokia - IN/Chennai) 
[mailto:bhargav.mokkap...@nokia.com]
Sent: 04 July 2017 14:00
To: user@cassandra.apache.org
Subject: Cassandra issue “Unable to gossip with any seeds”

Hi Team,

I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”

[cid:image001.jpg@01D2F4D3.1E74E5E0]

I am using Apache Cassandra 3.0.6 version.

I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155

Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155

All the nodes have same Cassandra.yaml configuration file

I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.

[cid:image002.png@01D2F4D3.1E74E5E0]


Also node2 is pinging from seed nodes and vice versa.

[cid:image003.png@01D2F4D3.1E74E5E0]


Please let me know if any of you have faced the same issue and found the 
solution.

Thank you very much

Regards,
Bhargav









This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy it. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly 
forbidden. Tradeweb reserves the right to monitor all e-mail communications 
through its networks. If you do not wish to receive marketing emails about our 
products / services, please let us know by contacting us, either by email at 
contac...@tradeweb.com or by writing to us at the registered office of Tradeweb 
in the UK, which is: Tradeweb Europe Limited (company number 3912826), 1 Fore 
Street Avenue London EC2Y 9DT. To see our privacy policy, visit our website @ 
www.tradeweb.com.


Cassandra issue “Unable to gossip with any seeds”

2017-07-04 Thread Mokkapati, Bhargav (Nokia - IN/Chennai)
Hi Team,

I am getting the below issue when I started a node. “Unable to gossip with any 
seeds”

[cid:image003.jpg@01D2F4F3.8B790480]

I am using Apache Cassandra 3.0.6 version.

I have 5 nodes in the cluster,10.50.20.151 , 10.50.20.152 , 10.50.20.153 , 
10.50.20.154 , 10.50.20.155

Seed nodes -  10.50.20.153 , 10.50.20.154 , 10.50.20.155

All the nodes have same Cassandra.yaml configuration file

I am getting this issue only in node2 (10.50.20.152). It didn’t even joined the 
cluster.

[cid:image004.png@01D2F4F1.9773CC90]


Also node2 is pinging from seed nodes and vice versa.

[cid:image005.png@01D2F4F2.4B7CAA90]


Please let me know if any of you have faced the same issue and found the 
solution.

Thank you very much

Regards,
Bhargav