LAMP with Debian Etch on a Virtual Machine & Leopard as host
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
when i restart my web server i get this error message
' Forcing reload of web server (apache2)...httpd no pid file not running
(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 0.0.0.0: 80
no listening sockets available, shutting down. Unable to open logs
I would really appreciate your help out there. I am really stuck and don't really know where to look. Is the problem due to the fact that I am running Debian in a VM? I do understand that there is no socket available for the webserver to listen too but do not know how to fix that problem.
when i restart my web server i get this error message
' Forcing reload of web server (apache2)...httpd no pid file not running
(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 0.0.0.0: 80
no listening sockets available, shutting down. Unable to open logs
I would really appreciate your help out there. I am really stuck and don't really know where to look. Is the problem due to the fact that I am running Debian in a VM? I do understand that there is no socket available for the webserver to listen too but do not know how to fix that problem.
Thank You.
Riganta
Something else is using port 80. Either your Apache server never really stopped, you're trying to start a second instance on the same port, or some other program grabbed port 80.
Do an apache full-stop, then do a "ps -ef | grep htt", to see if you've still got a thread running. If you see any httpd stuff running, and you're SURE things are ok, kill -9 those PID's. After that, crank Apache back up.
If everything does stop, then you'll have to find out what other services could be running on port 80, and either change them, or change Apache, to use a different port.
how can I simply find out what is taking my port 80 and kill it in my VM ?
I ran a test and configured apache to run on port 443. My Web Server started without any problem. As soon as i put port 80 i get the same error message.
I ran ps -ef | grep htt as advised by TB0ne but i didn't get any result at all. There is nothing that seems to be running at all on port 80.
I thank you all for your help.
Riganta
Quote:
Originally Posted by TB0ne
Something else is using port 80. Either your Apache server never really stopped, you're trying to start a second instance on the same port, or some other program grabbed port 80.
Do an apache full-stop, then do a "ps -ef | grep htt", to see if you've still got a thread running. If you see any httpd stuff running, and you're SURE things are ok, kill -9 those PID's. After that, crank Apache back up.
If everything does stop, then you'll have to find out what other services could be running on port 80, and either change them, or change Apache, to use a different port.
I have done "ps -ef | grep htt
I get no results --> there is actually nothing running. when I try to start up apahe I still get the same result. when I try to stop it, it says "stopping web server (apache2)... httpd (no pid file) not running.
I am kind of lost there..
how can I simply find out what is taking my port 80 and kill it in my VM ?
I ran a test and configured apache to run on port 443. My Web Server started without any problem. As soon as i put port 80 i get the same error message.
I ran ps -ef | grep htt as advised by TB0ne but i didn't get any result at all. There is nothing that seems to be running at all on port 80.
Well, SOMETHING is running on port 80, obviously. It's hard to say what, since you don't say what other services are running on the box. Did someone install Tomcat/Resin, and is it using port 80? Webmin? Really, almost ANY network-enabled service could be configured to use it, so without knowing what you've got loaded, it's hard to say what it is. Look at the netstat command, and it can give you further information.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.