Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By ijulie on
I'm running an (admittedly jerry-rigged) version of drupal 4.5, and my hosting was recently suspended because one of its processes crashed their SQL server (or so it seems). the problem moment was a long string of queries that looked like this:
| 100186 | russoj_russoj | localhost | russoj_julie | Query | 21 | Copying to tmp table | SELECT url, MAX(timestamp) AS last_hit, COUNT(url) AS hits FROM accesslog WHERE url <> '' GROUP BY u |
| 100187 | russoj_russoj | localhost | russoj_julie | Query | 21 | Copying to tmp table | SELECT url, MAX(timestamp) AS last_hit, COUNT(url) AS hits FROM accesslog WHERE url <> '' GROUP BY u |
a) does anybody know what module might have caused this, so I can either turn it off or fix it?
b) is there a more global way to limit the number of simultaneous connections to mysql to avoid flooding the server?
thanks...
Comments
throttle?
(I turned on throttle in hopes that that might help.)
cron?
I think that's from the statistics module.
Are you running cron regularly to prevent accesslog bloat?
poormanscron problem?
I did turn off the statistics module for now.
but you know, I'm looking at the system events listing, and I wonder if the problem is with poormanscron? I see lists like this:
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
30 Aug 2005 - 22:09 user error: Duplicate entry 'archive:calendar:30-8-2005' for key
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 user error: Duplicate entry 'archive:calendar:30-8-2005' for key
30 Aug 2005 - 22:09 feed: updated projectjulie.
30 Aug 2005 - 22:09 feed: updated projectjulie.
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 feed: updated projectjulie.
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
30 Aug 2005 - 22:09 feed: updated projectjulie.
30 Aug 2005 - 22:09 cron run completed (via poormanscron)
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
30 Aug 2005 - 22:09 user error: Duplicate entry 'poormanscron_lastrun' for key 1 que
why would poormanscron be running multiple times per minute? I turned it off, and that seems to have stopped the immediate flood of system events which might have been taxing the server. I'm going to run it manually for a while, or try to set it up server-side.
thanks for replying!