Questions[opscenter](server)

I'm trying to configure a new OpsCenter 5.2.2 manually to a newly launched and running Cassandra Cluster 2.0.17, so I add a cluster conf file, start the OpsCenter, which then creates the CF OpsCenter, all fine. When I start the datastax agent on the first node I get this:

2015-10-29 17:25:11+0100 [] WARN: Unable to find a matching cluster for node with IP d1r1n1; the message was [u'5.2.2', u'/2122343799/conf']. This usually indicates that an OpsCenter agent is still running on an old node that was decommissioned or is part of a cluster that OpsCenter is no longer monitoring.

Seems the agent is trying to push data to OpsCenter which then in turn doesn't recognize a cluster holding this node. But why what maybe I be missing?

Just defined my cluster in /etc/opscenter/cluster/cluster.conf:

[jmx]
port = 8081

[kerberos_client_principals]

[kerberos]

[agents]

[kerberos_hostnames]

[kerberos_services]

[cassandra]
api_port = 9161
seed_hosts = d1r1n1,d1r1n2,d1r1n3,d1r1n4
conf_location = /etc/cassandra/blob.conf/cassandra.yaml
log_location = /var/log/cassandra/blob-system.log

[storage_cassandra]
api_port = 9161

I am working with a OpsCenter 5.1.1 installation, while trying to add an existing DSE 4.6.5 cluster containing 5 nodes via the API. The options passed set the storage_cassandra variables for storing data on a separate cluster.

Intermittently this will fail and return a Time out with the following in the logs:

2015-06-04 21:00:10+0000 [dse_test]  INFO: Enterprise functionality: False
2015-06-04 21:00:10+0000 [dse_test]  INFO: OpsCenter shutting down.
2015-06-04 21:00:10+0000 [dse_test]  INFO: Stopping repair service
2015-06-04 21:00:10+0000 []  INFO: Unhandled error in Deferred:
2015-06-04 21:00:10+0000 [] Unhandled Error
        Traceback (most recent call last):
          File "/opt/iot-packages/datastax_opscenter/5.1.1/opscenter-5.1.1/lib/py-redhat/2.6/shared/amd64/twisted/internet/defer.py", line 361, in callback
            self._startRunCallbacks(result)
          File "/opt/iot-packages/datastax_opscenter/5.1.1/opscenter-5.1.1/lib/py-redhat/2.6/shared/amd64/twisted/internet/defer.py", line 455, in _startRunCallbacks
            self._runCallbacks()
          File "/opt/iot-packages/datastax_opscenter/5.1.1/opscenter-5.1.1/lib/py-redhat/2.6/shared/amd64/twisted/internet/defer.py", line 542, in _runCallbacks
            current.result = callback(current.result, *args, **kw)
          File "/opt/iot-packages/datastax_opscenter/5.1.1/opscenter-5.1.1/lib/py-redhat/2.6/shared/amd64/twisted/internet/defer.py", line 1076, in gotResult
            _inlineCallbacks(r, g, deferred)
        --- <exception caught here> ---
          File "/opt/iot-packages/datastax_opscenter/5.1.1/opscenter-5.1.1/lib/py-redhat/2.6/shared/amd64/twisted/internet/defer.py", line 1020, in _inlineCallbacks
            result = g.send(result)
          File "build/lib/python2.6/site-packages/opscenterd/ClusterServices.py", line 475, in waitForStartup

        exceptions.Exception: Storing data in a separate cluster is only supported when managing DSE clusters.

However, trying again using the same commands will succeed on the next attempt with the following difference in the opscenter log:

Enterprise functionality: True

What determines the enterprise functionality being set and how can I make sure it is consistent?

I enabled authentication on my opscenter node as per this . I've a python script that periodically invokes opscenter actions through the Opscenter REST APIs. From the REST API documentation, it looked like all I had to do was invoke these methods with basic HTTP auth (see this). But these calls always failed with a "user must be logged in" error.

