1 john Mar 12, 2006 08:48
3 john Mar 13, 2006 02:22
I think this may be a widespread problem.
I'm not sure about this, it may indicate something that is less than robust however this whole problem ( for me ) was the result of a site on the server running a rogue script. They were able to fix most of the issues but in the whole process evo_hitlog somehow got corrupted.
One thing I do know is that if your going to have server related problems, don't have them on a weekend :)
They are going to try another repair when their MYSQL guru comes on tomorrow.
I have to say that I have had no B2Evo MYSQL issues for years that couldn't be fixed by running "repair tables" and this one was a real surprise.
I will attempt to get a full explanation when ( if) it gets resolved :)
4 daethian2 Mar 13, 2006 21:05
Mine seems to have fixed itself while I was sleeping. Now explain that! LOL weird
5 john Mar 13, 2006 23:44
Well, my host worked on the corrupted hitlog table last night and fixed it without losing any data.
Thank goodness for a host that cares !!
Man that evo_hitlog table is big !!!
I think this may be a widespread problem.
Today my forum AND my blogs developed errors similiar to yours.
My linkblog section on my blog says:
My forum has
I'm no tech whiz my any means but this is different software and different people now with the same errors so it has to by MySQL right?