May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:10:51 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:10:51 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:10:51 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:10:51 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:10:51 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: Assertion failure in thread 140405174830848 in file ../../../storage/innobase/handler/ha_innodb.cc line 8085
May 25 17:10:51 ns29670 mysqld: InnoDB: Failing assertion: auto_inc > 0
May 25 17:10:51 ns29670 mysqld: InnoDB: We intentionally generate a memory trap.
May 25 17:10:51 ns29670 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 25 17:10:51 ns29670 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 25 17:10:51 ns29670 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 25 17:10:51 ns29670 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 25 17:10:51 ns29670 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
May 25 17:10:51 ns29670 mysqld: InnoDB: about forcing recovery.
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 - mysqld got signal 6 ;
May 25 17:10:51 ns29670 mysqld: This could be because you hit a bug. It is also possible that this binary
May 25 17:10:51 ns29670 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 25 17:10:51 ns29670 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 25 17:10:51 ns29670 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
May 25 17:10:51 ns29670 mysqld: the problem, but since we have already crashed, something is definitely wrong
May 25 17:10:51 ns29670 mysqld: and this may fail.
May 25 17:10:51 ns29670 mysqld:
May 25 17:10:51 ns29670 mysqld: key_buffer_size=16777216
May 25 17:10:51 ns29670 mysqld: read_buffer_size=131072
May 25 17:10:51 ns29670 mysqld: max_used_connections=26
May 25 17:10:51 ns29670 mysqld: max_threads=151
May 25 17:10:51 ns29670 mysqld: threads_connected=15
May 25 17:10:51 ns29670 mysqld: It is possible that mysqld could use up to
May 25 17:10:51 ns29670 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K
May 25 17:10:51 ns29670 mysqld: bytes of memory
May 25 17:10:51 ns29670 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 25 17:10:51 ns29670 mysqld:
May 25 17:10:51 ns29670 mysqld: Thread pointer: 0x7fb24424a5c0
May 25 17:10:51 ns29670 mysqld: Attempting backtrace. You can use the following information to find out
May 25 17:10:51 ns29670 mysqld: where mysqld died. If you see no messages after this, something went
May 25 17:10:51 ns29670 mysqld: terribly wrong...
May 25 17:10:51 ns29670 mysqld: stack_bottom = 0x7fb2a091fe88 thread_stack 0x30000
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7fb2a10e7ef9]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(handle_segfault+0x435) [0x7fb2a0e42d25]
May 25 17:10:51 ns29670 mysqld: /lib/libpthread.so.0(+0xef60) [0x7fb2a06bef60]
May 25 17:10:51 ns29670 mysqld: /lib/libc.so.6(gsignal+0x35) [0x7fb29f162165]
May 25 17:10:51 ns29670 mysqld: /lib/libc.so.6(abort+0x180) [0x7fb29f164f70]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7fb2a0fc43ff]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7fb2a0fca11f]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(+0x46033f) [0x7fb2a0f4c33f]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0xa8c) [0x7fb2a0f57bbc]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x200) [0x7fb2a0f47c20]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x4e5) [0x7fb2a0eb82f5]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x15c) [0x7fb2a0eb488c]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7fb2a0eb9fd4]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(+0x36108a) [0x7fb2a0e4d08a]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x4ce) [0x7fb2a0e4f21e]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d3) [0x7fb2a0e546b3]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd3d) [0x7fb2a0e5586d]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7fb2a0e563da]
May 25 17:10:51 ns29670 mysqld: /usr/sbin/mysqld(handle_one_connection+0x22d) [0x7fb2a0e4946d]
May 25 17:10:51 ns29670 mysqld: /lib/libpthread.so.0(+0x68ba) [0x7fb2a06b68ba]
May 25 17:10:51 ns29670 mysqld: /lib/libc.so.6(clone+0x6d) [0x7fb29f1ff02d]
May 25 17:10:51 ns29670 mysqld:
May 25 17:10:51 ns29670 mysqld: Trying to get some variables.
May 25 17:10:51 ns29670 mysqld: Some pointers may be invalid and cause the dump to abort.
May 25 17:10:51 ns29670 mysqld: Query (0x7fb24c02b390): is an invalid pointer
May 25 17:10:51 ns29670 mysqld: Connection ID (thread ID): 30311
May 25 17:10:51 ns29670 mysqld: Status: NOT_KILLED
May 25 17:10:51 ns29670 mysqld:
May 25 17:10:51 ns29670 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 25 17:10:51 ns29670 mysqld: information that should help you find out what is causing the crash.
May 25 17:10:51 ns29670 mysqld_safe: Number of processes running now: 0
May 25 17:10:51 ns29670 mysqld_safe: mysqld restarted
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 [Note] Plugin 'FEDERATED' is disabled.
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: Initializing buffer pool, size = 1.0G
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: Completed initialization of buffer pool
May 25 17:10:51 ns29670 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 20 1858236512
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: Database was not shut down normally!
May 25 17:10:51 ns29670 mysqld: InnoDB: Starting crash recovery.
May 25 17:10:51 ns29670 mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 25 17:10:51 ns29670 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 25 17:10:51 ns29670 mysqld: InnoDB: buffer...
May 25 17:10:51 ns29670 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 20 1858317448
May 25 17:10:51 ns29670 mysqld: 110525 17:10:51 InnoDB: Starting an apply batch of log records to the database...
May 25 17:10:52 ns29670 mysqld: InnoDB: Progress in percents: 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
May 25 17:10:52 ns29670 mysqld: InnoDB: Apply batch completed
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 InnoDB: Started; log sequence number 20 1858317448
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [Note] Event Scheduler: Loaded 0 events
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [Note] /usr/sbin/mysqld: ready for connections.
May 25 17:10:52 ns29670 mysqld: Version: '5.1.57-1~dotdeb.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 9481 (Debian)
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [ERROR] /usr/sbin/mysqld: La table './realmd/account' est marquée 'crashed' et devrait être réparée
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [Warning] Checking table: './realmd/account'
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [ERROR] /usr/sbin/mysqld: La table './bc_world/creature_respawn' est marquée 'crashed' et devrait être réparée
May 25 17:10:52 ns29670 mysqld: 110525 17:10:52 [Warning] Checking table: './bc_world/creature_respawn'
May 25 17:10:53 ns29670 mysqld: 110525 17:10:53 [ERROR] /usr/sbin/mysqld: La table './tlk_char/armory_character_stats' est marquée 'crashed' et devrait être réparée
May 25 17:10:53 ns29670 mysqld: 110525 17:10:53 [Warning] Checking table: './tlk_char/armory_character_stats'
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [ERROR] /usr/sbin/mysqld: La table './tlk_char/character_feed_log' est marquée 'crashed' et devrait être réparée
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [Warning] Checking table: './tlk_char/character_feed_log'
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:10:54 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:10:54 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:10:54 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:10:54 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:10:54 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Assertion failure in thread 139946615310080 in file ../../../storage/innobase/handler/ha_innodb.cc line 8085
May 25 17:10:54 ns29670 mysqld: InnoDB: Failing assertion: auto_inc > 0
May 25 17:10:54 ns29670 mysqld: InnoDB: We intentionally generate a memory trap.
May 25 17:10:54 ns29670 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 25 17:10:54 ns29670 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 25 17:10:54 ns29670 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 25 17:10:54 ns29670 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 25 17:10:54 ns29670 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
May 25 17:10:54 ns29670 mysqld: InnoDB: about forcing recovery.
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 - mysqld got signal 6 ;
May 25 17:10:54 ns29670 mysqld: This could be because you hit a bug. It is also possible that this binary
May 25 17:10:54 ns29670 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 25 17:10:54 ns29670 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 25 17:10:54 ns29670 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
May 25 17:10:54 ns29670 mysqld: the problem, but since we have already crashed, something is definitely wrong
May 25 17:10:54 ns29670 mysqld: and this may fail.
May 25 17:10:54 ns29670 mysqld:
May 25 17:10:54 ns29670 mysqld: key_buffer_size=16777216
May 25 17:10:54 ns29670 mysqld: read_buffer_size=131072
May 25 17:10:54 ns29670 mysqld: max_used_connections=3
May 25 17:10:54 ns29670 mysqld: max_threads=151
May 25 17:10:54 ns29670 mysqld: threads_connected=3
May 25 17:10:54 ns29670 mysqld: It is possible that mysqld could use up to
May 25 17:10:54 ns29670 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K
May 25 17:10:54 ns29670 mysqld: bytes of memory
May 25 17:10:54 ns29670 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 25 17:10:54 ns29670 mysqld:
May 25 17:10:54 ns29670 mysqld: Thread pointer: 0x7f482ea1a100
May 25 17:10:54 ns29670 mysqld: Attempting backtrace. You can use the following information to find out
May 25 17:10:54 ns29670 mysqld: where mysqld died. If you see no messages after this, something went
May 25 17:10:54 ns29670 mysqld: terribly wrong...
May 25 17:10:54 ns29670 mysqld: stack_bottom = 0x7f47dc4afe88 thread_stack 0x30000
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f482aa27ef9]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(handle_segfault+0x435) [0x7f482a782d25]
May 25 17:10:54 ns29670 mysqld: /lib/libpthread.so.0(+0xef60) [0x7f4829ffef60]
May 25 17:10:54 ns29670 mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f4828aa2165]
May 25 17:10:54 ns29670 mysqld: /lib/libc.so.6(abort+0x180) [0x7f4828aa4f70]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7f482a9043ff]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7f482a90a11f]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(+0x46033f) [0x7f482a88c33f]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0xa8c) [0x7f482a897bbc]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x200) [0x7f482a887c20]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x4e5) [0x7f482a7f82f5]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x15c) [0x7f482a7f488c]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7f482a7f9fd4]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(+0x36108a) [0x7f482a78d08a]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x4ce) [0x7f482a78f21e]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d3) [0x7f482a7946b3]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd3d) [0x7f482a79586d]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7f482a7963da]
May 25 17:10:54 ns29670 mysqld: /usr/sbin/mysqld(handle_one_connection+0x22d) [0x7f482a78946d]
May 25 17:10:54 ns29670 mysqld: /lib/libpthread.so.0(+0x68ba) [0x7f4829ff68ba]
May 25 17:10:54 ns29670 mysqld: /lib/libc.so.6(clone+0x6d) [0x7f4828b3f02d]
May 25 17:10:54 ns29670 mysqld:
May 25 17:10:54 ns29670 mysqld: Trying to get some variables.
May 25 17:10:54 ns29670 mysqld: Some pointers may be invalid and cause the dump to abort.
May 25 17:10:54 ns29670 mysqld: Query (0x7f482ea76eb0): SHOW TABLE STATUS FROM `tlk_char`
May 25 17:10:54 ns29670 mysqld: Connection ID (thread ID): 4
May 25 17:10:54 ns29670 mysqld: Status: NOT_KILLED
May 25 17:10:54 ns29670 mysqld:
May 25 17:10:54 ns29670 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 25 17:10:54 ns29670 mysqld: information that should help you find out what is causing the crash.
May 25 17:10:54 ns29670 mysqld_safe: Number of processes running now: 0
May 25 17:10:54 ns29670 mysqld_safe: mysqld restarted
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [Note] Plugin 'FEDERATED' is disabled.
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Initializing buffer pool, size = 1.0G
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Completed initialization of buffer pool
May 25 17:10:54 ns29670 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 20 1858236512
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Database was not shut down normally!
May 25 17:10:54 ns29670 mysqld: InnoDB: Starting crash recovery.
May 25 17:10:54 ns29670 mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 25 17:10:54 ns29670 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 25 17:10:54 ns29670 mysqld: InnoDB: buffer...
May 25 17:10:54 ns29670 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 20 1858342470
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Starting an apply batch of log records to the database...
May 25 17:10:54 ns29670 mysqld: InnoDB: Progress in percents: 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
May 25 17:10:54 ns29670 mysqld: InnoDB: Apply batch completed
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 InnoDB: Started; log sequence number 20 1858342470
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [Note] Event Scheduler: Loaded 0 events
May 25 17:10:54 ns29670 mysqld: 110525 17:10:54 [Note] /usr/sbin/mysqld: ready for connections.
May 25 17:10:54 ns29670 mysqld: Version: '5.1.57-1~dotdeb.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 9481 (Debian)
May 25 17:10:55 ns29670 mysqld: 110525 17:10:55 [ERROR] /usr/sbin/mysqld: La table './bc_world/creature_respawn' est marquée 'crashed' et devrait être réparée
May 25 17:10:55 ns29670 mysqld: 110525 17:10:55 [Warning] Checking table: './bc_world/creature_respawn'
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:10:57 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:10:57 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:10:57 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:10:57 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:10:57 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: Assertion failure in thread 140458354702080 in file ../../../storage/innobase/handler/ha_innodb.cc line 8085
May 25 17:10:57 ns29670 mysqld: InnoDB: Failing assertion: auto_inc > 0
May 25 17:10:57 ns29670 mysqld: InnoDB: We intentionally generate a memory trap.
May 25 17:10:57 ns29670 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 25 17:10:57 ns29670 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 25 17:10:57 ns29670 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 25 17:10:57 ns29670 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 25 17:10:57 ns29670 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
May 25 17:10:57 ns29670 mysqld: InnoDB: about forcing recovery.
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 - mysqld got signal 6 ;
May 25 17:10:57 ns29670 mysqld: This could be because you hit a bug. It is also possible that this binary
May 25 17:10:57 ns29670 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 25 17:10:57 ns29670 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 25 17:10:57 ns29670 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
May 25 17:10:57 ns29670 mysqld: the problem, but since we have already crashed, something is definitely wrong
May 25 17:10:57 ns29670 mysqld: and this may fail.
May 25 17:10:57 ns29670 mysqld:
May 25 17:10:57 ns29670 mysqld: key_buffer_size=16777216
May 25 17:10:57 ns29670 mysqld: read_buffer_size=131072
May 25 17:10:57 ns29670 mysqld: max_used_connections=6
May 25 17:10:57 ns29670 mysqld: max_threads=151
May 25 17:10:57 ns29670 mysqld: threads_connected=6
May 25 17:10:57 ns29670 mysqld: It is possible that mysqld could use up to
May 25 17:10:57 ns29670 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K
May 25 17:10:57 ns29670 mysqld: bytes of memory
May 25 17:10:57 ns29670 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 25 17:10:57 ns29670 mysqld:
May 25 17:10:57 ns29670 mysqld: Thread pointer: 0x7fbefc05e800
May 25 17:10:57 ns29670 mysqld: Attempting backtrace. You can use the following information to find out
May 25 17:10:57 ns29670 mysqld: where mysqld died. If you see no messages after this, something went
May 25 17:10:57 ns29670 mysqld: terribly wrong...
May 25 17:10:57 ns29670 mysqld: stack_bottom = 0x7fbf02566e88 thread_stack 0x30000
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7fbf50bd3ef9]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(handle_segfault+0x435) [0x7fbf5092ed25]
May 25 17:10:57 ns29670 mysqld: /lib/libpthread.so.0(+0xef60) [0x7fbf501aaf60]
May 25 17:10:57 ns29670 mysqld: /lib/libc.so.6(gsignal+0x35) [0x7fbf4ec4e165]
May 25 17:10:57 ns29670 mysqld: /lib/libc.so.6(abort+0x180) [0x7fbf4ec50f70]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7fbf50ab03ff]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7fbf50ab611f]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(+0x46033f) [0x7fbf50a3833f]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0xa8c) [0x7fbf50a43bbc]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x200) [0x7fbf50a33c20]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x4e5) [0x7fbf509a42f5]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x15c) [0x7fbf509a088c]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7fbf509a5fd4]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(+0x36108a) [0x7fbf5093908a]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x4ce) [0x7fbf5093b21e]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d3) [0x7fbf509406b3]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd3d) [0x7fbf5094186d]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7fbf509423da]
May 25 17:10:57 ns29670 mysqld: /usr/sbin/mysqld(handle_one_connection+0x22d) [0x7fbf5093546d]
May 25 17:10:57 ns29670 mysqld: /lib/libpthread.so.0(+0x68ba) [0x7fbf501a28ba]
May 25 17:10:57 ns29670 mysqld: /lib/libc.so.6(clone+0x6d) [0x7fbf4eceb02d]
May 25 17:10:57 ns29670 mysqld:
May 25 17:10:57 ns29670 mysqld: Trying to get some variables.
May 25 17:10:57 ns29670 mysqld: Some pointers may be invalid and cause the dump to abort.
May 25 17:10:57 ns29670 mysqld: Query (0x7fbf54cbc8c0): SHOW TABLE STATUS FROM `tlk_char`
May 25 17:10:57 ns29670 mysqld: Connection ID (thread ID): 9
May 25 17:10:57 ns29670 mysqld: Status: NOT_KILLED
May 25 17:10:57 ns29670 mysqld:
May 25 17:10:57 ns29670 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 25 17:10:57 ns29670 mysqld: information that should help you find out what is causing the crash.
May 25 17:10:57 ns29670 mysqld_safe: Number of processes running now: 0
May 25 17:10:57 ns29670 mysqld_safe: mysqld restarted
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 [Note] Plugin 'FEDERATED' is disabled.
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: Initializing buffer pool, size = 1.0G
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: Completed initialization of buffer pool
May 25 17:10:57 ns29670 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 20 1858236512
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: Database was not shut down normally!
May 25 17:10:57 ns29670 mysqld: InnoDB: Starting crash recovery.
May 25 17:10:57 ns29670 mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 25 17:10:57 ns29670 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 25 17:10:57 ns29670 mysqld: InnoDB: buffer...
May 25 17:10:57 ns29670 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 20 1858342735
May 25 17:10:57 ns29670 mysqld: 110525 17:10:57 InnoDB: Starting an apply batch of log records to the database...
May 25 17:10:57 ns29670 mysqld: InnoDB: Progress in percents: 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
May 25 17:10:57 ns29670 mysqld: InnoDB: Apply batch completed
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 InnoDB: Started; log sequence number 20 1858342735
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 [Note] Event Scheduler: Loaded 0 events
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 [Note] /usr/sbin/mysqld: ready for connections.
May 25 17:10:58 ns29670 mysqld: Version: '5.1.57-1~dotdeb.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 9481 (Debian)
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:10:58 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:10:58 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:10:58 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:10:58 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:10:58 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 InnoDB: Assertion failure in thread 139804015630080 in file ../../../storage/innobase/handler/ha_innodb.cc line 8085
May 25 17:10:58 ns29670 mysqld: InnoDB: Failing assertion: auto_inc > 0
May 25 17:10:58 ns29670 mysqld: InnoDB: We intentionally generate a memory trap.
May 25 17:10:58 ns29670 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 25 17:10:58 ns29670 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 25 17:10:58 ns29670 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 25 17:10:58 ns29670 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 25 17:10:58 ns29670 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
May 25 17:10:58 ns29670 mysqld: InnoDB: about forcing recovery.
May 25 17:10:58 ns29670 mysqld: 110525 17:10:58 - mysqld got signal 6 ;
May 25 17:10:58 ns29670 mysqld: This could be because you hit a bug. It is also possible that this binary
May 25 17:10:58 ns29670 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 25 17:10:58 ns29670 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 25 17:10:58 ns29670 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
May 25 17:10:58 ns29670 mysqld: the problem, but since we have already crashed, something is definitely wrong
May 25 17:10:58 ns29670 mysqld: and this may fail.
May 25 17:10:58 ns29670 mysqld:
May 25 17:10:58 ns29670 mysqld: key_buffer_size=16777216
May 25 17:10:58 ns29670 mysqld: read_buffer_size=131072
May 25 17:10:58 ns29670 mysqld: max_used_connections=3
May 25 17:10:58 ns29670 mysqld: max_threads=151
May 25 17:10:58 ns29670 mysqld: threads_connected=3
May 25 17:10:58 ns29670 mysqld: It is possible that mysqld could use up to
May 25 17:10:58 ns29670 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K
May 25 17:10:58 ns29670 mysqld: bytes of memory
May 25 17:10:58 ns29670 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 25 17:10:58 ns29670 mysqld:
May 25 17:10:58 ns29670 mysqld: Thread pointer: 0x7f26fb158850
May 25 17:10:58 ns29670 mysqld: Attempting backtrace. You can use the following information to find out
May 25 17:10:58 ns29670 mysqld: where mysqld died. If you see no messages after this, something went
May 25 17:10:58 ns29670 mysqld: terribly wrong...
May 25 17:10:58 ns29670 mysqld: stack_bottom = 0x7f26a8b08e88 thread_stack 0x30000
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f26f70e2ef9]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(handle_segfault+0x435) [0x7f26f6e3dd25]
May 25 17:10:58 ns29670 mysqld: /lib/libpthread.so.0(+0xef60) [0x7f26f66b9f60]
May 25 17:10:58 ns29670 mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f26f515d165]
May 25 17:10:58 ns29670 mysqld: /lib/libc.so.6(abort+0x180) [0x7f26f515ff70]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7f26f6fbf3ff]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7f26f6fc511f]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(+0x46033f) [0x7f26f6f4733f]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0xa8c) [0x7f26f6f52bbc]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x200) [0x7f26f6f42c20]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x4e5) [0x7f26f6eb32f5]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x15c) [0x7f26f6eaf88c]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7f26f6eb4fd4]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(+0x36108a) [0x7f26f6e4808a]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x4ce) [0x7f26f6e4a21e]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d3) [0x7f26f6e4f6b3]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd3d) [0x7f26f6e5086d]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7f26f6e513da]
May 25 17:10:58 ns29670 mysqld: /usr/sbin/mysqld(handle_one_connection+0x22d) [0x7f26f6e4446d]
May 25 17:10:58 ns29670 mysqld: /lib/libpthread.so.0(+0x68ba) [0x7f26f66b18ba]
May 25 17:10:58 ns29670 mysqld: /lib/libc.so.6(clone+0x6d) [0x7f26f51fa02d]
May 25 17:10:58 ns29670 mysqld:
May 25 17:10:58 ns29670 mysqld: Trying to get some variables.
May 25 17:10:58 ns29670 mysqld: Some pointers may be invalid and cause the dump to abort.
May 25 17:10:58 ns29670 mysqld: Query (0x7f26fb1631f0): SHOW TABLE STATUS FROM `tlk_char`
May 25 17:10:58 ns29670 mysqld: Connection ID (thread ID): 3
May 25 17:10:58 ns29670 mysqld: Status: NOT_KILLED
May 25 17:10:58 ns29670 mysqld:
May 25 17:10:58 ns29670 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 25 17:10:58 ns29670 mysqld: information that should help you find out what is causing the crash.
May 25 17:10:59 ns29670 mysqld_safe: Number of processes running now: 0
May 25 17:10:59 ns29670 mysqld_safe: mysqld restarted
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Note] Plugin 'FEDERATED' is disabled.
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 InnoDB: Initializing buffer pool, size = 1.0G
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 InnoDB: Completed initialization of buffer pool
May 25 17:10:59 ns29670 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 20 1858236512
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 InnoDB: Database was not shut down normally!
May 25 17:10:59 ns29670 mysqld: InnoDB: Starting crash recovery.
May 25 17:10:59 ns29670 mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 25 17:10:59 ns29670 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 25 17:10:59 ns29670 mysqld: InnoDB: buffer...
May 25 17:10:59 ns29670 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 20 1858342735
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 InnoDB: Starting an apply batch of log records to the database...
May 25 17:10:59 ns29670 mysqld: InnoDB: Progress in percents: 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
May 25 17:10:59 ns29670 mysqld: InnoDB: Apply batch completed
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 InnoDB: Started; log sequence number 20 1858342735
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Note] Event Scheduler: Loaded 0 events
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Note] /usr/sbin/mysqld: ready for connections.
May 25 17:10:59 ns29670 mysqld: Version: '5.1.57-1~dotdeb.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 9481 (Debian)
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [ERROR] /usr/sbin/mysqld: La table './snort/event' est marquée 'crashed' et devrait être réparée
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Warning] Checking table: './snort/event'
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [ERROR] /usr/sbin/mysqld: La table './snort/tcphdr' est marquée 'crashed' et devrait être réparée
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Warning] Checking table: './snort/tcphdr'
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [ERROR] /usr/sbin/mysqld: La table './snort/iphdr' est marquée 'crashed' et devrait être réparée
May 25 17:10:59 ns29670 mysqld: 110525 17:10:59 [Warning] Checking table: './snort/iphdr'
May 25 17:11:01 ns29670 mysqld: 110525 17:11:01 [ERROR] /usr/sbin/mysqld: La table './bc_world/creature_respawn' est marquée 'crashed' et devrait être réparée
May 25 17:11:01 ns29670 mysqld: 110525 17:11:01 [Warning] Checking table: './bc_world/creature_respawn'
May 25 17:11:01 ns29670 /USR/SBIN/CRON[32659]: (root) CMD (/usr/local/rtm/bin/rtm 24 > /dev/null 2> /dev/null)
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:11:04 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:11:04 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:11:04 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:11:04 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:11:04 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 InnoDB: Assertion failure in thread 139764384794368 in file ../../../storage/innobase/handler/ha_innodb.cc line 8085
May 25 17:11:04 ns29670 mysqld: InnoDB: Failing assertion: auto_inc > 0
May 25 17:11:04 ns29670 mysqld: InnoDB: We intentionally generate a memory trap.
May 25 17:11:04 ns29670 mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
May 25 17:11:04 ns29670 mysqld: InnoDB: If you get repeated assertion failures or crashes, even
May 25 17:11:04 ns29670 mysqld: InnoDB: immediately after the mysqld startup, there may be
May 25 17:11:04 ns29670 mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
May 25 17:11:04 ns29670 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
May 25 17:11:04 ns29670 mysqld: InnoDB: about forcing recovery.
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 - mysqld got signal 6 ;
May 25 17:11:04 ns29670 mysqld: This could be because you hit a bug. It is also possible that this binary
May 25 17:11:04 ns29670 mysqld: or one of the libraries it was linked against is corrupt, improperly built,
May 25 17:11:04 ns29670 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
May 25 17:11:04 ns29670 mysqld: We will try our best to scrape up some info that will hopefully help diagnose
May 25 17:11:04 ns29670 mysqld: the problem, but since we have already crashed, something is definitely wrong
May 25 17:11:04 ns29670 mysqld: and this may fail.
May 25 17:11:04 ns29670 mysqld:
May 25 17:11:04 ns29670 mysqld: key_buffer_size=16777216
May 25 17:11:04 ns29670 mysqld: read_buffer_size=131072
May 25 17:11:04 ns29670 mysqld: max_used_connections=7
May 25 17:11:04 ns29670 mysqld: max_threads=151
May 25 17:11:04 ns29670 mysqld: threads_connected=6
May 25 17:11:04 ns29670 mysqld: It is possible that mysqld could use up to
May 25 17:11:04 ns29670 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346521 K
May 25 17:11:04 ns29670 mysqld: bytes of memory
May 25 17:11:04 ns29670 mysqld: Hope that's ok; if not, decrease some variables in the equation.
May 25 17:11:04 ns29670 mysqld:
May 25 17:11:04 ns29670 mysqld: Thread pointer: 0x7f1dc0f0c430
May 25 17:11:04 ns29670 mysqld: Attempting backtrace. You can use the following information to find out
May 25 17:11:04 ns29670 mysqld: where mysqld died. If you see no messages after this, something went
May 25 17:11:04 ns29670 mysqld: terribly wrong...
May 25 17:11:04 ns29670 mysqld: stack_bottom = 0x7f1d6e81fe88 thread_stack 0x30000
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f1dbce8cef9]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(handle_segfault+0x435) [0x7f1dbcbe7d25]
May 25 17:11:04 ns29670 mysqld: /lib/libpthread.so.0(+0xef60) [0x7f1dbc463f60]
May 25 17:11:04 ns29670 mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f1dbaf07165]
May 25 17:11:04 ns29670 mysqld: /lib/libc.so.6(abort+0x180) [0x7f1dbaf09f70]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) [0x7f1dbcd693ff]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) [0x7f1dbcd6f11f]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(+0x46033f) [0x7f1dbccf133f]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(get_all_tables(THD*, TABLE_LIST*, Item*)+0xa8c) [0x7f1dbccfcbbc]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(get_schema_tables_result(JOIN*, enum_schema_table_state)+0x200) [0x7f1dbccecc20]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(JOIN::exec()+0x4e5) [0x7f1dbcc5d2f5]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x15c) [0x7f1dbcc5988c]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x174) [0x7f1dbcc5efd4]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(+0x36108a) [0x7f1dbcbf208a]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x4ce) [0x7f1dbcbf421e]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x2d3) [0x7f1dbcbf96b3]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0xd3d) [0x7f1dbcbfa86d]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) [0x7f1dbcbfb3da]
May 25 17:11:04 ns29670 mysqld: /usr/sbin/mysqld(handle_one_connection+0x22d) [0x7f1dbcbee46d]
May 25 17:11:04 ns29670 mysqld: /lib/libpthread.so.0(+0x68ba) [0x7f1dbc45b8ba]
May 25 17:11:04 ns29670 mysqld: /lib/libc.so.6(clone+0x6d) [0x7f1dbafa402d]
May 25 17:11:04 ns29670 mysqld:
May 25 17:11:04 ns29670 mysqld: Trying to get some variables.
May 25 17:11:04 ns29670 mysqld: Some pointers may be invalid and cause the dump to abort.
May 25 17:11:04 ns29670 mysqld: Query (0x7f1d68044540): is an invalid pointer
May 25 17:11:04 ns29670 mysqld: Connection ID (thread ID): 9
May 25 17:11:04 ns29670 mysqld: Status: NOT_KILLED
May 25 17:11:04 ns29670 mysqld:
May 25 17:11:04 ns29670 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
May 25 17:11:04 ns29670 mysqld: information that should help you find out what is causing the crash.
May 25 17:11:04 ns29670 mysqld_safe: Number of processes running now: 0
May 25 17:11:04 ns29670 mysqld_safe: mysqld restarted
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 [Warning] '--log_slow_queries' is deprecated and will be removed in a future release. Please use ''--slow_query_log'/'--slow_query_log_file'' instead.
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 [Note] Plugin 'FEDERATED' is disabled.
May 25 17:11:04 ns29670 mysqld: 110525 17:11:04 InnoDB: Initializing buffer pool, size = 1.0G
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 InnoDB: Completed initialization of buffer pool
May 25 17:11:05 ns29670 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 20 1858236512
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 InnoDB: Database was not shut down normally!
May 25 17:11:05 ns29670 mysqld: InnoDB: Starting crash recovery.
May 25 17:11:05 ns29670 mysqld: InnoDB: Reading tablespace information from the .ibd files...
May 25 17:11:05 ns29670 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
May 25 17:11:05 ns29670 mysqld: InnoDB: buffer...
May 25 17:11:05 ns29670 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 20 1858343786
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 InnoDB: Starting an apply batch of log records to the database...
May 25 17:11:05 ns29670 mysqld: InnoDB: Progress in percents: 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
May 25 17:11:05 ns29670 mysqld: InnoDB: Apply batch completed
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 InnoDB: Started; log sequence number 20 1858343786
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Note] Event Scheduler: Loaded 0 events
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Note] /usr/sbin/mysqld: ready for connections.
May 25 17:11:05 ns29670 mysqld: Version: '5.1.57-1~dotdeb.1-log' socket: '/var/run/mysqld/mysqld.sock' port: 9481 (Debian)
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [ERROR] /usr/sbin/mysqld: La table './snort/event' est marquée 'crashed' et devrait être réparée
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Warning] Checking table: './snort/event'
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [ERROR] /usr/sbin/mysqld: La table './snort/tcphdr' est marquée 'crashed' et devrait être réparée
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Warning] Checking table: './snort/tcphdr'
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [ERROR] /usr/sbin/mysqld: La table './snort/iphdr' est marquée 'crashed' et devrait être réparée
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Warning] Checking table: './snort/iphdr'
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [ERROR] /usr/sbin/mysqld: La table './snort/data' est marquée 'crashed' et devrait être réparée
May 25 17:11:05 ns29670 mysqld: 110525 17:11:05 [Warning] Checking table: './snort/data'
May 25 17:11:06 ns29670 mysqld: 110525 17:11:06 [ERROR] /usr/sbin/mysqld: La table './realmd/account' est marquée 'crashed' et devrait être réparée
May 25 17:11:06 ns29670 mysqld: 110525 17:11:06 [Warning] Checking table: './realmd/account'
May 25 17:11:17 ns29670 mysqld: 110525 17:11:17 [ERROR] /usr/sbin/mysqld: La table './snort/opt' est marquée 'crashed' et devrait être réparée
May 25 17:11:17 ns29670 mysqld: 110525 17:11:17 [Warning] Checking table: './snort/opt'
May 25 17:11:27 ns29670 mysqld: 110525 17:11:27 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
May 25 17:11:27 ns29670 mysqld: InnoDB: Unable to find the AUTOINC column surveyId in the InnoDB table tlk_char/gm_subsurveys.
May 25 17:11:27 ns29670 mysqld: InnoDB: We set the next AUTOINC column value to 0,
May 25 17:11:27 ns29670 mysqld: InnoDB: in effect disabling the AUTOINC next value generation.
May 25 17:11:27 ns29670 mysqld: InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
May 25 17:11:27 ns29670 mysqld: InnoDB: or fix the data dictionary by recreating the table.