Hi, I'm a complete newbie, and I'm trying to set up a webserver with red hat 8.0 and apache.

when I try to restart apache, I get this error:
"(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80"

I'm guessing this means that something else is using port 80, but I don't know what it is or how to get rid of it. When restarting, I notice that a process called TUX starts up and says "TUX listening to 0.0.0.0:80" before HTTPD starts. Do I need TUX running? How can I get rid of it if I don't need it? Also, when I installed, I installed the DNS name server as well as Apache. I don't think I need the DNS, and if I don't, how can I get rid of it?

I changed apache to listen to all addresses on port 81 instead of 80, and it restarted with no errors. But I believe I need it to run on port 80. How can I identify what is running on port 80?

Thanks for helping a newbie out!

netstat -ap

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 *:http *:* LISTEN 10036/httpd

The process using port 80 is listed at the end.

To uninstall dns :

rpm -e bind

Assuming you installed bind as your dns, that is. Check with :

rpm -aq | grep bind

Slick.

the last tcp line given by netstat -ap is:
"tcp 0 0 servername:smtp *:* LISTEN 802/sendmail: accep"
the http line is:
"tcp 0 0 *:http *:* listen -"
There is just a dash under PID/Program name

I looked in /etc/mail/sendmail.mc (and sendmail.cf) and it looks like it only listens for mail on an internal loopback IP address (begins with 127.0....).

Ah um..

by end, I meant the end of the line lists what process is using it. Rather than uh.. the end of the list. My bad..

So um.. sendmail is good..

As you discovered you have something using port 80. Unfortunately I have no idea what 'tux' is. Well, Tux is traditionally the name of the penguin that is the mascot for Linux.

I'm only aware of one 'tux' program, and that's 'tux racer' which is a little x-windows game.

D'you know what this tux is doing? Or where you got it from?

First thing is first. Does your isp leave port 80 open? I had problems w/ this at first.

According to red hat, TUX is some sort of acceleration app. It came with the red hat 8.0 distro. I couldn't find any documentation on how to configure it.

I'm not sure if my ISP leaves port 80 open or not. I went to myserver.org/portsniff.asp and it said all of my ports were not detected. I'm not sure if this is a firewall problem coming from the linux box, or a problem with my router. I configured the router to put the Linux box in a DMZ, and turned off the routers firewall - I figure I'll get it working and then play with security.

Slick - I'm sorry for being obtuse, I'm a newbie. I wasn't sure what you meant, and there was no process listed by HTTP, so I decided to play it safe and list both.

One more thing, I've got a Windoze XP Pro box on the same network, and it surfs to the website just fine (and even thinks it is on the internet in doing so, as opposed to local intranet or whatever).

Thank you for any help you give me!

Oky... From RedHat's site :

http://www.redhat.com/docs/manuals/tux/
Red Hat Content Accelerator is a kernel-based, multi-threaded, extremely high performance HTTP server with the ability to serve both static and dynamic data. TUX is also an architecture for kernel-accelerated network services.

So, what you have there is (if my very brief perusal of the readme is right) is a web server running on port 80. Which is conflicting with Apache webserver's configuration (also trying to run on port 80).

Now, I've never used Tux. I have no idea how it's configured and where it puts its files. I also don't know if it's been installed on your system because of a requirement elsewhere.

But, you can *probably* safely remove it. I don't know.. don't blame me if stuff stops working.

Try looking for it's rpm

rpm -aq | grep tux

you'll probably see something that looks like :

tux-2.3.91-i386.rpm

In which case to remove it you would type :

rpm -e tux

Once it's gone, it should be removed from your startup, and you can get your Apache back on port 80 again.

As for wether your port 80 is blocked, you can be pretty sure that if you're on a cable modem it *is*, and if you're on dsl it isn't.

Slick.

OK, removed TUX and I think everything is cool...
It didn't give me any error messages (or say anything at all).

I then restarted apache (w/ "service httpd restart"), and didn't get any error messages.

Thank you so much Slick!

Now, I do have a cable modem. Is there anything I can do about my ISP blocking port 80? I know I can set apache to listen to other ports, but can I set up zone edit to forward my website name to other ports? I used zone edit because you mentioned it in another post here (i'm pretty sure it was you slick).

Woot.. Glad it's working.

As for getting around port 80 blocks. Um.. it's not easy.

It *can* be done, but it's rather fiddley. Unless you *really* have to be running something on port 80, then it's best to simply get by with the :81 addition.

But, basically you need to supply a hostname like www.wibble.com and define the www bit to forward traffic to wibble.com on port 81.

You run your web server on port 80 as normal, but use an iptables rule to re-write incoming port 81 traffic to port 80. That way your web server recieves it, thinks it's running on port 80 (which it is) and doesn't append the :81 to the end of the url when it writes back. But the traffic actually hits your machine on port 81, which isn't blocked... Um. hope that made sense.

There are dynamic dns hosts (which you'll need 'cos your ip address can/will change) who'll do the port forwarding for you. dns2go is one I use, but they charge um.. I think 10 bucks (a year.. doh) for their port forwarding service. They have a linux client which works well.

As for the dns.. not me mate, I didn't say nuttin 'bout any dns stuff...

Slick.

Btw TUX and apache can coexsist on the same server, what you could do is use tux for serving static files and pass off dynamic proccesses to apache.