| Linux - Server This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
12-17-2008, 02:18 PM
|
#1
|
|
Member
Registered: May 2007
Location: Cork (Ireland)
Distribution: FreeBSD 9.1
Posts: 151
Rep:
|
LAMP with Debian Etch on a Virtual Machine & Leopard as host
Hi Guys
I am trying to install LAMP on Debian Etch VM. I have installed LAMP following the link below but now I am faced with problems
http://linux.justinhartman.com/Setting_up_a_LAMP_Server
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
|
|
|
|
12-17-2008, 02:46 PM
|
#2
|
|
Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 12,008
|
Quote:
Originally Posted by riganta
Hi Guys
I am trying to install LAMP on Debian Etch VM. I have installed LAMP following the link below but now I am faced with problems
http://linux.justinhartman.com/Setting_up_a_LAMP_Server
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.
Last edited by TB0ne; 12-17-2008 at 02:49 PM.
|
|
|
|
12-18-2008, 02:17 AM
|
#3
|
|
Member
Registered: May 2007
Location: Cork (Ireland)
Distribution: FreeBSD 9.1
Posts: 151
Original Poster
Rep:
|
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..
Cheers
Riganta
Last edited by riganta; 12-18-2008 at 04:34 AM.
|
|
|
|
12-18-2008, 08:52 AM
|
#4
|
|
Guru
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 12,008
|
Quote:
Originally Posted by riganta
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.
|
|
|
|
12-18-2008, 10:35 AM
|
#5
|
|
Guru
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870
|
A "netstat -pantu" should show you what is using it.
BTW, I'm moving this to Server as it's not a security issue.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:59 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|