Page 1 of 5 123 ... LastLast
Results 1 to 10 of 42

Thread: CPU Quota exceeded every DB backup

  1. #1
    Join Date
    Mar 2006
    Posts
    1

    Exclamation CPU Quota exceeded every DB backup

    Hello to everybody...
    Everytime I make backup of my database I get the CPU quota error and site is down for some minutes...I asked support but never got an exhaustive reply.....they told me "we have done backup of your database and no errors" .....but every time I make it it's always the same story

    Does it happen to anybody else....???
    Is there a way to get rid of the problem...???

    Thanks in advance

  2. #2

    Default

    I get that annoying cpu quota crap every single day and I'm seriously thinking of moving to a different server.

  3. #3
    Join Date
    Feb 2006
    Posts
    177

    Default

    Quote Originally Posted by Zabref
    Hello to everybody...
    Everytime I make backup of my database I get the CPU quota error and site is down for some minutes...I asked support but never got an exhaustive reply.....they told me "we have done backup of your database and no errors" .....but every time I make it it's always the same story

    Does it happen to anybody else....???
    Is there a way to get rid of the problem...???

    Thanks in advance
    We know of this happening during backups, and it should not happen. It's on our list to fix, but I have a few higher priority things to take care of.

  4. #4
    Dave Guest

    Default

    Quote Originally Posted by rando
    We know of this happening during backups, and it should not happen. It's on our list to fix, but I have a few higher priority things to take care of.
    Higher priority things such as the system wide favicon.ico push.

  5. #5
    Join Date
    Feb 2006
    Posts
    177

    Default

    Quote Originally Posted by Dave
    Higher priority things such as the system wide favicon.ico push.
    I actually didn't even know about the favicon.ico push until after it happened and people started complaining.

    What's been eating up my time in the last week is working on newer efforts to protect against people abusing our network to send spam. Last week someone exploited something and killed our outbound mail cluster for a day and a half while I tracked down who it was and how he was doing it.

    This is on my project list, but there really are more important things right now. I'd really like to get to it soon, but when there's mail issues which affect every customer who is sending email, they kind of take priority over something that affects so few customers. This doesn't even affect everyone who uses the backup software, you have to have some pretty big databases for it to happen.

    Anyway, as a workaround, if you're feeling brave enough, you can have shell access enabled on your account and log in and do this directly with the mysqldump command. That, or only run your backups at night, where a 1-2 minute cpu restriction won't bother many people. I promise I'll get to this as soon as I can, but unfortunately I'm only one guy and since these are actually fairly difficult things to do, it's a little hard to pawn them off on one of the junior developers.

  6. #6
    Join Date
    Feb 2006
    Location
    Texas
    Posts
    11

    Default Yes

    I get this same message when i back up also.

    I called once and was told it's due to a PHP script running and not finishing in "X" amount of time. I've forgotten what that amount of time was.

    Like Rando said, back up in the evening, that's what I do, it's no big deal.
    Scott
    MOPAR! If you have to ask you won't understand!
    http://www.sweptline.ORG

  7. #7
    Join Date
    Feb 2006
    Posts
    177

    Default

    Quote Originally Posted by HellBelly
    I get this same message when i back up also.

    I called once and was told it's due to a PHP script running and not finishing in "X" amount of time. I've forgotten what that amount of time was.
    That's not entirely correct. It's not how long it takes to run, but how much actual processing time it takes. You shouldn't be blamed for the backups, and I am going to get to that soon.

  8. #8
    Join Date
    Nov 2006
    Posts
    5

    Default

    I recently joined Bluehost and this is happening to me. It's an awful a nuisance.

    Is it still happening to other people?

  9. #9
    Join Date
    Feb 2006
    Location
    Somewhere where I don't know where I am
    Posts
    2,155

    Default

    Quote Originally Posted by Nigel
    I recently joined Bluehost and this is happening to me. It's an awful a nuisance.

    Is it still happening to other people?
    They should have had this fixed. If you're still having problems, then you should contact bluehost support.

    They only thing that I would suggest would be to do it in parts.
    Sign Up Now!
    Unlimited Storage, Unlimited Transfer, Host Unlimited domain names, 1 Free Domain Name
    BlueHost Features | BlueHost Help Desk | Become a BlueHost Affiliate | BlueHost CEO Blog
    (888) 401-4678 | Create a support ticket

  10. #10
    Join Date
    Sep 2006
    Posts
    7

    Default Letter to Bluehost regading recent CPU overage policy changes

    I have written a letter to Bluehost regarding the apparent change in CPU enforecement, as evidenced by the numerous posts on this forum. I am very disappointed by the way this has been handled....

    Dear Bluehost,

    I have contacted Bluehost tech support recently regarding repeated excessive CPU Usage messages I have been receiving lately.

    Nothing about my account has changed recently - number of users visiting the site has effectively stayed constant, and even decreased slightly over the last month.

    I was assured by Bluehost support that nothing has changed as far as Bluehost's CPU policy - however I have never had this problem before. My site has effectively been shutdown by this CPU overage policy. In order to attempt to fix the problem, I shut my site down completely, and even with only myself using the site, I still get these CPU overage errors.

    I went to Bluehost's customer forums to see if there have been any others with this problem, and have been very disappointed to see that there are many others who have been experiencing the same problem recently. Clearly there has been a change in Bluehost's policy on CPU, or at the very least, the enforcement of the policy.

    Please see the following threads for a reference to what I am talking about. It appears that this policy began to be enforced on some boxes at the end of August. There have been no references on the Bluehost forum prior to this date about CPU overage errors.

    http://www.bluehostforum.com/showthread.php?t=2960

    http://www.bluehostforum.com/showthread.php?t=2121

    http://www.bluehostforum.com/showthr...ighlight=quota

    http://www.bluehostforum.com/showthr...ighlight=quota

    http://www.bluehostforum.com/showthr...ighlight=quota

    Clearly there are many others who have been ambushed recently by this policy.

    I was told that in order to solve the problem, I would have to pay $30 per month to move to a high CPU box. Had Bluehost told me about this change in policy prior to implementing it, I might have understood and decided to move to a high CPU box of my own volition. However, I am very upset that Bluehost has decided to effectively shutdown my site by changing its CPU overage enforcement. This has created strain on my site development, and has cost me money by lowering my site revenue. It is entirely inappropriate.

    I am asking that Bluehost acknowledge at the very least that they have modified their CPU overage enforcement, and allow its customers to decide whether or not the service is still for them.

    Failing this acknowledgment, or a reversion to the old CPU policy which did not repeatedly shutdown my site, I will be cancelling my account with Bluehost quite soon, and will no longer refer others to your service. I am clearly very disappointed with what has transpired over the last few weeks.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •