Kuroro Luc
06-05-2004, 07:00 PM
Starting httpd: httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
[Sun Jun 06 06:58:12 2004] [error] VirtualHost _default_:443 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results
[Sun Jun 06 06:58:12 2004] [warn] NameVirtualHost xx.xxx.xx.xxx:0 has no VirtualHosts
[FAILED]
Above is the error message I got when tried to Start httpd Apache 2...:(
Anyone know what might be the problem and how to fix it?
Thanks.
CArmstrong
06-05-2004, 07:09 PM
The error tells you exactly what happened. Find the VirtualHost configuration section of httpd.conf and do what it tells you to do: either specify the port for all entries or remote the port for all entries.
Kuroro Luc
06-05-2004, 07:19 PM
hmm what do you mean?
The Apache server was working fine until suddenly it stopped. When I tried to start it again, those error messages appears.
I'm not sure by what you mean by Find the VirtualHost configuration section of httpd.conf and do what it tells you to do: either specify the port for all entries or remote the port for all entries.
Kuroro Luc
06-05-2004, 07:33 PM
Ok I've edited httpd.conf and somehow all the errors disappear except for the "Starting httpd: httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName"
What do I have to do with this one? Thanks.
pizzaboy_au
06-05-2004, 09:17 PM
The fully qualified domain name is the servername of your server.
For example delta.domainname.com
It is the internet name of your server. It is using 127.0.0.1 which is localhost because it can not find a valid servername.
Kuroro Luc
06-06-2004, 05:58 PM
Where can I change it? Why it doesnt need servername at first and its working fine?
Is it this one on httpd.conf : ?
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
#
ServerName xxx.xxx.xxx.xxx:80
Thanks
Daniel53
06-06-2004, 09:30 PM
You might want to check your hosts and resolv files for the correct info.
CybexHost
06-06-2004, 10:42 PM
vi /etc/resolv.conf ;)
You can edit what should be edited there.
linux-tech
06-06-2004, 11:50 PM
httpd technically doesn't need a servername. You can call it joe.shmoe.com and httpd won't care. The only thing you'll have a problem with is anything in your default <virtualhost> setting unless you've specifically define the sub.domain.name there.
None of those errors in fact are critical errors. They won't prevent http from starting up though mixing ports might be a bit touchy. Most likely you've got an error somewhere else. Check your error_log right after starting the server up, see what it says.