After poking around the javascript that runs when I use the opscenter's web frontend, I figured that I must actually invoke the login method to create a session and use that session to invoke other methods, such as:

session = requests.Session()
login_body = '{"username": "%s", "password": "%s"}' % (opsc_uname, opsc_pwd)
login_resp = session.post("http://{url}/login".format(url=opsc_url), data=login_body).json()
clusterconf = session.get("http://{url}/cluster-configs".format(url=opsc_url)).json()

Is the api documentation (that claims to use basic http auth) wrong? Or am I doing something incorrectly? The opscenter version I'm using is 5.1.1

I recently installed Datastax community edition for windows. As per the installation manual, after successful installation, the Ops Center is supposed to open and show the status of the Test Cluster.

Looks like there was an issue, the Test Cluster did not come up by default. When I tried to create the test cluster there was a failure. Below is the error message in the opscenterd log.

INFO: Testing SSH connectivity to blrkec75614l
2014-09-24 20:14:16+0530 [] ERROR: Problem while calling ProvisionClusterController (NameError): global name 'get_output' is not defined
  File "C:\Program Files\DataStax Community\opscenter\lib\py-win32\2.7\twisted\internet\defer.py", line 1020, in _inlineCallbacks
    result = g.send(result)

  File "build/lib/python2.7/site-packages/opscenterd/SecureShell.py", line 206, in get_remote_ssh_key_bulk_by_type

Let me know what is the issue with this.

I guess the question is: why isn't this working? I'm a bit stuck because there isn't much in the way of documentation on the agent itself, and the exception (seemingly from Clojure) isn't particularly helpful.

