There are several ways to install the DataStax agent from OpsCenter. Based on your IP address 127.0.1.1, you should use the Linux version for Debian. I know that he says "optional", but I could never work without the ssh private key. In this case, you must install the OpenSSH server using the following command
xyz@ubuntu $ sudo apt-get install openssh-server
Then follow these instructions to configure the SSH key, which you will then use to provide your credentials in the "fix agent" dialog box. The Datastax username / password for the DSE side is datastax / datastax unless you change it. This is what you need to enter for the username / password, and then also copy / paste the new SSH key into the private key field. The ssh key is in
/etc/ssh/ssh_host_rsa_key.pub
Once all the credentials are combined together, run the Installation Agents tool. If it is still not complete, you should check the datastax-agent folder in which you installed DSE and check if the jar file exists for the agent. It should be something like
datastax-agent-5.2.4-standalone.jar
You should also see the folder structure for the Agent, all directories bin, conf ... etc should be there. If everything is in place and your cassandra.yaml file is correct, you should be able to run the agent.
You can also do this manually by moving the correct directories and jar files into place, and then restarting the agent (s).
EDIT:
Looking at your last agent.log file, I would say this. A broken pipe error in Java refers to a connection that no longer works or is no longer available. Where he is absent from agent.log, he tries to contact opscenter. One of your connections is not configured or incorrectly configured. You also have another log for cassandra, which is usually located in / var / log / cassandra depending on how you installed cassandra. Comb it and make sure there are no errors during startup, warnings are good, but errors usually indicate a problem.
From now on, you have the following log files. Please note that the location of the files may differ from yours, depending on how you installed everything.
/var/log/cassandra /var/log/datastax-agent /var/log/OpsCenter
and you have the following commands to help you figure out what actually works and which port is connected. See below what these commands tell you.
xyz@ubuntu $ sudo netstat -p | grep 127.0.1.1
You should see at least the following ports bound to your 127.0.1.1 addr: 9042, 8888, 61620 and several others.
Also see the output of these two commands. If you don’t get anything, try running them as sudo. The output will depend on how you launched the banks.
xyz@ubuntu $ ps -ef | grep datastax-agent xyz@ubuntu $ ps -ef | grep cassandra
You should see all the downloaded jar files, as well as the environment variables that were set when you started cassandra and / or datastax-agent.
You can edit your post and explain how you started cassandra. those. as a service or from the command line?
In addition, from OpsCenter you can see test_cluster at 127.0.1.1:8888. If your request to fix agents simply leaves these dialog boxes, until you are on the main screen where the data center is located. Even if it does not connect to the agent, opscenter should still show an instance of cassandra. Do you see your test_cluster?
Finally, what do you get when you type this
xyz@ubuntu $ nodetool status
EDIT 2:
Based on your last edit, it seems like everything except the agent is up and running. So says nodetool, which is good. Also, since you see Keyspaces in OpsCenter, you are definitely connected to an executable instance of cassandra.
Thus, looking further, your datastax agent is still not connecting. Looking at your address.yaml file, I see a couple of possible problems. This is a simple standalone cassandra cluster with a single IP address of 127.0.1.1. Thus, the address 127.0.1.1 will be used in all configurations where the IP address or host is involved. I would make the following changes to the address.yaml file.
stomp_interface: 127.0.1.1 cassandra-conf: /home/kaushaya/Dropbox/Work/ITNow/olderVersions/cassandra2.11/apache-cassandra-2.1.12/conf/cassandra.yaml stomp_port: 61620
Leave the JMX parts as they are not needed and will be sent using opscenterd after connecting. Agent_rpc_interface is also not required in this installation.
There is also a cassandra-env.sh script, which is located in the cassandra / conf directory. this script is executed when cassandra starts. find the next line at the bottom of the script and uncomment it and add your host IP address 127.0.1.1 instead of <public name>
# jmx: metrics and administration interface
Finally, there is the cassandra utility registered HERE. You can pass several cli parameters to the cassandra shell during initialization. This specific below is useful when you want to start / restart the cassandra cluster after changing the IP or hostname. After you make these changes, you need to restart cassandra. In fact, you shoudl are restarting everything in that order. Cassandra, datastax-agent and then opscenter.
xyz@ubuntu $ bin/cassandra -Dcassandra.load_ring_state=false
After you make the changes and try to start the agent and it still does not work, you will need additional debugging information. Netstat returned false due to the fact that we connected to the grep utility. try the following as the ports are probably associated with your hostname as you are using 127.0.1.1. Run it for the following ports: 9042 ,: 7199, and: 61620. You are looking for your hostname associated with all these ports while cassandra is running.
xyz@ubuntu $ sudo netstat -p | grep :9042
Please also edit your question and add versions of OpsCenter and Datastax-Agent. It is important.