3 Replies Latest reply on Aug 19, 2011 12:19 PM by gointomexico

    agent fails to start

    gointomexico

      and continues to restart throwing the error below. I was running rhq 3 fine, and I couldnt see my apache instances. I dont need to see them, im mostly monitoring jboss instances with this agent. Can someone tell me how to remove this error and get the agent to start? I already tried removing the module from the module directory, but the agent just downloads it back from the server.

       

      RHQ 4.0.1 [ecd91b2] (Fri May 20 16:41:18 UTC 2011)

      Failed to start the agent

      org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10947, type=Apache HTTP Server, key=/etc/httpd||/etc/httpd/conf/httpd2.conf, name=/etc/httpd/conf/httpd2.conf, parent=server1, version=2.2.3].

              at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1589)

              at org.rhq.core.pc.inventory.InventoryManager.activateAndUpgradeResourceRecursively(InventoryManager.java:2745)

              at org.rhq.core.pc.inventory.InventoryManager.activateAndUpgradeResourceRecursively(InventoryManager.java:2747)

              at org.rhq.core.pc.inventory.InventoryManager.activateAndUpgradeResources(InventoryManager.java:2723)

              at org.rhq.core.pc.inventory.InventoryManager.initialize(InventoryManager.java:228)

              at org.rhq.core.pc.PluginContainer.startContainerService(PluginContainer.java:425)

              at org.rhq.core.pc.PluginContainer.initialize(PluginContainer.java:279)

              at org.rhq.enterprise.agent.AgentMain.startPluginContainer(AgentMain.java:1867)

              at org.rhq.enterprise.agent.AgentMain.start(AgentMain.java:648)

              at org.rhq.enterprise.agent.AgentMain.main(AgentMain.java:418)

      Caused by: org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Neither SNMP nor an URL for checking availability has been configured

              at org.rhq.plugins.apache.ApacheServerComponent.start(ApacheServerComponent.java:210)

              at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:525)

              at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

              at java.util.concurrent.FutureTask.run(FutureTask.java:138)

              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:619)

      Agent will be restarted soon to see if the failure condition cleared up

        • 1. Re: agent fails to start
          mazz

          I would try to start the agent with its data purged - let the agent start up with no inventory and force it to sync inventory down from the server. That might help:

           

          rhq-agent.sh --purgedata

           

          It seems odd that this happened though. Did you recently upgrade the agent or the apache plugin? I'm at a loss for how this happened. But see if starting with --purgedata helps clear up the error.

          • 2. Re: agent fails to start
            gointomexico

            Thanks for your reply. I tried that, and I still go the same error.

             

            $ ./rhq-agent.sh --purgedata

            RHQ 4.0.1 [ecd91b2] (Fri May 20 16:41:18 UTC 2011)

            Failed to start the agent

            org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10947, type=Apache HTTP Server,...

            • 3. Re: agent fails to start
              gointomexico

              I fixed the issue myself. I went to the server and un-invintoried the http resources. I dont care much about monitoring them so I just removed them. After I did that the agents started up fine.

               

              I was running rhq3 andupgraded to 4. rhq3 didnt seem to care that it could not monitor the http services, but rhq4 agents would not start up if it couldnt connect. I think this should be some sort of bug, yea?