Upgrade killed apache
Anyone else that has upgraded had any problems?
I just did all updates via WHM and now apache as dies and I am having trouble getting to come back to life. EVERYHTING on my box is D-E-A-D....
I also did the upgrade on Apache via the link in WHM, as it told me it was out of date. So I did it and recompiled it wil my needed items. Thats actually when it died.
cPanel.net Support Ticket Number:
It broke it for me too .... I'm running easyapache from the shell to see if it's buildapache or if the WHM script is just broken.
cPanel.net Support Ticket Number:
It worked for me but it took a longtime to restart!
cPanel.net Support Ticket Number:
also broken here on a fully loaded production server. Need a fix !!
cPanel.net Support Ticket Number:
That could be the problem. When it says "Done" you expect it to be done. Maybe we jumped the gun, and it wasn't finished yet.
cPanel.net Support Ticket Number:
odd....
I am running it from shell as well right now. I will post back after it complets.
WHY!! WHY do I do these bleeding upgrades??????? STUPID ME!
cPanel.net Support Ticket Number:
i tryed it running by shell. I used option 5 with gd + freetype.
www.fast-is.nl is the result..no images
cPanel.net Support Ticket Number:
How long? I waited 20 minues and Apache was still dead. Every site on that server is dead..... Hope running from shell fixes it!It worked for me but it took a longtime to restart!
cPanel.net Support Ticket Number:
No STUPID!!!! We're just curious!!Originally posted by blaze64
odd....
I am running it from shell as well right now. I will post back after it complets.
WHY!! WHY do I do these bleeding upgrades??????? STUPID ME!
cPanel.net Support Ticket Number:
cPanel.net Support Ticket Number:
Well, ran /scripts/easyapache from shell and this was the outcome:
..........finished.
13472 13471 13470 13469 13455
httpd: [ != HTTP/1..]
httpd has failed, please contact the sysadmin.
root@box12 [/]#
Damn.......
cPanel.net Support Ticket Number:
same hereOriginally posted by blaze64
Well, ran /scripts/easyapache from shell and this was the outcome:
..........finished.
13472 13471 13470 13469 13455
httpd: [ != HTTP/1..]
httpd has failed, please contact the sysadmin.
root@box12 [/]#
Damn.......
cPanel.net Support Ticket Number:
cPanel.net Support Ticket Number:
Does anybody know yet what went wrong?
cPanel.net Support Ticket Number:
If I do:
/usr/local/apache/bin/apachectl stop
It says stopped...
And then do:
/usr/local/apache/bin/apachectl startssl
It says
startssl: httpd started
What the hell? Is it or ins't it?
cPanel.net Support Ticket Number:
Does WHM tell if it is running or not? sounds like you got it to run again...Originally posted by blaze64
If I do:
/usr/local/apache/bin/apachectl stop
It says stopped...
And then do:
/usr/local/apache/bin/apachectl startssl
It says
startssl: httpd started
What the hell? Is it or ins't it?
cPanel.net Support Ticket Number:
cPanel.net Support Ticket Number:
WHM shows dead. And so do all of the accounts on that server as 100% of them can not be displayed. So I don't know who is lying but I think that shell is just a bit confused.
cPanel.net Support Ticket Number:
LinkBack URL
About LinkBacks
Reply With Quote
