Yum Update and Upgrade, Now Apache Shows Red

[rustblack]

Hi,

I just ran through the Yum update and upgrade, now apache won't start properly. It actually is running, but it shows red in the Plesk panel.

RH9 Plesk 7.5.4

The odd thing, Plesk control panel works fine, but all the sites refuse connection. Apache doesn't come up in the list of processes. When I restart Apache is says Start-fail, Start=OK. If I restart it in Plesk, it says:

Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to stop

--------------------------------------------------------------------------------

0: /usr/local/psa/admin/htdocs/server/restart_services.php:28 psaerror(string "Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to stop")

--------------------
I don't see any other glaring errors in the logs. Other than the red apache icon in Plesk, it looks like there's a firewall blocking port 80...perhaps yum installed a firewall?? I'm not using Plesks' firewall at the moment.

Is this a good time to throw in the towel and switch to CentOS??

[scott]

Do you see the process running? I'll bet the init scripts are telling you its starting when it really isnt. Do you have more than 250 domains on the system?

[rustblack]

Well, httpsd is running, but that's all I can see. Only about 20 domains running...

[scott]

Nothing obvious comes to mind then, you'll have to get down into the weeds on debugging it. Try checking the error_logs when you start it.

[rustblack]

Okay, thanks. Nothing in the logs seems out of the ordinary.

Plesk panel works great because it's on 8443.....80 and 443 and refusing connection...

I'm stumped...although I'm 99.9999999 percent certain the server was hacked due to an Apache vulnerability. Having a problem after a Yum update is likely a symptom from that hack.

Peace out...

[scott]

Ah, if its an owned box, they may be running their trojan's on port 80 and 443, which might be why apache cant start.