Could be a crash related to innodb data dictionary being out of sync. Could be a bug.
http://bugs.mysql.com/bug.php?id=55277 On 12 Oct 2013 11:21, "Jørn Dahl-Stamnes" <sq...@dahl-stamnes.net> wrote: > On Saturday 12 October 2013 12:01, nixofortune wrote: > > You might want to comment > > > > bind-address = 127.0.0.1 > > > > in your my.cnf and restart mysql server. > > It does not explain why it works under low load and not under high load. > > However, I seem to have found something. When I started phpMyAdmin and > selected one of the database, the server went away again and I found this > in /var/log/syslog: > > Oct 12 11:53:33 cebycny mysqld: 131012 11:53:33 InnoDB: Assertion failure > in > thread 140182892447488 in file > ../../../storage/innobase/handler/ha_innodb.cc > line > 8066 > Oct 12 11:53:33 cebycny mysqld: InnoDB: Failing assertion: auto_inc > 0 > Oct 12 11:53:33 cebycny mysqld: InnoDB: We intentionally generate a memory > trap. > Oct 12 11:53:33 cebycny mysqld: InnoDB: Submit a detailed bug report to > http://bugs.mysql.com. > Oct 12 11:53:33 cebycny mysqld: InnoDB: If you get repeated assertion > failures > or crashes, even > Oct 12 11:53:33 cebycny mysqld: InnoDB: immediately after the mysqld > startup, > there may be > Oct 12 11:53:33 cebycny mysqld: InnoDB: corruption in the InnoDB > tablespace. > Please refer to > Oct 12 11:53:33 cebycny mysqld: InnoDB: > http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html > Oct 12 11:53:33 cebycny mysqld: InnoDB: about forcing recovery. > Oct 12 11:53:33 cebycny mysqld: 09:53:33 UTC - mysqld got signal 6 ; > Oct 12 11:53:33 cebycny mysqld: This could be because you hit a bug. It is > also possible that this binary > Oct 12 11:53:33 cebycny mysqld: or one of the libraries it was linked > against > is corrupt, improperly built, > Oct 12 11:53:33 cebycny mysqld: or misconfigured. This error can also be > caused by malfunctioning hardware. > Oct 12 11:53:33 cebycny mysqld: We will try our best to scrape up some info > that will hopefully help > Oct 12 11:53:33 cebycny mysqld: diagnose the problem, but since we have > already crashed, > Oct 12 11:53:33 cebycny mysqld: something is definitely wrong and this may > fail. > Oct 12 11:53:33 cebycny mysqld: > Oct 12 11:53:33 cebycny mysqld: key_buffer_size=2147483648 > Oct 12 11:53:33 cebycny mysqld: read_buffer_size=2097152 > Oct 12 11:53:33 cebycny mysqld: max_used_connections=8 > Oct 12 11:53:33 cebycny mysqld: max_threads=100 > Oct 12 11:53:33 cebycny mysqld: thread_count=2 > Oct 12 11:53:33 cebycny mysqld: connection_count=2 > Oct 12 11:53:33 cebycny mysqld: It is possible that mysqld could use up to > Oct 12 11:53:33 cebycny mysqld: key_buffer_size + (read_buffer_size + > sort_buffer_size)*max_threads = 3941387 K bytes of memory > Oct 12 11:53:33 cebycny mysqld: Hope that's ok; if not, decrease some > variables in the equation. > Oct 12 11:53:33 cebycny mysqld: > Oct 12 11:53:33 cebycny mysqld: Thread pointer: 0x7f7f1bf997c0 > Oct 12 11:53:33 cebycny mysqld: Attempting backtrace. You can use the > following information to find out > Oct 12 11:53:33 cebycny mysqld: where mysqld died. If you see no messages > after this, something went > Oct 12 11:53:33 cebycny mysqld: terribly wrong... > Oct 12 11:53:33 cebycny mysqld: stack_bottom = 7f7edf81fe88 thread_stack > 0x30000 > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) > [0x7f7edff62b59] > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x483) > [0x7f7edfd774a3] > Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0xeff0) > [0x7f7edf4c9ff0] > Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(gsignal+0x35) > [0x7f7eddf6c1b5] > Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(abort+0x180) > [0x7f7eddf6efc0] > Oct 12 11:53:33 cebycny > mysqld: /usr/sbin/mysqld(ha_innobase::innobase_peek_autoinc()+0x8f) > [0x7f7edfe1fa2f] > Oct 12 11:53:33 cebycny > mysqld: /usr/sbin/mysqld(ha_innobase::info_low(unsigned int, bool)+0x18f) > [0x7f7edfe2524f] > Oct 12 11:53:33 cebycny > mysqld: > /usr/sbin/mysqld(ha_innobase::update_create_info(st_ha_create_information*)+0x29) > [0x7f7edfe256b9] > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(+0x49e3dc) > [0x7f7edfd953dc] > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysqld_show_create(THD*, > TABLE_LIST*)+0x7a8) [0x7f7edfd9d388] > Oct 12 11:53:33 cebycny > mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0x184a) > [0x7f7edfc7cb0a] > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, > unsigned int, char const**)+0x3fb) [0x7f7edfc80dbb] > Oct 12 11:53:33 cebycny > mysqld: /usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, > unsigned int)+0x115a) [0x7f7edfc81f2a] > Oct 12 11:53:33 cebycny mysqld: /usr/sbin/mysqld(do_command(THD*)+0xea) > [0x7f7edfc8285a] > Oct 12 11:53:33 cebycny mysqld: > /usr/sbin/mysqld(handle_one_connection+0x235) > [0x7f7edfc74435] > Oct 12 11:53:33 cebycny mysqld: /lib/libpthread.so.0(+0x68ca) > [0x7f7edf4c18ca] > Oct 12 11:53:33 cebycny mysqld: /lib/libc.so.6(clone+0x6d) [0x7f7ede00992d] > Oct 12 11:53:33 cebycny mysqld: > Oct 12 11:53:33 cebycny mysqld: Trying to get some variables. > Oct 12 11:53:33 cebycny mysqld: Some pointers may be invalid and cause the > dump to abort. > Oct 12 11:53:33 cebycny mysqld: Query (7f7f1c0dcbc0): SHOW CREATE TABLE > `calculation` > Oct 12 11:53:33 cebycny mysqld: Connection ID (thread ID): 92 > Oct 12 11:53:33 cebycny mysqld: Status: NOT_KILLED > Oct 12 11:53:33 cebycny mysqld: > Oct 12 11:53:33 cebycny mysqld: The manual page at > http://dev.mysql.com/doc/mysql/en/crashing.html contains > Oct 12 11:53:33 cebycny mysqld: information that should help you find out > what > is causing the crash. > Oct 12 11:53:33 cebycny mysqld_safe: Number of processes running now: 0 > Oct 12 11:53:33 cebycny mysqld_safe: mysqld restarted > > -- > Jørn Dahl-Stamnes > homepage: http://photo.dahl-stamnes.net/ > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql > >
