I had SM techs look into this, each time they do somethign the problem just keeps coming back, I have no idea what their doing, I ask what theyve done but they dont tell me, everytime its the same error over and over

[Wed Dec 17 20:52:17 2003] [warn] pid file /usr/local/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Wed Dec 17 20:52:17 2003] [notice] Apache/1.3.29 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.2 PHP/4.3.3 FrontPage/5.0.2.2634 configured -- resuming normal operations
[Wed Dec 17 20:52:17 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Wed Dec 17 20:52:17 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Wed Dec 17 20:52:17 2003] [crit] (98)Address already in use: make_sock: could not bind to port 80

Originally this started out as port 443, sometime around saturday last week, but I have closed that port, now it says port 80. I have done apache rebuilds three times now, SM did it once. 4 reboots, nothing the error just keeps coming back.

SM wants 75 bucks to reload my software, and then I have to restore the accounts.

What gives?? Why is apache erroring out?

Try running
in a ssh session -- what does it return? You an also try

BTW what version of Apache are you running, 2? Are you running a PHP accelerator? CPanel?

lsof -i tcp:80


Mine shows this, I am worried about the 3 (ESTABLISHED)???????

edit! nevermind I had another idea thought maybe my drive was going bad... sure enough it is. So im gonna have a new drive and o/s reinstall done!

edit! double post :shock:

Those represent the IP's of the people who are currently accessing your Apache webserver.
Try browsing to your site and then run lsof -i tcp:80 again and you will see your ip there as well

Is there a fast way to ban a IP from the server at the shell command prompt?

yea, just make sure its not your own your doing, otherwise youll lock yourself out of the system...

iptables -A INPUT -s ipaddress -j DROP

replace ipaddress with the ip you want to ban

Thanks!

Guess I should study the iptables command more and later set up a 48 hour cron job delay to make it so it auto removes the banned ip. But for a crisis it should work nicely for now!!!!