[Solved] svensbluff web server down due to cPanel update problem
9:24 AM RESOLVED - We’ve rolled-back cPanel to 11.23.6 and Apache is magically running fine!! :) We’re opening a ticket with cPanel to have them repair whatever is wrong with 11.24.0 that is breaking legacy Apache.
In the meantime we have disabled this cPanel upgrade so it will not run again before we have this bug sorted out.
We are considering this case “closed” for the sake of this posting, however we will post here further as we continue to work on it later today.
Again we are very, very sorry for the trouble this morning!! If we had known cPanel’s handiwork was going to kill the server, we would not have allowed it to update.
Thank you for your patience!!
DCSN Support Team
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9:14 AM – We’re still working on this with no ETA as of yet. We will post further updates as we know more. ##
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Good morning,
This morning our server ’svensbluff’ auto-updated to cPanel 11.24.0, which appears to have killed Apache (the web server). Despite a thorough investigation, we’ve been unable to determine why exactly Apache will not run, other than it obviously appears related to the cPanel update.
We are recompiling Apache as we speak in an attempt to restore service.
We will post further updates here as they become available. Thank you for your patience!!
November 2nd, 2008 at 1:51 pm
By legacy Apache, do you mean an Apache install performed before EasyApache 3? Please provide further information as we are unable to locate the ticket you mentioned in your post that you would open with us.
Kenneth
cPanel QA
November 3rd, 2008 at 2:30 pm
First, in reply to cPanel-Kenneth:
Kenneth and I had a looooong exchange of emails last night. He was really nice to work with and offered several trouble-shooting tips. He also offered that they were going to try to re-create the situation a test machine at cPanel. (Frankly, I don’t think they’re going to be able to re-create it, because we have several dedicated clients running identical setups and their machines are all 100% fine since the 11.24.0 update.) It ended up that we didn’t need to do all that testing — which I was reluctant to do anyway, because I didn’t want customer sites to be down, that’s first & foremost — because I opted to do a huge upgrade on this machine instead in the hopes it would circumvent the fluke entirely.
The Apache, MySQL and PHP upgraded did indeed resolve whatever problem (fluke) had caused the problem between Apache 1 & cPanel 11.24.0. So as far as we are concerned …….. PROBLEM SOLVED. And customers are getting the absolute best service as a result because we’re now operating on Apache 2.x, MySQL 5.x and PHP 5.x. :)
I want to thank Kenneth at cPanel for taking the time to contact me as well as email with me in great depth about this on a Sunday night… I wasn’t expecting that at all and I really, really am appreciative of it.
~ Karin