avansant:
We recently had our mySQL grind to just about a halt ... we've had yahoo bots go bezerk and spider too vigorously, but that wasn't it this time. Once we had a bot continuously add things to it's cart somehow... but that wasn't it this time...
FINALLY we found it was an old installation of user tracking mod. (I emphasize old in case this issue has been solved). A bot was crawling through the database listings for that mod, which had gotten 1 GB large. The constant queries killed us.
I just removed the mod and the table from mySQL since we hadn't been using it really anymore anyway.
Appreciate the alert. And glad you have your issue resolved.
But I am curious how the mod was determined be related to your issue. All the tracking logging done by the mod is written to a database table. How can the database be spidered?
It is possible your shop URL containing a zenid was published somewhere on the web, contributed to the issue.
That can cause sessions to be hijacked.
Not that it would be related but are you writing your sql_cache to a file or the database?
You might want to search the forum on "db_cache". There was a related bug fix patch posted in July.
And note spider logging can be disabled in User Tracking (this is highly recommended).
There are flaws in latest versions of User Tracking, but as far as I understand nothing which would have contributed to your scenario. To be sure I'm no expert on these matters and just interested in how it was deduced that User Tracking was the culprit (besides just removing the mod and then all was better)?
Woody