Opscenter Config

(8 posts) (2 voices)

• Started 3 months ago by naseerm
• Latest reply from nickmbailey
• This topic is not resolved

Tags:

No tags yet.

1. 

   naseerm
   Member

   Where can I get a complete listing of the properties for the opscenterd and opscenter agent. It seems there are some well known defaults, but nothing really in the documentation that i have been able to find here. Could someone please provide a pointer?

   My issues are centered around trying to get the opscenter agent to connect to the server and this far i have not had much success.

   I read "opscenter is listening in the localhost(127.0.0.1) IP with port 61620 - how to modify this?" and found that there is a property for opscenterd.conf in the agent stanza "incoming_interface". i added this and it still does not do what i expect. I am currently using the community edition so i am not sure if that is the cause. We are trying to evaluate Cassandra through a labweek project and it would be nice to showcase the Opscenter.

   Inputs/Suggestions welcomed

   Posted 3 months ago #
2. 

   nickmbailey
   Administrator

   Naseerm,

   Currently the most complete listing of the opscenter configuration options is the conf file itself and the configuration options described here: http://www.datastax.com/docs/opscenter/configure_opscenter

   Generally you should not need to change any options besides these. Can you give more info on the exact error you are seeing when the agent fails to connect to OpsCenter? By default OpsCenter listens on port 61620 on all interfaces on the OpsCenter machine. Since it listens on all interfaces you should not need to change the 'incoming_interface' option. If you can provide more info on the errors you are seeing it would help us debug what the issue is here.

   Posted 3 months ago #
3. 

   naseerm
   Member

   There are four nodes in our cassandra cluster and here is the status of the services

   [root@lfs01 logs]# service cassandra status
   cassandra (pid 9911) is running...
   [root@lfs01x logs]# service opscenterd status
   opscenterd (pid 16290) is running...
   [root@lfs01x logs]# service opscenter-agent status
   opscenter-agent (pid 17089) is running...

   I have not modified any of the defaults, so 61620 has not been changed

   Here is what i see in the opscenterd logs

   2012-02-15 18:44:20+0000 [] DEBUG: Average opscenterd CPU usage: 0.60%, memory usage: 27 MB
   2012-02-15 18:44:21+0000 [] DEBUG: Collecting topology info for node 10.X.X.219
   2012-02-15 18:44:21+0000 [] ERROR: Error collecting datacenter: No agents available to query.
   2012-02-15 18:44:21+0000 [] DEBUG: Collecting topology info for node 10.X.X.222
   2012-02-15 18:44:21+0000 [] ERROR: Error collecting datacenter: No agents available to query.
   2012-02-15 18:44:21+0000 [] DEBUG: Collecting topology info for node 10.X.X.221
   2012-02-15 18:44:21+0000 [] ERROR: Error collecting datacenter: No agents available to query.
   2012-02-15 18:44:21+0000 [] DEBUG: Collecting topology info for node 10.X.X.220
   2012-02-15 18:44:21+0000 [] ERROR: Error collecting datacenter: No agents available to query.
   2012-02-15 18:44:21+0000 [] DEBUG: Getting nodelist over thrift

   and here is what i see in the agent logs

   INFO [StompConnection receiver] 2012-02-15 04:49:47,069 Jetty server started
   ERROR [pool-4-thread-3] 2012-02-15 04:49:47,532 Error getting devices and partitions
   java.lang.NullPointerException
   at java.util.regex.Matcher.getTextLength(Matcher.java:1140)
   at java.util.regex.Matcher.reset(Matcher.java:291)
   at java.util.regex.Matcher.<init>(Matcher.java:211)
   at java.util.regex.Pattern.matcher(Pattern.java:888)
   at clojure.core$re_matcher.invoke(core.clj:3760)
   at clojure.contrib.str_utils2$eval3698$fn__3699.invoke(str_utils2.clj:180)
   at clojure.lang.MultiFn.invoke(MultiFn.java:172)
   at opsagent.util$escape_device_name.invoke(util.clj:29)
   at opsagent.nodedetails$get_disk_info.invoke(nodedetails.clj:102)
   at opsagent.nodedetails$run_longtime_collection$fn__1180.invoke(nodedetails.clj:173)
   at opsagent.jmx$jmx_wrap.doInvoke(jmx.clj:93)
   at clojure.lang.RestFn.invoke(RestFn.java:410)
   at opsagent.nodedetails$run_longtime_collection.invoke(nodedetails.clj:165)
   at opsagent.nodedetails$start_pool$fn__1206$fn__1207.invoke(nodedetails.clj:214)
   at opsagent.util$error_wrap.doInvoke(util.clj:97)
   at clojure.lang.RestFn.invoke(RestFn.java:423)
   at opsagent.nodedetails$start_pool$fn__1206.invoke(nodedetails.clj:214)
   at clojure.lang.AFn.run(AFn.java:24)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
   INFO [pool-5-thread-2] 2012-02-15 04:49:52,004 New JMX connection (127.0.0.1:7199)

   - naseer

   Posted 3 months ago #
4. 

   nickmbailey
   Administrator

   Naseer,

   That error from the agent logs is related to the additional issue you posted about here: http://www.datastax.com/support-forums/topic/npe-error-getting-devices-and-partitions

   It should be unrelated to the problem causing communication issues between OpsCenter and the agents. Your sample from the OpsCenter log does indicate there is a problem with agent communication though. Can you give a larger sample of the logs from your agent? There will likely be errors when OpsCenter is starting up that indicate what the problem is. Even if there are not errors there may be an indication of what the problem is. Also can you verify if you are running the latest version of OpsCenter (1.4)?

   Posted 3 months ago #
5. 

   naseerm
   Member

   Here is what i did to fix the communication issue, hence the ask for properties.

   [root@lfs03x-dxc1 conf]# cat address.yaml
   #
   use_ssl: 0
   stomp_interface: "10.X.3.219"

   local_interface: "10.X.3.221"

   what mattered was the stomp_interface and local_interface. After adding this and restarting the agent, it worked like a charm. I am still seeing "Error getting devices and partitions" errors and i will look @ the other thread

   thanks for looking into it

   - Naseer

   Posted 3 months ago #
6. 

   nickmbailey
   Administrator

   Naseer,

   Glad you got it working. Those conf settings are automatically created when you setup the agent by runing 'bin/setup' in the agent install directory. (Assuming you are installing the agent manually.)

   http://www.datastax.com/docs/opscenter/install_agents#manually-installing-agents-in-tar-installations

   Editing them manually is also fine, however using the setup script should prevent you from needing to perform that step. Hope that helps.

   Nick

   Posted 3 months ago #
7. 

   naseerm
   Member

   FYI - actually i used the RPM - not the tar ball

   Posted 3 months ago #
8. 

   nickmbailey
   Administrator

   You mean you installed the agents manually but used the agent rpm rather than the agent tarball? In that case the options passed to the 'bin/install_agent.sh' script control those settings in the conf file, similar to the 'bin/setup' script.

   Posted 3 months ago #

RSS feed for this topic

Reply

You must log in to post.