Description of problem: JON Apache monitoring does not correctly detect virtual hosts when they are listening on more than one port. To resolve this issue I've found on Apache's website, http://httpd.apache.org/docs/2.2/vhosts/examples.html, if you are using the same IP with different ports, you will need a separate Virtual Host block for each port. i.e. Server configuration Listen 80 Listen 8080 NameVirtualHost 172.20.30.40:80 NameVirtualHost 172.20.30.40:8080 <VirtualHost 172.20.30.40:80> ServerName www.example.com DocumentRoot /www/domain-80 </VirtualHost> <VirtualHost 172.20.30.40:8080> ServerName www.example.com DocumentRoot /www/domain-8080 </VirtualHost> <VirtualHost 172.20.30.40:80> ServerName www.example.org DocumentRoot /www/otherdomain-80 </VirtualHost> <VirtualHost 172.20.30.40:8080> ServerName www.example.org DocumentRoot /www/otherdomain-8080 </VirtualHost> The customer believes this is an issue with JON's parsing of configuration files as Apache's VirtualHost directive is correct per Apache's documentation at http://httpd.apache.org/docs/2.2/mod/core.html#virtualhost, which indicates that more than one address and port number to be specified in a single VirtualHost directive.
From http://httpd.apache.org/docs/2.2/mod/core.html#virtualhost: <VirtualHost> Directive Description: Contains directives that apply only to a specific hostname or IP address Syntax: <VirtualHost addr[:port] [addr[:port]] ...> ... </VirtualHost> Note that the syntax clearly indicates that more than one address and port can be specified per virtual host. For example, the configuration below is completely valid in Apache and should be processed correctly within JON: Listen 80 Listen 8080 NameVirtualHost 172.20.30.40:80 NameVirtualHost 172.20.30.40:8080 <VirtualHost 172.20.30.40:80 172.20.30.40:8080> ServerName www.example.com DocumentRoot /www/domain </VirtualHost>
Lukas, is this addressed by the apache changes going into 2.4?
Triaged as urgent for investigation only, initially, since the release is so close. If changes are necessary, lets discuss before making them
This should be handled by the plugin that is going to be included with JON 2.4.
*** Bug 613072 has been marked as a duplicate of this bug. ***
If there is a test version that you would like us to run on our system to see if it resolves the issue, please let me know.
Pushing this to ON-QA since it should be fixed in 2.4
QA Verified, vhosts on multiple ports are now showing up
Mass-closure of verified bugs against JON.