1 joachim Feb 08, 2007 19:55
3 quard Apr 15, 2007 07:25
Since 1.8.x to 1.9.x I believe there is a known problem with how it handles the evo_stats tables. If you do a search there are a lot of people with different MYSQL errors in various evo_stats tables. The current advice, not a solution is to CONSTANTLY repair the tables when these often errors appear. I myself have posted about this problem prior but no fixes appear or suggestions to fix.
If you are using Cpanel, the temp fix is to click on CHECK the SQL file that b2 is using, then REPAIR.
I keep doing this, even emptying the affected table to have the problem re-appear every 3 days. No solution yet has been suggested, unfortunately.
I just had the MYSQL evo_stats bug appear yet again after my last repair a few days ago. My best guess with no help so far is that the way b2 writes the data to evo_stats it's putting writing incorrectly, which will just keep happening when whatever is causing it repeats itself on your blog.
My latest one was:
Additional information about this error:
MySQL error!
Got error 127 from storage engine(Errno=1030)
Your query: Get hit summary
SELECT COUNT(*) AS hits, agnt_type, YEAR(hit_datetime) AS year,
MONTH(hit_datetime) AS month, DAYOFMONTH(hit_datetime) AS day
FROM evo_hitlog INNER JOIN evo_useragents ON hit_agnt_ID = agnt_ID
WHERE hit_blog_ID = 5
GROUP BY year, month, day, agnt_type
ORDER BY year DESC, month DESC, day DESC, agnt_type
This ist the error from mysql:
Please help me :'(