Red Hat Bugzilla – Bug 139766
MySQL tells 'Got error 123 when reading table'
Last modified: 2013-07-02 23:03:06 EDT
Description of problem:
I get more and more the error
041117 22:48:34 [ERROR] Got error 123 when reading table './db/bb1_sessions'
in /var/log/mysqld.log and this error is related with MySQL >= 4.x.
Using MySQL 3.x, I can't reproduce this problem. There are a few
users I found with Google having the same problem, but there is no
real solution, except some stupid answers (like upgrading to latest
official MySQL etc).
Version-Release number of selected component (if applicable):
Sometimes and hard.
Steps to Reproduce:
a) Run for example WoltLab Burning Board >= 2.0.x
Errors in MySQL log and errors running the WoltLab Burning Board for
Maybe the problem is related with the table bb1_sessions. The table
has the format "ENGINE=HEAP" and some unsigned int(11) fields, some
of these unsigned int(11) fields are KEYs. I dunno, maybe it's
related, but the problem came up with MySQL 4.x. If you think, the
problem is a Woltlab Burning Board bug, I've got to disappoint you,
it doesn't seem so.
If you think the problem is related with the table and if you want
to have a MySQL dump etc, this bug report has to be marked
confidential, because WBB isn't open source software :-(
Oh I forgot to say, the browser tells me about the WBB software:
mysql error: Record has changed since last read in table 'bb1_sessions'
mysql error number: 1020
And the table contains sessions, but the box has a very low load and
the sessions table isn't accessed very often - so this also shouldn't
be a problem...but both error codes are confusing me totally.
Okay, my reported problem is upstream bug #6748 ("Record has changed
since last read in table ... error on HEAP table"), more information:
This bug will be fixed in 4.1.8, but maybe we can get a backported
patch, because it's a serious problem?!
would fix this bug report.
I looked at the MySQL change history:
and notice that there are quite a number of bug fixes pending for
4.1.8, several of which seem more serious than this one. Also it
looks like 4.1.8 release is just around the corner. So I'm inclined
to just wait rather than go to the trouble of patching this single
bug. I'll try to push out 4.1.8 as soon as it's available.
Okay Tom, MySQL 4.1.8 is now released... :)
I've pushed out MySQL 4.1.9 in the devel branch. Sorry about the delay.