Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
# apache2ctl restart
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Jan 17 00:51:23 2007] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Wed Jan 17 00:51:23 2007] [warn] NameVirtualHost *:0 has no VirtualHosts
[Wed Jan 17 00:51:23 2007] [warn] NameVirtualHost *:80 has no VirtualHosts
I'm used to seeing the ServerName error, but what's wrong with my virtual host setup?
Thanks for the help--I'm googled-out!
Last edited by gregmcavoy; 01-18-2007 at 12:55 PM.
# Include the virtual host configurations:
Include /etc/apache2/sites-enabled/
But I haven't done anything with sites-enabled. I'm used to working with Apache 1.3, so if 2.2 requires me to do something there, I'll need pointers. From the Apache 2.2 documentation, it looks like it just gives me the option of creating a special conf file for each virtual host, which I don't think I need.
And actually, I'm getting this sometimes, too (when trying to use the virtual host code listed above):
Code:
# apache2ctl start
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Wed Jan 17 15:07:04 2007] [error] VirtualHost *:80 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Wed Jan 17 15:07:04 2007] [warn] NameVirtualHost *:0 has no VirtualHosts
[Wed Jan 17 15:07:04 2007] [warn] NameVirtualHost *:80 has no VirtualHosts
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
But rebooting clears the darned sock error.
Any other ideas on getting the virtual hosts to be recognized normally?
Last edited by gregmcavoy; 01-17-2007 at 05:17 PM.
I needed to not have the virtual servers in httpd.conf, but instead have them in sites-available and then ln -s them to sites-enabled.
I got this set of error messages, however:
Code:
# apache2ctl start
apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
But this was because I can't include "Listen 80". That's already taken care of in ports.conf. Finally, I changed the first line of the virtual host configuration files to <VirtualHost *>, and made sure I didn't have NameVirtualHost * on any virtual host except the default. Now it's fixed.
Last edited by gregmcavoy; 01-17-2007 at 11:25 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.