110506 19:53:17 InnoDB: Assertion failure in thread 139916493055744 in file /export/home/pb2/build/sb_0-2859905-1295553452.13/mysql-5.5.9/storage/innobase/row/row0sel.c line 4465 InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOMMITTED 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 110506 19:53:17 - mysqld got signal 6 ; 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=33554432 read_buffer_size=1048576 max_used_connections=6 max_threads=151 thread_count=6 connection_count=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343735 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f40b02fbd20 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... stack_bottom = 0x7f40d8ddde50 thread_stack 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x794a09] /usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fcc60] /lib/libpthread.so.0(+0xf8f0)[0x7f40d8b048f0] /lib/libc.so.6(gsignal+0x35)[0x7f40d7edda75] /lib/libc.so.6(abort+0x180)[0x7f40d7ee15c0] /usr/local/mysql/bin/mysqld[0x7cedc7] /usr/local/mysql/bin/mysqld[0x7aaacc] /usr/local/mysql/bin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1d)[0x733e0d] /usr/local/mysql/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x79)[0x597e19] /usr/local/mysql/bin/mysqld[0x59d62d] /usr/local/mysql/bin/mysqld(_ZN4JOIN4execEv+0x915)[0x5b1055] /usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1c3)[0x5acdb3] /usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x179)[0x5b2b09] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3d31)[0x578141] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x15a)[0x578aaa] /usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1341)[0x57a641] /usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x337)[0x60dc37] /usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x60dca4] /lib/libpthread.so.0(+0x69ca)[0x7f40d8afb9ca] /lib/libc.so.6(clone+0x6d)[0x7f40d7f9070d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f40b0226fd0): is an invalid pointer Connection ID (thread ID): 676 Status: 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. 110506 19:53:17 mysqld_safe Number of processes running now: 0 110506 19:53:17 mysqld_safe mysqld restarted 110506 19:53:17 [Note] Plugin 'FEDERATED' is disabled. 110506 19:53:17 InnoDB: The InnoDB memory heap is disabled 110506 19:53:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110506 19:53:17 InnoDB: Compressed tables use zlib 1.2.3 110506 19:53:17 InnoDB: Using Linux native AIO 110506 19:53:17 InnoDB: Initializing buffer pool, size = 384.0M 110506 19:53:17 InnoDB: Completed initialization of buffer pool 110506 19:53:17 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 806451373263 110506 19:53:17 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 806456615936 InnoDB: Doing recovery: scanned up to log sequence number 806461858816 InnoDB: Doing recovery: scanned up to log sequence number 806467101696 InnoDB: Doing recovery: scanned up to log sequence number 806472344576 InnoDB: Doing recovery: scanned up to log sequence number 806477587456 InnoDB: Doing recovery: scanned up to log sequence number 806482830336 InnoDB: Doing recovery: scanned up to log sequence number 806488073216 InnoDB: Doing recovery: scanned up to log sequence number 806493316096 InnoDB: Doing recovery: scanned up to log sequence number 806498558976 InnoDB: Doing recovery: scanned up to log sequence number 806503801856 InnoDB: Doing recovery: scanned up to log sequence number 806509044736 InnoDB: Doing recovery: scanned up to log sequence number 806514287616 InnoDB: Doing recovery: scanned up to log sequence number 806519530496 InnoDB: Doing recovery: scanned up to log sequence number 806524773376 InnoDB: Doing recovery: scanned up to log sequence number 806530016256 InnoDB: Doing recovery: scanned up to log sequence number 806535259136 InnoDB: Doing recovery: scanned up to log sequence number 806540502016 InnoDB: Doing recovery: scanned up to log sequence number 806545082223 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 7159 row operations to undo InnoDB: Trx id counter is EAA2200 110506 19:53:18 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 4028083, file name ./mysql-bin.000542 InnoDB: Starting in background the rollback of uncommitted transactions 110506 19:53:25 InnoDB: Rolling back trx with id EAA2057, 7159 rows to undo InnoDB: Progress in percents: 1110506 19:53:25 InnoDB: Waiting for the background threads to start 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 InnoDB: Rolling back of trx id EAA2057 completed 110506 19:53:26 InnoDB: Rollback of non-prepared transactions completed 110506 19:53:26 InnoDB: 1.1.5 started; log sequence number 806545082223 110506 19:53:26 [Note] Recovering after a crash using mysql-bin 110506 19:53:26 [Note] Starting crash recovery... 110506 19:53:26 [Note] Crash recovery finished. 110506 19:53:26 [Note] Event Scheduler: Loaded 0 events 110506 19:53:26 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.9-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) 110506 19:54:40 [Note] /usr/local/mysql/bin/mysqld: Normal shutdown 110506 19:54:40 [Note] Event Scheduler: Purging the queue. 0 events 110506 19:54:40 InnoDB: Starting shutdown... 110506 19:55:01 InnoDB: Shutdown completed; log sequence number 806549761441 110506 19:55:01 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete 110506 19:55:01 mysqld_safe mysqld from pid file /usr/local/mysql/data/gw9.pid ended 110506 19:57:06 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 110506 19:57:06 [Note] Plugin 'FEDERATED' is disabled. 110506 19:57:06 InnoDB: The InnoDB memory heap is disabled 110506 19:57:06 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110506 19:57:06 InnoDB: Compressed tables use zlib 1.2.3 110506 19:57:06 InnoDB: Using Linux native AIO 110506 19:57:06 InnoDB: Initializing buffer pool, size = 384.0M 110506 19:57:06 InnoDB: Completed initialization of buffer pool 110506 19:57:06 InnoDB: highest supported file format is Barracuda. 110506 19:57:06 InnoDB: Waiting for the background threads to start 110506 19:57:07 InnoDB: 1.1.5 started; log sequence number 806549761441 110506 19:57:08 [Note] Event Scheduler: Loaded 0 events 110506 19:57:08 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.9-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) 110506 20:01:02 InnoDB: Assertion failure in thread 140048400721664 in file /export/home/pb2/build/sb_0-2859905-1295553452.13/mysql-5.5.9/storage/innobase/row/row0sel.c line 4465 InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOMMITTED 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 110506 20:01:02 - mysqld got signal 6 ; 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=33554432 read_buffer_size=1048576 max_used_connections=3 max_threads=151 thread_count=1 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343735 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x218ad90 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... stack_bottom = 0x7f5f8f2d1e50 thread_stack 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x794a09] /usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fcc60] /lib/libpthread.so.0(+0xf8f0)[0x7f5fb6c9d8f0] /lib/libc.so.6(gsignal+0x35)[0x7f5fb6076a75] /lib/libc.so.6(abort+0x180)[0x7f5fb607a5c0] /usr/local/mysql/bin/mysqld[0x7cedc7] /usr/local/mysql/bin/mysqld[0x7aaacc] /usr/local/mysql/bin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1d)[0x733e0d] /usr/local/mysql/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x79)[0x597e19] /usr/local/mysql/bin/mysqld[0x59d62d] /usr/local/mysql/bin/mysqld(_ZN4JOIN4execEv+0x915)[0x5b1055] /usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1c3)[0x5acdb3] /usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x179)[0x5b2b09] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3d31)[0x578141] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x15a)[0x578aaa] /usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1341)[0x57a641] /usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x337)[0x60dc37] /usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x60dca4] /lib/libpthread.so.0(+0x69ca)[0x7f5fb6c949ca] /lib/libc.so.6(clone+0x6d)[0x7f5fb612970d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x22140f0): INSERT INTO `af`.`gc_user_data2` (`user_id`, `fb_user_id`, `third_party_id`, `gauth`, `deleted`, `firstname`, `lastname`, `nick`, `rank_name`, `rank_image`, `sex`, `image`, `image_gauth`, `refer_user`, `country`, `class`, `farm_level`, `time_premium_expired`, `status`, `time_ban_expired`, `ban_reason`, `money`, `point`, `point_all`, `wood`, `training`, `fame`, `fame_lv`, `turn`, `turn_max`, `turn_regen`, `bonus`, `char_main_id`, `char_id`, `boost`, `time_boost_expired`, `time_register`, `time_lastlogin`, `time_lastaccess`, `playedtime_all`, `playedtime_today`, `session_id`, `session_expired`, `item`, `guild_id`, `active_key`, `bot_count`, `bot_key`, `decor_storage`, `data_serialized`, `emoticon_unlock`, `comment_theme_unlock`, `party_exp`, `party_lv`, `party_data`, `travel_serialized`, `timezone`, `email`, `time_last_profile_update`, `locale`, `image_big`, `birthday`, `others`, `last_facebook_session`, `greeting_text`, `friend_count`, `friend_invite_all`, `friend_invite_week`, `quest`, `collection`, `item2`, Connection ID (thread ID): 95 Status: 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. 110506 20:01:02 mysqld_safe Number of processes running now: 0 110506 20:01:02 mysqld_safe mysqld restarted 110506 20:01:02 [Note] Plugin 'FEDERATED' is disabled. 110506 20:01:02 InnoDB: The InnoDB memory heap is disabled 110506 20:01:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110506 20:01:02 InnoDB: Compressed tables use zlib 1.2.3 110506 20:01:02 InnoDB: Using Linux native AIO 110506 20:01:02 InnoDB: Initializing buffer pool, size = 384.0M 110506 20:01:02 InnoDB: Completed initialization of buffer pool 110506 20:01:02 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 806599285296 110506 20:01:02 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 806604528128 InnoDB: Doing recovery: scanned up to log sequence number 806609771008 InnoDB: Doing recovery: scanned up to log sequence number 806615013888 InnoDB: Doing recovery: scanned up to log sequence number 806620256768 InnoDB: Doing recovery: scanned up to log sequence number 806625499648 InnoDB: Doing recovery: scanned up to log sequence number 806630742528 InnoDB: Doing recovery: scanned up to log sequence number 806635985408 InnoDB: Doing recovery: scanned up to log sequence number 806641228288 InnoDB: Doing recovery: scanned up to log sequence number 806646471168 InnoDB: Doing recovery: scanned up to log sequence number 806651714048 InnoDB: Doing recovery: scanned up to log sequence number 806656956928 InnoDB: Doing recovery: scanned up to log sequence number 806662199808 InnoDB: Doing recovery: scanned up to log sequence number 806667442688 InnoDB: Doing recovery: scanned up to log sequence number 806672685568 InnoDB: Doing recovery: scanned up to log sequence number 806677928448 InnoDB: Doing recovery: scanned up to log sequence number 806683171328 InnoDB: Doing recovery: scanned up to log sequence number 806688414208 InnoDB: Doing recovery: scanned up to log sequence number 806693657088 InnoDB: Doing recovery: scanned up to log sequence number 806695242578 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 7063 row operations to undo InnoDB: Trx id counter is EAA2700 110506 20:01:03 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 613532, file name ./mysql-bin.000544 InnoDB: Starting in background the rollback of uncommitted transactions 110506 20:01:09 InnoDB: Rolling back trx with id EAA2535, 7063 rows to undo InnoDB: Progress in percents: 1110506 20:01:09 InnoDB: Waiting for the background threads to start 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 InnoDB: Rolling back of trx id EAA2535 completed 110506 20:01:10 InnoDB: Rollback of non-prepared transactions completed 110506 20:01:10 InnoDB: 1.1.5 started; log sequence number 806695242578 110506 20:01:10 [Note] Recovering after a crash using mysql-bin 110506 20:01:10 [Note] Starting crash recovery... 110506 20:01:10 [Note] Crash recovery finished. 110506 20:01:10 [Note] Event Scheduler: Loaded 0 events 110506 20:01:10 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.9-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) 110506 20:17:48 InnoDB: Assertion failure in thread 140710695442176 in file /export/home/pb2/build/sb_0-2859905-1295553452.13/mysql-5.5.9/storage/innobase/row/row0sel.c line 4465 InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOMMITTED 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 110506 20:17:48 - mysqld got signal 6 ; 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=33554432 read_buffer_size=1048576 max_used_connections=5 max_threads=151 thread_count=2 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343735 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x3e80d50 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... stack_bottom = 0x7ff9c3048e50 thread_stack 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x794a09] /usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fcc60] /lib/libpthread.so.0(+0xf8f0)[0x7ff9c2c6b8f0] /lib/libc.so.6(gsignal+0x35)[0x7ff9c2044a75] /lib/libc.so.6(abort+0x180)[0x7ff9c20485c0] /usr/local/mysql/bin/mysqld[0x7cedc7] /usr/local/mysql/bin/mysqld[0x7aaacc] /usr/local/mysql/bin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1d)[0x733e0d] /usr/local/mysql/bin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x943)[0x5e2313] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x16ca)[0x575ada] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x15a)[0x578aaa] /usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1341)[0x57a641] /usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x337)[0x60dc37] /usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x60dca4] /lib/libpthread.so.0(+0x69ca)[0x7ff9c2c629ca] /lib/libc.so.6(clone+0x6d)[0x7ff9c20f770d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x4066d40): UPDATE `gc_user_data` SET image_gauth = 'member' Connection ID (thread ID): 193 Status: 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. 110506 20:17:49 mysqld_safe Number of processes running now: 0 110506 20:17:49 mysqld_safe mysqld restarted 110506 20:17:49 [Note] Plugin 'FEDERATED' is disabled. 110506 20:17:49 InnoDB: The InnoDB memory heap is disabled 110506 20:17:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110506 20:17:49 InnoDB: Compressed tables use zlib 1.2.3 110506 20:17:49 InnoDB: Using Linux native AIO 110506 20:17:49 InnoDB: Initializing buffer pool, size = 384.0M 110506 20:17:49 InnoDB: Completed initialization of buffer pool 110506 20:17:49 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 806700828929 110506 20:17:49 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 806706071552 InnoDB: Doing recovery: scanned up to log sequence number 806711314432 InnoDB: Doing recovery: scanned up to log sequence number 806716557312 InnoDB: Doing recovery: scanned up to log sequence number 806721800192 InnoDB: Doing recovery: scanned up to log sequence number 806727043072 InnoDB: Doing recovery: scanned up to log sequence number 806732285952 InnoDB: Doing recovery: scanned up to log sequence number 806737528832 InnoDB: Doing recovery: scanned up to log sequence number 806742771712 InnoDB: Doing recovery: scanned up to log sequence number 806747501580 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 6867 row operations to undo InnoDB: Trx id counter is EAA2B00 110506 20:17:49 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 1237258, file name ./mysql-bin.000545 InnoDB: Starting in background the rollback of uncommitted transactions 110506 20:17:50 InnoDB: Rolling back trx with id EAA2918, 6867 rows to undo InnoDB: Progress in percents: 1110506 20:17:50 InnoDB: Waiting for the background threads to start 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85110506 20:17:51 InnoDB: 1.1.5 started; log sequence number 806747501580 110506 20:17:51 [Note] Recovering after a crash using mysql-bin 110506 20:17:51 [Note] Starting crash recovery... 110506 20:17:51 [Note] Crash recovery finished. 86 87 88 89110506 20:17:51 [Note] Event Scheduler: Loaded 0 events 110506 20:17:51 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.9-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) 90 91 92 93 94 95 96 97 98 99 100 InnoDB: Rolling back of trx id EAA2918 completed 110506 20:17:51 InnoDB: Rollback of non-prepared transactions completed 110506 20:18:10 InnoDB: Assertion failure in thread 140690106472192 in file /export/home/pb2/build/sb_0-2859905-1295553452.13/mysql-5.5.9/storage/innobase/row/row0sel.c line 4465 InnoDB: Failing assertion: trx->isolation_level == TRX_ISO_READ_UNCOMMITTED 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.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 110506 20:18:10 - mysqld got signal 6 ; 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=33554432 read_buffer_size=1048576 max_used_connections=2 max_threads=151 thread_count=2 connection_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343735 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x28722a0 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... stack_bottom = 0x7ff4f7d1ce50 thread_stack 0x40000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x39)[0x794a09] /usr/local/mysql/bin/mysqld(handle_segfault+0x380)[0x4fcc60] /lib/libpthread.so.0(+0xf8f0)[0x7ff4f793f8f0] /lib/libc.so.6(gsignal+0x35)[0x7ff4f6d18a75] /lib/libc.so.6(abort+0x180)[0x7ff4f6d1c5c0] /usr/local/mysql/bin/mysqld[0x7cedc7] /usr/local/mysql/bin/mysqld[0x7aaacc] /usr/local/mysql/bin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1d)[0x733e0d] /usr/local/mysql/bin/mysqld(_Z12mysql_updateP3THDP10TABLE_LISTR4ListI4ItemES6_PS4_jP8st_ordery15enum_duplicatesbPySB_+0x943)[0x5e2313] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x16ca)[0x575ada] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x15a)[0x578aaa] /usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1341)[0x57a641] /usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x337)[0x60dc37] /usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x60dca4] /lib/libpthread.so.0(+0x69ca)[0x7ff4f79369ca] /lib/libc.so.6(clone+0x6d)[0x7ff4f6dcb70d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x28fb570): UPDATE `gc_user_data` SET image_gauth = 'member' Connection ID (thread ID): 6 Status: 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. 110506 20:18:10 mysqld_safe Number of processes running now: 0 110506 20:18:10 mysqld_safe mysqld restarted 110506 20:18:10 [Note] Plugin 'FEDERATED' is disabled. 110506 20:18:10 InnoDB: The InnoDB memory heap is disabled 110506 20:18:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins 110506 20:18:10 InnoDB: Compressed tables use zlib 1.2.3 110506 20:18:10 InnoDB: Using Linux native AIO 110506 20:18:10 InnoDB: Initializing buffer pool, size = 384.0M 110506 20:18:10 InnoDB: Completed initialization of buffer pool 110506 20:18:10 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 806709540318 110506 20:18:10 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 806714782720 InnoDB: Doing recovery: scanned up to log sequence number 806720025600 InnoDB: Doing recovery: scanned up to log sequence number 806725268480 InnoDB: Doing recovery: scanned up to log sequence number 806730511360 InnoDB: Doing recovery: scanned up to log sequence number 806735754240 InnoDB: Doing recovery: scanned up to log sequence number 806740997120 InnoDB: Doing recovery: scanned up to log sequence number 806746240000 InnoDB: Doing recovery: scanned up to log sequence number 806751482880 InnoDB: Doing recovery: scanned up to log sequence number 806756725760 InnoDB: Doing recovery: scanned up to log sequence number 806761968640 InnoDB: Doing recovery: scanned up to log sequence number 806767211520 InnoDB: Doing recovery: scanned up to log sequence number 806772454400 InnoDB: Doing recovery: scanned up to log sequence number 806777697280 InnoDB: Doing recovery: scanned up to log sequence number 806782940160 InnoDB: Doing recovery: scanned up to log sequence number 806788183040 InnoDB: Doing recovery: scanned up to log sequence number 806793425920 InnoDB: Doing recovery: scanned up to log sequence number 806798668800 InnoDB: Doing recovery: scanned up to log sequence number 806803911680 InnoDB: Doing recovery: scanned up to log sequence number 806809154560 InnoDB: Doing recovery: scanned up to log sequence number 806814397440 InnoDB: Doing recovery: scanned up to log sequence number 806819640320 InnoDB: Doing recovery: scanned up to log sequence number 806824883200 InnoDB: Doing recovery: scanned up to log sequence number 806830126080 InnoDB: Doing recovery: scanned up to log sequence number 806835368960 InnoDB: Doing recovery: scanned up to log sequence number 806837526327 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 6894 row operations to undo InnoDB: Trx id counter is EAA2D00 110506 20:18:12 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Last MySQL binlog file position 0 102162, file name ./mysql-bin.000546 InnoDB: Starting in background the rollback of uncommitted transactions 110506 20:18:12 InnoDB: Rolling back trx with id EAA2B22, 6894 rows to undo InnoDB: Progress in percents: 1110506 20:18:12 InnoDB: Waiting for the background threads to start 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47110506 20:18:13 InnoDB: 1.1.5 started; log sequence number 806837526327 110506 20:18:13 [Note] Recovering after a crash using mysql-bin 110506 20:18:13 [Note] Starting crash recovery... 110506 20:18:13 [Note] Crash recovery finished. 48 49 50 51 52 53 54 55 56110506 20:18:13 [Note] Event Scheduler: Loaded 0 events 110506 20:18:13 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.9-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL) 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 InnoDB: Rolling back of trx id EAA2B22 completed 110506 20:18:19 InnoDB: Rollback of non-prepared transactions completed