httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Pielmeier." <ste...@symlinux.com>
Subject [users@httpd] warning: NameVirtualHost has no VirtualHosts
Date Mon, 09 Sep 2013 09:22:07 GMT
Hi,

I am courious if there are others who have the same observation in my case.

I used the Apache documentation to use name based virtual hosts.

My site-enabled file looks now like this:
--
NameVirtualHost *:80
<VirtualHost *:80>
        ServerName wiki.mydomain.com
        ServerAdmin webmaster@mydomain.com
        DocumentRoot /var/lib/wiki/
        <Directory /var/lib/wiki/>
                Options +FollowSymLinks
                AllowOverride All
                order allow,deny
                allow from all
        </Directory>
</VirtualHost>

<VirtualHost *:80>
        ServerName www.mydomain.com
        ServerAlias *.mydomain.com
        ServerAdmin webmaster@localhost

        DocumentRoot /var/www
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        </Directory>
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
        </Directory>

        ErrorLog /var/log/apache2/error.log

        LogLevel warn

        CustomLog /var/log/apache2/access.log combined
</VirtualHost>
--

I want to achieve that wiki.mydomain.com loads the wiki directly, thus the
1st virtual host.
All other *.mydomain.com hosts shall be handled by the 2nd virtual host.

Actually, it works (on the surface?), but I get this warning when I
restart acpache2:

--
# service apache2 restart
 * Restarting web server apache2
[Mon Sep 09 11:05:03 2013] [warn] NameVirtualHost *:80 has no VirtualHosts
 ... waiting [Mon Sep 09 11:05:04 2013] [warn] NameVirtualHost *:80 has no
VirtualHosts
   ...done.
--

What does the warning really mean?
I have specified Virtual Hosts with pattern *:80, they are apparently
working, but why the warning then?

How could I change my configuration to make the warning disappear?

Ah, the same happens if I try to do that on SSL port 443 site definition
file.

PS: I tried to find the answer through searching the net, but apparenetly,
I was not good enough at it.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message