Description:
Made an update from 4.1.11 to 4.1.12 (using rpms). Since then I always get an error message "Connection was lost during query" when I try to connect from any of the (Windows) clients. Working on the servers console works, it's just when connection over network.
The mysql log file shows this:
050518 11:11:03 [Warning] Asked for 196608 thread stack, but got 126976
050518 11:11:03 InnoDB: Started; log sequence number 0 43634
/usr/sbin/mysqld: ready for connections.
Version: '4.1.12-standard' socket: '/var/lib/mysql/mysql.sock' port:
3306 MySQL Community Edition - Standard (GPL)
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=16777216
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 =
80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x8930b00
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=0xbfe7eaf8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808df77
0x82e8af8
0x808bd1e
0x80b3fe1
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...
[...]
Number of processes running now: 0
050518 11:11:04 mysqld restarted
How to repeat:
How to stop????
