Check-out our new look and give us some feedback!

Cassandra Failed to connect Error: [SOLVED]

Reading Time: < 1 minute
Pre-Flight Check
  • These instructions are intended specifically for solving the error: Failed to connect to ‘127.0.0.1:7199’: Connection refused.
  • I’ll be working from both Liquid Web Core Managed CentOS 6 and CentOS 7 servers, and I’ll be logged in as root.

Error While Using Cassandra’s ‘nodetool’

This error may occur when using the ‘nodetool’ command, such as in the following example:

nodetool status

For both CentOS 6 and CentOS 7 search the following configuration file:

vim /etc/cassandra/default.conf/cassandra-env.sh

For a refresher on editing files with vim see: New User Tutorial: Overview of the Vim Text Editor

Search for:

JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=

Which for my search resulted in:

# add this if you're having trouble connecting:
# JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=<public name>"

Uncomment the second line, and add the hostname of your server or the IP address which you’re connecting to/from. In this case, replacing <public name> with 127.0.0.1 resolved the issue, because we are connecting to/from that IP address.

Then exit and save the file with the command:
wq

Then, restart Cassandra:

systemctl restart cassandra

About the Author: J. Mays

Latest Articles

How to Edit Your DNS Hosts File

Read Article

How to Edit Your DNS Hosts File

Read Article

Microsoft Exchange Server Security Update

Read Article

How to Monitor Your Server in WHM

Read Article

How to Monitor Your Server in WHM

Read Article