J. Greenlees wrote:
Running Apache 2.2.8 [ Mandriva 2008.1 default build with php5, mod_perl
and mod_python over base install ]
I set up 3 vhosts, using name based vhosts.
all 3 work but the 3rd one has a response time of over 5 minutes. This
is just loading a basic html page, so the php, perl and python support
shouldn't be an issue.
The other two vhosts load and display the correct page instantly.
I added them one at a time and tested, when the first one worked I
copied the container and edited it to meet the needs of the second,
tested then repeated for the third.
Does anyone have any idea what would cause the 3rd vhost to take so long
to respond?
here is the vhost conf currently in use:
<VirtualHost *:80>
ServerAdmin
DocumentRoot /home/jaqui/public_html
ServerName dev.runic-hosting.com
ErrorLog /var/log/httpd/dev.runic-hosting.com-error_log
CustomLog /var/log/httpd/dev.runic-hosting.com-access_log common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin
DocumentRoot /home/dawnfyre/public_html
ServerName dev.jaqui-greenlees.net
ErrorLog /var/log/httpd/dev.jaqui-greenlees.net-error_log
CustomLog /var/log/httpd/dev.jaqui-greenlees.net-access_log common
</VirtualHost>
<VirtualHost *:80>
ServerAdmin
DocumentRoot /home/shawan/public_html
ServerName dev.shawanspage.com
ErrorLog /var/log/httpd/dev.shawanspage.com-error_log
CustomLog /var/log/httpd/dev.shawanspage.com-access_log common
</VirtualHost>
This is a testing system, so it's not a critical issue as in harming
production system(s)
The email addresses removed to avoid spambots getting them.
The error logs only show:
Request exceeded the limit of 10 internal redirects due to probable
configuration error. Use 'LimitInternalRecursion' to increase the limit
if necessary. Use 'LogLevel debug' to get a backtrace.
for the default vhost, the other 2 vhosts have empty error logs.
Hi.If it wasn't for the error message in the log, I would tell you to first look at your DNS configuration, and check how that hostname "dev.shawanspage.com" is being resolved. If you have two DNS servers configured, and the first one for some reason is not answering, then your local resolver will first wait for an answer from the first one, time out, then try the second one. That could be your delay.
Second, remember that the first Vhost is the default Vhost. That means that when any request somehow arrives to your server, if the server cannot match the "Host:" header in the request, with one of your VHost "ServerName" lines, it will process the request using the first defined VHost, no matter what its own "ServerName" line says.
But then there is the error log.Because the message occurs in the log of the default VHost, it seems to indicate that the request did not match the ServerName of your third VHost, and was thus processed by the default host.
Which is strange on the face of it.But the error message also indicates some kind of loop. As if the request did arrive and was first processed by the 3rd VHost, which re-directed it to the same IP, but with a wrong "Host:" header, which caused the redirected request to be handled by the default VHost, which itself re-directed it and so on. Do you by any chance, in these VHosts, have .htaccess files in the DocumentRoot that would do some kind of re-direct ?
Or is there some part of the configuration that you are not showing us ? --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|