MySQL Bugs: #10671: During/after 4.1.12 upgrade, all updates segfault or give read-only errors

Bug #10671	During/after 4.1.12 upgrade, all updates segfault or give read-only errors
Submitted:	16 May 2005 14:58	Modified:	5 Jun 2005 14:47
Reporter:	Paul Roub	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: MyISAM storage engine	Severity:	S1 (Critical)
Version:	4.1.12	OS:	Linux (RedHat 9)
Assigned to:	Matthew Lord	CPU Architecture:	Any

Description:
Upgraded to 4.1.12 (from 4.1.11) this morning, using Linux x86 RPMs - saw a failure updating the help tables - out of memory error, I believe.

Since then, all updates fail.  All files check out OK w/myisamchk, permissions/accounts are as before.

Will attach binary logs, stack trace, etc.  I'm out of ideas, and this is killing us.

How to repeat:
Execute any update or insert, against any of our databases.

Stack trace on error:

mysqld got signal 11;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=65536
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217663 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x894ec00
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0xbfe7ea88, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808df77
0x82e8af8
0x8561749
0x8084834
0x80b4c0e
0x80a2c14
0x809d0f2
0x809cab4
0x809c167
0x82e62ac
0x830fc3a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8955110 = delete from whos_online where time_last_click < '1116253109'
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
050516 10:33:29 mysqld restarted
050516 10:33:29 [Warning] Asked for 196608 thread stack, but got 126976
InnoDB: Warning: we did not need to do crash recovery, but log scan
InnoDB: progressed past the checkpoint lsn 0 43824 up to lsn 0 43854
050516 10:33:29 InnoDB: Started; log sequence number 0 43824

sample table on which any update fails

Attachment: nighttable.zip (application/x-zip-compressed, text), 153.93 KiB.

binary logs - seem empty

Attachment: ib_logfile.zip (application/x-zip-compressed, text), 34.29 KiB.

Not sure if I'm following the binary log procedure properly -- none of the logs seems (attached) seems to show the updates going on.  An example command triggering the problem is: "update night set active=0 where id=241"

FYI - forcing rpm downgrade to 4.1.11 clears up the problem.  Any files, data, etc. I can provide to test why the upgrade fails, please let me know.

Hi Paul,

Thank you for your bug report!

We had a problem with bad RPMs when 4.1.12 was first released.  From
your description it sounds like you got the bad ones.  When you are
next able can you please download the RPMs from our site again and
try the upgrade?  I apologize for the inconvenience but you should no
longer experience this problem.

Best Regards

That solved the problem.  4.1.12 is installed and running now.  Thanks!