exceeded max_questions resource [#32660]

Hello. I get the following error, sporadically :

Fatal error: User 'slackdad_hyper' has exceeded the 'max_questions' resource (current value: 50000) query: SELECT u.*, s.* FROM users u INNER JOIN sessions s ON u.uid = s.uid WHERE s.sid = 'ee6ee006ccc48c5272eb56358c39dbbe' AND u.status < 3 LIMIT 0, 1 in /home/slackdad/public_html/includes/database.mysql.inc on line 66\par }

When I called my server, they said they couldn't help because it's not their software, but they told me a trick, which was to add a user to my drupal database, which would cause it to refresh (apparently I'm only allowed 50000 queries/hour, but my site's honestly not that popular, and I've seen much bigger).

I lost my site once already, and it all started with this same error; I rebuilt it, and very slowly added modules, and had no problems for a couple of months. Then it started happening again, just like the first time: very rarely at first, and then more and more frequently. Any ideas?

Oh also, if it helps, I've been noticing goofy stuff since it started showing up again, like when I sign in, do something, hit "home", and I'm suddenly logged back out, with no changes made... Then I log in and everything's fine, hit "home", same thing... Is it a session ID thing? Something else going on?

Thanks in advance..

Comments

Comment #1

Richard Archer CreditAttribution: Richard Archer commented 7 October 2005 at 04:11

This is an error message generated by MySQL when the hosting service provider has set a limit to the number of database queries per hour a site is allowed and this limit has been exceeded.

Here's more info about this:
http://dev.mysql.com/doc/mysql/en/user-resources.html

I can see a couple of ways to address this problem:

Contact the host and have the limit lifted
Find a host that doesn't have limits
Enable throttle
Disable modules which are database-hungry

I can't see how this can be construed to be a Drupal problem or that there's anything beyond the ongoing optimization that Drupal can do to help with this problem.

I vote for closing this case.