Posted on: 02/19/03 08:07pm
By: Anonymous (tgotc)
Posted on: 02/19/03 10:22pm
By: Anonymous (Anonymous)
Posted on: 02/19/03 11:14pm
By: Anonymous (tgotc)
Posted on: 02/20/03 12:08am
By: Anonymous (Anonymous)
Posted on: 02/20/03 03:51am
By: Anonymous (Anonymous)
Would you happen to know which precise version of mySQL your site happens to be running? This may be a big clue to getting to the bottom of this.
Thanks.
Posted on: 02/20/03 07:01pm
By: Anonymous (Anonymous)
Posted on: 02/22/03 05:57am
By: Anonymous (Anonymous)
When I run phpMyAdmin, the second line of text shows "MySQL 4.0.10-gamma-log running on..."
Yep, that's the magic number. Ok, I think I can see what's happening now.
MySQL 4.02 and later provides some level of control over how much drain a database user can place upon the database server. There is a "maximum number of updates per hour" limit which, it appears, your activity on that day exceeded. Remember that Geeklog tracks things like the number of page hits, keeps tabs on your session and other housekeeping behind the scenes. This implies that each visitor to your web site will trigger database update activity. Exceed the max_updates_per_hour limit in a sixty minute period and the database server will start to squawk at you. Back off for a short while and all appears to be normal again...
GRANT USAGE ... WITH MAX_UPDATES_PER_HOUR 0;
If you never see that message again, you might not really care too much about taking any action. I guess it depends on how much activity your site sees.
If you're interested, you can read more about this in the Limiting User Resources[*2] section of the MySQL documentation.
I happen to be running version 3.x of MySql but after reading about your technical problem, I think it's time to consider upgrading to version 4.x at some stage, so thanks for helping to bring this to my attention!