Apache2 log_config_module : starting apache2 webserver.

 I am running an application in my webserver. I restarted my OS (SUSE Enterprise linux 10.1) and then when I tried to run apache2 I get this error.

bioch2022:/usr/local/ensembl # httpd2 -d /usr/local/ensembl
[Mon Oct 08 12:45:48 2007] [warn] module log_config_module is already loaded, skipping
(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
no listening sockets available, shutting down
Unable to open logs

I have cleared the files from the log directory and yet I am getting this error.

Can someone help me find out what is going wrong in this and how I would run the server.

Who is Participating?
Looks like some other process is binding to port 80 or may be apache2 is already running.

Before you start apache server try as root :
netstat -atp  | grep 80

This will show you what process is binding to port 80. Then you can either stop it or if it is apache2, you know it is already started.
i would agree with sanjooz on another apache may be running.

from my past experience with suse (and some other linux flav.) apache tend to be a common apps that would be installed by default -- especially when you select "server" mode during installation.

check the folder /etc/init.d/ and see if there is any startup script called httpd2. If there is, then probably apache2 (that comes with SLES) may already be running.  If this is the cases, do a "/etc/init.d/httpd2 stop", and try to start your custom apache.

another thing to look at would be the apache config.  Check if there are duplicate "Listen" directive that bind to the same port 80 (on the same interface).  This is another common cause for this error.

Forced accept.

EE Admin
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.