Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm fairly new to Apache and to Linux. I'm trying to configure Apache to host a website. I've set up the information as best I can, but I get an error every time I try to start the httpd service. Maybe someone can define my error. Here is the error:
Starting HTTPD: (99)Cannot assign requested address: make_sock could not bind to address 172.16.1.3:80
No listening sockets available, shutting down
Any help is greatly appreciated as this is for a school project.
Something's got that socket bound up already, to find out what it is run: "netstat -nap --inet|grep -w 80|grep -i listen" (is it possible that apache's already running when you're trying to start it?)
That was the output for the command I gave you? Weird....
Try this one "lsof -i :80"
in the first column of the output will be the process that's listening on port 80, kill it
Something's already listening on port 80, or you have apache configured to listen on a non-existant interface, I'm assuming "172.16.1.3" is the ip you're trying to get it to listen on from your first post. if thats not correct you'll need to fix it in your httpd.conf.
You're right, I'm trying to congure it so that when someone types in my IP address 172.16.1.3 in their address bar they bring up my webpage. Would it help if I copy pasted my HTTPD.conf file here?
What, if anything is set as "bindaddress" in httpd.conf? also, are you certain that the ip address you gave is correct? Check the output of ifconfig eth0 (assuming you've only got one NIC and are trying to bind to it)
(if you're getting an IP from DHCP, change over to a static addy as well)
Edit ...also, just for S&G, run "apachectl configtest" to check your config files for accuracy....
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
Listen 172.16.1.3:80
#Listen *:80
I've already configured my IP address to be static. I'm the DHCP server on our project.
Nick
EDIT: The resut of that command was that the syntax was OK.
Would it matter if I wrote to the httpd.conf file using the GUI HTTPD tool and now am trying to edit it without that tool?
Thanks for trying to help, I really appreciate it.
Nick
EDIT: It only says that HTTPD service failed.
Oh by thje way, I've changed a few things since we began, and I am no longer seeing the error on the first post. All it says now is that the service failed withy no error message.
Maybe that will spark something.
Last edited by nickmoncrief; 04-08-2005 at 08:06 PM.
There's gotta be a simple explanation...it's just hard as heck going back and forth via a message board. Are you trying to run any vhosts by chance?
Also, if you can, go ahead and post your httpd.conf ...there's gotta be something amiss in there that apache's not seeing as an error, but is preventing it from starting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.