Apache Server Not Starting

sandeepshanu · 01-04-2011, 03:14 AM

Hi Frnz,

I am getting following error in starting the apache:
Starting httpd: (13)Permission denied: make_sock: could not bind to address 10.136.167.21:88
no listening sockets available, shutting down
Unable to open logs
[FAILED]

I have logged in as root and no other process is using port 88.
In httpd.conf i have provided "Listen 10.136.167.21:88".

I am doing it in virtual server Centos 5.
There is one more such server and same configurations settings are working fine in that. I have also compared httpd.conf, except IP there is no difference.

Can anyone tell what could be the reason for this error?

Thanks in advance..
Regards
Sandy

bathory · 01-04-2011, 03:44 AM

Hi and welcome to LQ,

This is due to SELinux that by default does not allow apache to bind on port 88.
You can run:

Code:

semanage port -a -t http_port_t -p tcp 88

and try again to start apache

Regards

sandeepshanu · 01-04-2011, 04:46 AM

Quote:

Originally Posted by bathory

Hi and welcome to LQ,

This is due to SELinux that by default does not allow apache to bind on port 88.
You can run:

Code:

semanage port -a -t http_port_t -p tcp 88

and try again to start apache

Regards

Thanks for giving quick reply.
Its saying /usr/sbin/semanage: Port tcp/88 already defined
When i changed port to 80 or 8080, its working fine.

bathory · 01-04-2011, 05:13 AM

In the default SELinux ports policy, port 80 is allowed for apache and port 8080 is allowed for http_cache, that also is a common port for apache if used as a web proxy.
If port 88 is allowed, then it should work. What gives

Code:

semanage port -l | grep http

Maybe you need to define just

Code:

Listen 88
NameVirtualHost *:88
<VirtualHost *:88>

in httpd.conf, instead of using the full IP address

ort definition

ComputerErik · 01-04-2011, 07:16 AM

Also what user are you trying to run this as? By default you will need to start as root to access a low numbered port and then switch the process to a less privileged user after the fact, which is usually taken care of by specifying a user in httpd.conf.

sandeepshanu · 01-11-2011, 09:22 AM

Thanx Guyz For Ur help..
Issue is resolved now..