JON is unable to manage or monitor Apache HTTP Server due to invalid connection properties

Solution Verified - Updated -

Issue

  • When I try to change the Inventory -> Connection properties for Apache HTTP server to point to the correct configuration directory I get the error message:
    The agent reported the following error on its last attempt (1/1/10, 4:08:57 AM, EDT) to connect to this resource:
    Failed to start component for resource Resource[id=10851, type=Apache HTTP Server, key=/etc/httpd, name=my-ews-host.net Apache 2.2.14 (/etc/httpd/), parent=my-ews-host.net, version=2.2.14].
    For more details, see the stack trace.
    
    Please make sure that the managed resource is running and that its connection properties are set correctly.
    
    org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10851, type=Apache HTTP Server, key=/etc/httpd, name=my-ews-host.net Apache 2.2.14 (/etc/httpd/), parent=my-ews-host.net, version=2.2.14].
         at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1280)
         at org.rhq.core.pc.inventory.InventoryManager.refreshResourceComponentState(InventoryManager.java:2256)
         at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2057)
         at org.rhq.core.pc.inventory.InventoryManager.processSyncInfo(InventoryManager.java:2063)
         at org.rhq.core.pc.inventory.InventoryManager.synchInventory(InventoryManager.java:807)
         at org.rhq.core.pc.inventory.InventoryManager.handleReport(InventoryManager.java:787)
         at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:119)
         at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:55)
         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
         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)
    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:153)
         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)
         ... 3 more
    
  • Newly inventoried Apache HTTP server shows a state of DOWN
  • Management of Apache HTTP server fails and the following log message appears in the JON Agent:
    INFO  [WorkerThread#0[127.0.0.1:60748]] (rhq.core.pc.inventory.InventoryManager)- Unable to connect to managed resource of type [Apache HTTP Server] using the specified connection properties.
    org.rhq.core.pluginapi.inventory.InvalidPluginConfigurationException: Failed to start component for resource Resource[id=10494, type=Apache HTTP Server, key=/etc/httpd, name=localhost.localdomain Apache 2.2.14 (/etc/httpd/), parent=Agent1, version=2.2.14].
            at org.rhq.core.pc.inventory.InventoryManager.activateResource(InventoryManager.java:1280)
            at org.rhq.core.pc.inventory.InventoryManager.updatePluginConfiguration(InventoryManager.java:402)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at org.rhq.enterprise.communications.command.impl.remotepojo.server.RemotePojoInvocationCommandService.execute(RemotePojoInvocationCommandService.java:184)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93)
            at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27)
            at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)
            at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)
            at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)
            at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
            at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
            at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
            at $Proxy0.execute(Unknown Source)
            at org.rhq.enterprise.communications.command.server.CommandProcessor.handleIncomingInvocationRequest(CommandProcessor.java:290)
            at org.rhq.enterprise.communications.command.server.CommandProcessor.invoke(CommandProcessor.java:184)
            at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809)
            at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
            at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406)
            at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
    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:153)
            at sun.reflect.GeneratedMethodAccessor25.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)
    
  • Metrics are not being collected for Apache HTTP server and the following warning appears in the agent log:
    WARN  [ResourceContainer.invoker.daemon-15] (org.rhq.plugins.apache.ApacheServerComponent)- Failed to connect to SNMP agent at 127.0.0.1/1610/public
    . Make sure
    1) the managed Apache server has been instrumented with the JON SNMP module,
    2) the Apache server is running, and
    3) the SNMP agent host, port, and community are set correctly in this resource's connection properties.
    The agent will not be able to record metrics from apache httpd without SNMP
    
  • Agent debug log contains the following entry for the corresponding Apache instance:
    DEBUG [ResourceContainer.invoker.daemon-1] (rhq.plugins.www.snmp.SNMPSession_v2c)- Error while pinging SNMP 1 agent at 192.168.1.50/1610/public. SNMP GETNEXT request for iso(1) failed - org.rhq.plugins.www.snmp.SNMPException: Request for [iso] timed out.
    
  • We do not see any metrics reported for Apache server
  • Missing Apache metrics or measurements

Environment

  • JBoss Operations Network (JON) 2.3.1
  • JBoss Enterprise Web Server (EWS) 1.0.1
  • Apache HTTP Server provided by JBoss EWS
  • Apache HTTP Server provided by Red Hat Enteprirse Linux (RHEL) Red Hat Network (RHN) update channel

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.