Exceeded CPU Quota?
New Here? You may want to Subscribe to my RSS feed for daily updates. Or if you prefer, 
Subscribe by Email Thanks for visiting!
 Moderate and possibly incoherent Rant Ahead.Â
3:50 til 9:32 My site was down yesterday and I didn’t even know it. Consulting with John using CrossLoop, didn’t bother looking at my own site as I was busy trying to make some money.
Just happened to notice when I checked to moderate spam comments and couldn’t access my site through the link in email. I tried to log in manually and got an error that I had exceeded my CPU Quota!?!
I checked my main site, (webpage) same thing. Archive, Joe’s finds same thing. Looked through the rest of email for any indication and found a notice from BlueHost that they changed IP addresses. It’s a shared server. I figured that if it was down for so many hours and wasn’t fixed, I WANTED TO TALK TO SOMEONE.
We checked the Files on the server itself and it showed that Google had indexed and they (at BH) thought that could have taxed the service and caused the excess usage. However, they investigated further (at my insistence) and found that others were having the same problem on the server that we shared.
Apparently there was a corrupt file in the script of the changover and that put the whole server (they have more than one) down for hours. It seems that others had reported the problem through regular channels (email). But I Called on the Phone, this should have been fixed Long Before I found it.
I apologize to everyone who participated in Yesterdays Working at Home Blog Carnival for the lack of exposure that may have resulted in the downtime I experienced.
This is the First Major Outage I have experienced since signing up with BluehHost last June. Did Anyone else who uses BlueHost have similar problems yesterday, ever?
Related Posts:
Promote Your Home Business on the Featured Home Business Page... no charge, but no splogs allowed
My Skype: joe.hauckes
Joe - I’ve had this error a few times - mostly when my site hits the front page of digg.
But a bunch of other sites I help with has a similar problem on digg - they’re podcast sites, so on the day when the podcast is launched and it gets a lot of quick downloads, I get the error.
I’m in the process of TRYING to move - but right now a nameserver change isn’t taking affect and it’s driving me nuts. I’m moving to A Small Orange on 2 solid recommendations I received.
Input by Ben Yoskovitz | March 18, 2007 @ 7:42 pm
Hey Ben,
No idea what kind of problems THAT could cause.
This seems to be a one time thing from what Bluehost is telling me. It more than likely was caused by the change over that they were doing combined with a corrupt script and being crawled by Google at the same time (from what they could figure out).
I never made the Front page of Digg or anywhere else for that matter.
I thought of using A Small Orange (recommended by Chris Cree) but worked out a nice deal with BlueHost instead. I hope I don’t end up regretting it, although this is the first major outage I’ve had since last June. That’s Really Long in Internet Years.
Call me if you think I could be of any help in your move.
Input by Joe | March 18, 2007 @ 9:01 pm
Joe - looks like the nameserver for Instigator Blog finally kicked in after I called Bluehost again - so I’m over at ASO now. We’ll see what happens when I go for the front page of digg again. *smile*
Bluehost’s quota thing has happened to me 4 or 5 times. If you want more CPU usage you have to go up to $19.99/month (but they’ll put you on a waiting list first.)
Digg does send thousands of visitors in a very short period of time - so it is unusual in terms of traffic patterns - but I need a host that can support that.
Bluehost claims it’s WordPress and/or the plugins that cause the problems. That’s probably true (although even after I disabled all the plugins I was still having trouble) due to inefficiencies with how WordPress/plugins hit the database. But considering there are millions of far more heavily trafficked sites than mine out there on WordPress there has to be a hosting company that can handle it without charging me thousands of dollars.
Let’s hope I’ve found one cause moving hosting companies is painful.
Input by Ben Yoskovitz | March 18, 2007 @ 9:09 pm
Ben,
When I first saw the CPU message, the first thing I thought was someone Dugg me and that caused the overage. Wrong…
Maybe someday (if I ever learn how to write).
Until I have the need for more capability, I’ll stay with what I have. As you said about moving, it’s painful.
The one thing I DO like about BH is if I call, I talk to people who are involved with the inner workings and actually get some real answers. They worked with me the other night until we found out the right answer. Not just some stupid S*** to get me off the phone.
Let me know how things work out with the move to ASO, just in case I ever get that much traffic all at once.
Input by Joe | March 18, 2007 @ 9:23 pm
It took 3 phone calls to resolve the nameserver issue. I don’t know how many times you’ve called Bluehost but I’ve definitely had mixed results. The last guy solved the problem in 10 seconds - clearly he knew what he was doing. The others didn’t.
Hosting is a crap shoot. ASO could be worse, we’ll have to wait and see.
I’ve recommended Bluehost in the past and would probably keep doing so since their support has been BETTER than many other hosting companies I’ve dealt with. But I probably wouldn’t recommend them for heavily trafficked sites because of that CPU issue.
Input by Ben Yoskovitz | March 18, 2007 @ 9:28 pm
Ben,
I have only had need to talk to them about 3-4 times and they were always helpful. And they are willing to listen to what I have to say and stayed with me until whatever problem was resolved.
The only thing I have any regrets about(so far) is that when I changed over to WP from Blogger, they advised me to create a folder for the WP download. THAT’S why I have /WP for this Blog. :-}
Input by Joe | March 18, 2007 @ 9:43 pm
Trackbacks
Sorry, the comment form is closed at this time.