Red Hat Bugzilla – Bug 656497
[apache] Unresolvable hostname in VirtualHost or ServerName directive fails vhost discovery
Last modified: 2011-05-23 21:13:07 EDT
+++ This bug was initially created as a clone of Bug #656491 +++ Description of problem: 2010-11-23 21:27:26,654 WARN [ResourceDiscoveryComponent.invoker.daemon-3] (rhq.plugins.apache.util.HttpdAddressUtility)- Failed to obtain virtual host address. java.net.UnknownHostException: v-hovnech at java.net.InetAddress.getAllByName0(InetAddress.java:1158) at java.net.InetAddress.getAllByName(InetAddress.java:1084) at java.net.InetAddress.getAllByName(InetAddress.java:1020) at java.net.InetAddress.getByName(InetAddress.java:970) at org.rhq.plugins.apache.util.HttpdAddressUtility.updateWithServerName(HttpdAddressUtility.java:369) at org.rhq.plugins.apache.util.HttpdAddressUtility.getVirtualHostSampleAddress(HttpdAddressUtility.java:275) at org.rhq.plugins.apache.ApacheVirtualHostServiceDiscoveryComponent.discoverResources(ApacheVirtualHostServiceDiscoveryComponent.java:102) at sun.reflect.GeneratedMethodAccessor263.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.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:279) 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) 2010-11-23 21:27:26,654 WARN [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Failure during discovery for [Apache Virtual Host] Resources - failed after 383 ms. java.lang.Exception: Discovery component invocation failed. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:283) 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) Caused by: java.lang.NullPointerException at org.rhq.plugins.apache.ApacheVirtualHostServiceDiscoveryComponent.discoverResources(ApacheVirtualHostServiceDiscoveryComponent.java:147) at sun.reflect.GeneratedMethodAccessor263.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.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:279) ... 5 more Version-Release number of selected component (if applicable): 3.0.0 How reproducible: always Steps to Reproduce: 1. have httpd.conf with ServerName with invalid hostname in the main server configuration, or a VirtualHost directive with invalid hostname specified as its address, or a ServerName directive with invalid hostname inside VirtualHost definition. 2. discover and inventory the server Actual results: the entries with invalid hostnames are not discovered Expected results: All the vhosts and the Main server and discovered Additional info:
commit 3e03058e6b276b66affd1529d684882db3cc3a13 Author: Lukas Krejci <lkrejci@redhat.com> Date: Fri Nov 26 14:48:32 2010 +0100 A cherry-pick and adaptation of the original fix ae99b5bc0bf42909308a9d1efc09cee77d06ffc1 in release-3.0.0 branch: a couple of robustness enhancements to the apache plugin: BZ 656449 - use the matching algorithm between SNMP values and augeas nodes also when matching the vhost node by resource key, because resource key in RHQ 3 is based on the SNMP value. BZ 652247 - Log the SNMP errors only on DEBUG level during discovery because SNMP isn't required for it to work. BZ 656476 - Do not fail the discovery if a non-existent directory is used in an Include directive BZ 652247, BZ 656491 - Do not choke on invalid/unresolvable hostnames in VirtualHost or ServerName directives
Verified on build#1086 (Version: 4.0.0-SNAPSHOT Build Number: 7b2d9f6) Configured httpd.conf with ServerName with invalid hostname in the main server configuration and aslo inside VirtualHost definition. All the vhosts and the Main server are discovered. Marking as verified.
Bookkeeping - closing bug - fixed in recent release.