- b2evolution CMS Support Forums
- b2evolution Support
- General Support
- [1.9.x] MySQL Error 127 in stats
1 quard Apr 07, 2007 09:24
My b2evolution Version: 1.9.x
I have been having tons of problems with evo_stats lately spitting out SQL error 127's all over the place. These errors display in my main page sometimes,, or any time I'm in an admin page. I've repaired the SQL database a dozen times but the errors keep a'coming. I even emptied the table too which made everything ok for a short while but now they're back again. If anyone can help please let me know what you think. The following is some of the messages as well as what the repair said when it fixed the problem (temporarily):
An unexpected error has occured!
If this error persits, please report it to the administrator.
Go back to home page
Additional information about this error:
MySQL error!
Got error 127 from storage engine(Errno=1030)
Your query:
SELECT COUNT(*) AS totalHits, hit_referer, dom_name
FROM evo_hitlog
INNER JOIN evo_useragents ON hit_agnt_ID = agnt_ID
LEFT JOIN evo_basedomains ON dom_ID = hit_referer_dom_ID
WHERE hit_referer_type IN ('search')
AND agnt_type = "browser"
AND hit_blog_ID = '5'
GROUP BY dom_name
ORDER BY totalHits DESC
LIMIT 20
-----
MySQL error!
Got error 127 from storage engine(Errno=1030)
Your query:
SELECT COUNT(*) AS totalHits, hit_referer, dom_name
FROM evo_hitlog
INNER JOIN evo_useragents ON hit_agnt_ID = agnt_ID
LEFT JOIN evo_basedomains ON dom_ID = hit_referer_dom_ID
WHERE hit_referer_type IN ('referer')
AND agnt_type = "browser"
AND hit_blog_ID = '5'
GROUP BY dom_name
ORDER BY totalHits DESC
LIMIT 30
------
This is what the repair said below:
vincent_b2evolution.evo_hitlog
info : Wrong bytesec: 0- 0- 0 at 80832; Skipped
info : Wrong bytesec: 0- 0- 0 at 85592; Skipped
info : Wrong bytesec: 0- 0- 0 at 87520; Skipped
warning : Number of rows changed from 1212 to 1209
status : OK
The server is running php5 and I'm running b2 1.9.2
Every day or so I get some table in the evo_stats database SQL error 127ing. Usually a different one. If anyone knows a way to re-initialize everything at once to fix this problem, please let me know