Reputation: 51
I upgraded to OS X Mavericks and I am trying to start the apache web server
I am using the command
sudo apachectl start
to start the server but I get the following error
(13)Permission denied: make_sock: could not bind to address [::]:80
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
Upvotes: 4
Views: 19368
Reputation: 346
Another service is running on the port 80.
Check the service by execute this command:
sudo lsof -i :80
Stop the service before you run start the apachectl.
Upvotes: 0
Reputation: 148
had the same thing this morning, out of the blue..
I found that running :
sudo /Applications/AMPPS/apache/bin/apachectl start
at least gave me some info :
AH00544: httpd: bad group name administration
so I typed (in terminal)
groups
to see which groups were available and found that there is no administration group but there is admin group
so I went into httpd.conf and found the user/groups config section and changed accordingly and -surprise!- apache started!
Upvotes: 2
Reputation: 2351
Have a read of this blog post
It sounds like you're not seeing the same "silent terminating" thing, but maybe you have a similar problem, that with Maveriks superfluous "Listen 80" line in another config file will now trip up apache. So check if you have a config file under /etc/apache2/users , and also check VirtualHosts which maybe configured in /etc/apache2/extra/httpd-vhosts.conf (or try temporarily disabling these)
Upvotes: 0
Reputation: 3322
Official Bug Fix is here, so you can manage it from UI.
Also sudo apachectl start/stop
is for apache bundled with Mac OS X.
Type the whole path as suggested by Daniel above.
Upvotes: 0
Reputation: 91
With AMPPS or any other app, you can run it through Terminal:
Start $ sudo /Applications/AMPPS/apache/bin/apachectl start
Stop $ sudo /Applications/AMPPS/apache/bin/apachectl stop
Upvotes: 9
Reputation: 2652
Here is what u can do.
Make sure the server is turned on with sudo ( root ) but I assume this is going just fine since u are using sudo in your start post.
The other way to solve this is to check in your
/etc/apache2/httpd.conf
And change the listen port from 80 into 8080 or anything greater than 1024
Upvotes: 0