MySQL Bugs: #21927: mysqld crash

Bug #21927	mysqld crash
Submitted:	30 Aug 2006 17:17	Modified:	1 Oct 2006 6:17
Reporter:	Daniele Gallina	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.24	OS:	Linux (CentOS 4.3)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
Loading images in Coppermine Photo Gallery, often MySql crash with this 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=8388600
read_buffer_size=131072
max_used_connections=6
max_connections=100
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8b8e6d8
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=0xb5715288, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817b1b0
0xb7f8d0b7
0x81cdbee
0x81d4ad1
0x81daa69
0x81db132
0x8191987
0x819825f
0x819904c
0x81999cc
0x819a3aa
0xb7f86ce1
0xb7eb2ffa
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 0x8b99b60 = SELECT title, data
FROM datastore
WHERE title IN ('','options','bitfields','forumcache','usergroupcache','stylecache','languagecache','products','pluginlist','cron','smiliecache','bbcodecache','mailqueue','hidprofilecache')
thd->thread_id=99
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
060830 19:10:30 mysqld restarted
060830 19:10:30 InnoDB: Started; log sequence number 0 43655
060830 19:10:30 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.24-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Edition - Standard (GPL)

How to repeat:
Load images in Coppermine Photo Gallery

Thank you for the report.

Could you please provide output of SHOW CREATE TABLE datastore; and SHOW TABLE STATUS LIKE 'datastore'; statements?

The table don't exist. I think it is a temporary table?

mysql> use i-networks;
Database changed
mysql> SHOW CREATE TABLE datastore;
ERROR 1146 (42S02): Table 'i-networks.datastore' doesn't exist
mysql> show tables
    -> ;
+----------------------+
| Tables_in_i-networks |
+----------------------+
| foto_albums          |
| foto_banned          |
| foto_bridge          |
| foto_categories      |
| foto_comments        |
| foto_config          |
| foto_dict            |
| foto_ecards          |
| foto_exif            |
| foto_favpics         |
| foto_filetypes       |
| foto_hit_stats       |
| foto_pictures        |
| foto_plugins         |
| foto_sessions        |
| foto_temp_data       |
| foto_usergroups      |
| foto_users           |
| foto_vote_stats      |
| foto_votes           |
+----------------------+
20 rows in set (0.05 sec)

mysql>

We have similar bug #21582 already fixed in 5.0.24a released today. Could you please try to repeat the problem with MySQL 5.0.24a? You can download it here: http://dev.mysql.com/downloads/mysql/5.0.html

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".