Unable to connect to port 80

[tanjilkamal]

Hi,

httpd on server1.npowerhost.com failed
httpd failed @ Sat Dec 26 01:11:30 2009. A restart was attempted automagically.
Service Check Method: [tcp connect]
Failure Reason: Unable to connect to port 80

I am getting flood of above messages in my email box, from my new linux whm dedicated server. I went to restart HTTP Server (Apache) but is says:
"httpd has failed, please contact the sysadmin". I checked the firewall configuration though puttey (ssh) with setup command and it is enabled. But is does not show that block port 80.

when i check the Apache status from whm panel it shows "Failed to receive status information from Apache. Unable to connect to local httpd server"

Also when i try to check Include Editor under Apache Configuration in whm panel i see this error message: Sorry, you cannot update the include files at this time. Your Apache configuration file currently has a syntax error.
Error: Syntax check failed. Unable to locate executable Apache binary

when i try to use this command "/etc/init.d/httpd restart" in puttey to restart Apache is says no such file or directory exit.

Also when i try to use /usr/local/apache/logs in puttey (ssh) it says that no such file or directory exit!


my no domain cpanel load using the browser even! not even the domain itself!

Any solution for this?

Tanjil

[markb14391]

Getting the same thing on a new 11.25 server. It isn't in production yet and I haven't had time to troubleshoot this yet...but it's kind of funny...dozens of these e-mails per day.

[tanjilkamal]

Hi,
thanks i have solve the problem. If anyone suffering from this problem then please goto Software - EasyApache in whm panel and then rebuild the apache system. It will take 15 minutes and Apache server will start running again!

Cheers!!!!!

Tanjil

[madaboutlinux]

Right, you need to recompile Apache if you receive a module missing OR Apache directory missing error message. You can compile Apache from WHM >> Software - EasyApache OR using /scripts/easyapache script.

[markb14391]

Now it's happening on another brand new server.

Funny, I already rebuilt Apache. I always do that when launching a new server...I rebuild Apache and PHP the same way every time.

But on 11.25, httpd breaks a few hours later. It just stops working. In this case it stopped after I set up DNS clustering, which definitely shouldn't break Apache. I shouldn't have to rebuild Apache (again) to fix what should already be working.

The other question is: When will it break again? With 11.25 Apache seems to break if you look at your server the wrong way.

Sorry to sound so negative, but if I could regain the hours I spent in the past two years troubleshooting cPanel bugs, I would have a lot of time on my hands. As my wife/partner says, "Why doesn't it ever just work the way it's supposed to?"

[markb14391]

Update: In a ticket I was told that Apache breaks in 11.25 when you activate the mod_userdir tweak before adding an account. Someone else from cPanel confirmed this in another thread. So it's an easy solution as long as you know the order of events involved.

[cPanelDon]

Update: In a ticket I was told that Apache breaks in 11.25 when you activate the mod_userdir tweak before adding an account. Someone else from cPanel confirmed this in another thread. So it's an easy solution as long as you know the order of events involved.

Specifically regarding the above, to cross-reference another thread (so others in this thread are aware), please see the following two posts that detail a potential scenario that could trigger difficulty with Apache:
cPanel Forums - View Single Post - cPanelCory

I just wanted to clarify the Apache issue as it is a known issue and being worked on but it only occurs in a very limited and specific way that most users will not encounter.

On a fresh install of cPanel if you enable the Apache mod_userdir Tweak in WHM *BEFORE* adding any accounts there is a problem with blank UserDir directives being placed in the httpd.conf file which will keep Apache from starting.

In most cases clients will never run into this situation and it is being reviewed at this time to be fixed.

We do apologize for any inconvenience this may have caused.

Thank you,

cPanel Forums - View Single Post - cPanelCory

Hi Mark,

Indeed the scenario you described was the only people I could think of this would really affect, and had imagined that was how you were getting to the issue.

Again, we apologize for the inconvenience and hope to have a fix out shortly to fix this issue for you.

Thanks again,

[markb14391]

Yep, I don't mind things like this when I know the steps that cause the issue. It was the "not knowing" that was the problem. I just happen to have a certain routine for setting up and hardening a server, and it involved the steps in a certain order.

So it's no problem now that I know how to avoid it. Thanks!

Mark