• 3-node cluster running DSE 4.0.2 (on SLES 11 SP3, Oracle JRE 1.7.0_45)
• OpsCenter 4.1.2 on Ubuntu 14.04 LTS
• OpsCenter is able to connect to the cluster without problems, but obviously complaining that the agents on the three nodes haven't connected; being SLES the "Fix" link in the OpsCenter dashboard doesn't work (because SLES doesn't use apt or yum)
• Cassandra configuration in /etc/cassandra/ (which, based on strace, datastax-agent is finding, though it looks like it uses JMX after this, rather than reading cassandra.yaml)

Followed the manual agent setup instructions in the DataStax OpsCenter 4.1 documentation (basically just creating address.yaml), and started the datastax-agent on all three nodes. All three nodes get the same exception shortly after starting:

 INFO [StompConnection receiver] 2014-05-26 16:06:17,735 Starting up agent collection.
 INFO [StompConnection receiver] 2014-05-26 16:06:17,736 New JMX connection (127.0.0.1:7199)
ERROR [StompConnection receiver] 2014-05-26 16:06:17,749 failed calling listener
java.lang.IllegalArgumentException: No matching field found: getParentFile for class clojure.lang.Keyword
        at clojure.lang.Reflector.getInstanceField(Reflector.java:271)
        at clojure.lang.Reflector.invokeNoArgInstanceMember(Reflector.java:300)
        at opsagent.util.cassandra_util$find_base_dse_dir.invoke(cassandra_util.clj:50)
        at opsagent.util.cassandra_util$get_base_dse_dir.invoke(cassandra_util.clj:73)
        at opsagent.util.cassandra_util$tar_conf_location.invoke(cassandra_util.clj:89)
        at opsagent.util.cassandra_util$cassandra_conf_location.invoke(cassandra_util.clj:103)
        at opsagent.util.cassandra_util$get_cassandra_conf.invoke(cassandra_util.clj:123)
        at opsagent.opsagent$create_thrift_conf_vars.invoke(opsagent.clj:52)
        at opsagent.opsagent$post_interface_startup.doInvoke(opsagent.clj:95)
        at clojure.lang.RestFn.invoke(RestFn.java:421)
        at opsagent.conf$handle_new_conf.invoke(conf.clj:174)
        at opsagent.messaging$message_callback$fn__5242.invoke(messaging.clj:31)
        at opsagent.messaging.proxy$java.lang.Object$StompConnection$Listener$7f16bc72.onMessage(Unknown Source)
        at org.jgroups.client.StompConnection.notifyListeners(StompConnection.java:311)
        at org.jgroups.client.StompConnection.run(StompConnection.java:261)
        at java.lang.Thread.run(Unknown Source)

I get a similar (but more detailed) exception logged if I try to manually configure the node through OpsCenter (using the Configure action when viewing the node overview dialog):

 INFO [qtp1593743543-20] 2014-05-26 16:08:54,436 New JMX connection (127.0.0.1:7199)
ERROR [qtp1593743543-20] 2014-05-26 16:08:54,453 Unhandled route Exception: java.lang.IllegalArgumentException: No matching field found: getParentFile for class clojure.lang.Keyword
                       Reflector.java:271 clojure.lang.Reflector.getInstanceField
                       Reflector.java:300 clojure.lang.Reflector.invokeNoArgInstanceMember
                    cassandra_util.clj:50 opsagent.util.cassandra-util/find-base-dse-dir
                    cassandra_util.clj:73 opsagent.util.cassandra-util/get-base-dse-dir
                    cassandra_util.clj:89 opsagent.util.cassandra-util/tar-conf-location
                   cassandra_util.clj:103 opsagent.util.cassandra-util/cassandra-conf-location
                   cassandra_util.clj:123 opsagent.util.cassandra-util/get-cassandra-conf
                           routes.clj:130 opsagent.http.routes/fn
                              core.clj:94 compojure.core/make-route[fn]
                              core.clj:40 compojure.core/if-route[fn]
                              core.clj:25 compojure.core/if-method[fn]
                             core.clj:107 compojure.core/routing[fn]
                            core.clj:2443 clojure.core/some
                             core.clj:107 compojure.core/routing
                          RestFn.java:139 clojure.lang.RestFn.applyTo
                             core.clj:619 clojure.core/apply
                             core.clj:112 compojure.core/routes[fn]
                             Var.java:415 clojure.lang.Var.invoke
                        middleware.clj:76 opsagent.http.middleware/wrap-application-error[fn]
                        middleware.clj:58 opsagent.http.middleware/wrap-content-type[fn]
                        middleware.clj:95 opsagent.http.middleware/wrap-content-error[fn]
                        middleware.clj:14 opsagent.http.middleware/wrap-request-logging[fn]
                    keyword_params.clj:32 ring.middleware.keyword-params/wrap-keyword-params[fn]
                            params.clj:58 ring.middleware.params/wrap-params[fn]
                             jetty.clj:18 ring.adapter.jetty/proxy-handler[fn]
                         (Unknown Source) ring.adapter.jetty.proxy$org.eclipse.jetty.server.handler.AbstractHandler$0.handle
                  HandlerWrapper.java:111 org.eclipse.jetty.server.handler.HandlerWrapper.handle
                          Server.java:349 org.eclipse.jetty.server.Server.handle
          AbstractHttpConnection.java:452 org.eclipse.jetty.server.AbstractHttpConnection.handleRequest
          AbstractHttpConnection.java:894 org.eclipse.jetty.server.AbstractHttpConnection.content
          AbstractHttpConnection.java:948 org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content
                      HttpParser.java:857 org.eclipse.jetty.http.HttpParser.parseNext
                      HttpParser.java:235 org.eclipse.jetty.http.HttpParser.parseAvailable
              AsyncHttpConnection.java:76 org.eclipse.jetty.server.AsyncHttpConnection.handle
           SelectChannelEndPoint.java:609 org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle
            SelectChannelEndPoint.java:45 org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run
                QueuedThreadPool.java:599 org.eclipse.jetty.util.thread.QueuedThreadPool.runJob
                QueuedThreadPool.java:534 org.eclipse.jetty.util.thread.QueuedThreadPool$3.run
                         (Unknown Source) java.lang.Thread.run