Actually this error won't stop the server from starting and serving web pages. You have a problem which is breaking your server _and_ your hostname is not set with the ServerName directive.
I have one that runs fine and gets this error, that's how I got to this thread 8) I set the ServerName directive with the same name that gets returned with the command: [root@foo.bar.com etc]# hostname foo.bar.com and server is now quiet. As well, it still works. If your server is registered in dns, you don't need to do this. Getting back to the server not starting... How do you know it's not starting? Can you see it in your process list? Can you browse it from the local machine? If you can't see it in the process list it's really crashing. There should be some pertinent information in the error log. What happens if you do an [root@foo.bar.com etc]# apachectl start [root@foo.bar.com etc]# apachectl --configtest Does it print something like: (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 If so it means the server is in fact running and you have an apache host configuration issue that's not letting you browse it, or you are typing the wrong stuff in the browser. This error from configtest means server won't start because it's configured to bind to port 80 and it can't bind to port 80 because 80 is already in use (most likely by the apache process that's running. hope this helps. I'll follow up if you provide more diagnostic info. -Viza |
edit the httpd.conf file
Under section 2: main server configuration. unhash # ServerName ....:80 and change the name after the ServerName to your FQDN name. ( hou can type hostname at the command line to see you server name) in my case it is ServerName UHS:80 |
Quote:
|
I had the same problem.. fixed it like this:
Code:
vi /etc/apache2/apache2.conf Code:
# ServerName Code:
/etc/init.d/apache2 stop |
I had the same message when I started apache2 server, and I added in my /etc/apache2/apache2.conf file the line:
Servername myservername.mydomain.net as antken mentioned above, restarted the server and it didn't print out this ugly message anymore. Thanks. |
hi there. i've recently installed apache2 and am getting the same. my hostname and the servername in the default config are both the same (i added the servername to the server config) . have i missed a step?
thanks |
hello,
I have the similar problem. However, my setup might be slightly different from what I have read. I run one box with several (named based) virtual servers. I am not sure, but I think the Apache message started to appear after I did a Debian apt-get upgrade, which upgraded mostly everything on my server... The functionallity is ok, even though the Apache message keeps comming. The Apache.conf-file is setup with no global ServerName-directive. I don't want a fallback if a lookup fails. Instead, I have a NameVirtualServer *:80 which servers as a catch-all directive. Then, I have one VirtualHost-block for each of the virtual servers. Inside this block I have the ServerName directive which corresponds to the virtual server. This setup works ok, but as I said, the Apache-message "suddenly" keeps comming up, and I don't know why... :| One more thing, though, for the curious. To have name-based virtual servers work as I described, you have to put the names of the virtual servers in your hosts file. Since Apache uses reverse lookup to find out it's server name, I also configured bind/named to be a local authorative on the LAN network. This also has to do with Sendmail, which is rather strict on lookups. If someone has any comment or hunch to where to start looking, please post! :) t. |
I am using fedora 6... but this should be applicable to all.
Go to System --> Administration --> Network (that's same as the good old redhat-config-network) go to the dns tab and enter the hostname as localhost.localdomain now go to hosts ... and edit the hostnames as u like. now edit the httpd.conf and add the line ServerName yourservername and lastly edit the line canonicalname CanonicalName On ... and there u have it.... it will work from anywhere in da world wid ur ip .. AND u get ur own server name |
syddel, that worked for me too!
thanks a bunch :) |
I read the whole thread and tried following some of the instructions people suggested. Unfortunately, none of them worked for me. Here is my set-up:
I own alkos333.net, but since I'm running apache on my laptop, I don't have a stable ip address to point the domain name to. Here is some information about the set-up: Code:
me@laptop0:~/slackbuilds/packages$ cat /etc/HOSTNAME |
I've a dynamic IP, too, and in my /etc/hosts file I didn't include the 'fully qualified domain name' like your laptop0.alkos333.net laptop0. For localhost, I have only a line like:
127.0.0.1 localhost laptop0 and, in my /etc/apache2/apache2.conf I've added the line like: Servername alkos333.net |
I've tried setting it up just like you said. My /etc/hosts now has only one line:
Code:
127.0.0.1 localhost laptop0 |
apache mod ssl on freebsd
all, need your help for the problem
i am installing snort @ freebsd6 however stuck on the apache. i successfully installed apache+mod_ssl-1.3.37+2.8.28, however when starting the apache (./apachectl start), it gives just nothing. no error though, but not running as well #./apache.sh status apache is not running #./apachectl status lynnx: not found any ideas/solutions? thanks before |
Quote:
|
sorry guys..
|
All times are GMT -5. The time now is 07:42 AM. |