Форум пользователей MySQL

При работе, иногда (при пока не выясненных обстоятельствах), сервис падает с таким логом:

100420 17:03:56  InnoDB: Assertion failure in thread 3548 in file .\row\row0mysql.c line 1534
InnoDB: Failing assertion: index->type & DICT_CLUSTERED
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/ … overy.html
InnoDB: about forcing recovery.
100420 17:03:56 - mysqld got exception 0xc0000005 ;
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=135266304
read_buffer_size=65536
max_used_connections=32
max_threads=40
threads_connected=13
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 145148 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x20fba538
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...
InnoDB: Thread 4332 stopped in file .\os\os0sync.c line 271
InnoDB: Thread 5900 stopped in file .\sync\sync0arr.c line 337
InnoDB: Thread 2436 stopped in file .\os\os0sync.c line 574
006B5906    mysqld.exe!row_unlock_for_mysql()[row0mysql.c:1534]
006BDB18    mysqld.exe!row_search_for_mysql()[row0sel.c:4090]
006AA670    mysqld.exe!ha_innobase::index_read()[ha_innodb.cc:4412]
0043AB39    mysqld.exe!handler::index_read_map()[handler.h:1390]
00447D56    mysqld.exe!handler::read_range_first()[handler.cc:4176]
00445E6C    mysqld.exe!handler::read_multi_range_first()[handler.cc:4050]
004D7A4B    mysqld.exe!QUICK_RANGE_SELECT::get_next()[opt_range.cc:8468]
004E9261    mysqld.exe!rr_quick()[records.cc:313]
0053C74D    mysqld.exe!mysql_delete()[sql_delete.cc:289]
00556878    mysqld.exe!mysql_execute_command()[sql_parse.cc:3273]
0050213D    mysqld.exe!sp_instr_stmt::exec_core()[sp_head.cc:2907]
00504D4A    mysqld.exe!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:2734]
00504F09    mysqld.exe!sp_instr_stmt::execute()[sp_head.cc:2850]
00506360    mysqld.exe!sp_head::execute()[sp_head.cc:1253]
005074A8    mysqld.exe!sp_head::execute_procedure()[sp_head.cc:1982]
005584A1    mysqld.exe!mysql_execute_command()[sql_parse.cc:4355]
0050213D    mysqld.exe!sp_instr_stmt::exec_core()[sp_head.cc:2907]
00504D4A    mysqld.exe!sp_lex_keeper::reset_lex_and_exec_core()[sp_head.cc:2734]
00504F09    mysqld.exe!sp_instr_stmt::execute()[sp_head.cc:2850]
00506360    mysqld.exe!sp_head::execute()[sp_head.cc:1253]
005074A8    mysqld.exe!sp_head::execute_procedure()[sp_head.cc:1982]
005584A1    mysqld.exe!mysql_execute_command()[sql_parse.cc:4355]
0055A8C3    mysqld.exe!mysql_parse()[sql_parse.cc:5933]
0055B3B3    mysqld.exe!dispatch_command()[sql_parse.cc:1218]
0055C1B7    mysqld.exe!do_command()[sql_parse.cc:861]
005DF511    mysqld.exe!handle_one_connection()[sql_connect.cc:1115]
0064588B    mysqld.exe!pthread_start()[my_winthread.c:85]
0072ADD3    mysqld.exe!_callthreadstart()[thread.c:293]
FCB0E900   
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 21382188=DELETE
    FROM
      location_spawn_mob
    WHERE
      Location_Id =  NAME_CONST('p_LocId',1073746827)
thd->thread_id=5720
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
InnoDB: Log scan progressed past the checkpoint lsn 0 379482287

В коде используются хранимые процедуры с вызовом в них других процедур. Используются транзакции, т.е.
1) connect
2) set AutoCommit=0
3) выполняется хранимая процедура
4) выполняется ряд DML операций (удаление, вставка записей)
5) выполняется хранимая процедура
5.1) вызывается другая хранимая процедура (тут иногда падает)
6) commit

Используется С++Connect 1.0.5. Язык С++ Windows.
Сервер:  5.1.33 windows

Спасибо.

Отредактированно QuaziKing (20.04.2010 19:10:23)