Thread pointer: 0xc32a7c0 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 = 7f526c66ce88 thread_stack 0x60000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x7711ce] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65d21a] /lib/libpthread.so.0(+0xeff0)[0x7f54ce0b5ff0] /lib/libc.so.6(+0x1071ba)[0x7f54cce461ba] /usr/local/mysql/bin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_LIST+0x4e)[0x5e334e] /usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x169)[0x542ad9] /usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x30f)[0x543edf] /usr/local/mysql/bin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x47)[0x544947] /usr/local/mysql/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xd2)[0x565942] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1158)[0x575828] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x578ab9] /usr/local/mysql/bin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x9c4)[0x6f9d14] /usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x11d)[0x51cb6d] /usr/local/mysql/bin/mysqld[0x522146] /usr/local/mysql/bin/mysqld(handle_slave_sql+0x8f5)[0x523495] /lib/libpthread.so.0(+0x68ca)[0x7f54ce0ad8ca] /lib/libc.so.6(clone+0x6d)[0x7f54cce0eb6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f526000a851): is an invalid pointer Connection ID (thread ID): 1 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. The "--memlock" argument, which was enabled, uses system calls that are unreliable and unstable on some operating systems and operating-system versions (notably, some versions of Linux). This crash could be due to use of those buggy OS calls. You should consider whether you really need the "--memlock" parameter and/or consult the OS distributer about "mlockall" bugs. 121024 11:55:29 mysqld_safe Number of processes running now: 0 121024 11:55:29 mysqld_safe mysqld restarted 121024 11:55:29 InnoDB: The InnoDB memory heap is disabled 121024 11:55:29 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121024 11:55:29 InnoDB: Compressed tables use zlib 1.2.3.4 121024 11:55:29 InnoDB: Initializing buffer pool, size = 6.0G 121024 11:55:29 InnoDB: Completed initialization of buffer pool 121024 11:55:29 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 121024 11:55:29 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: Last MySQL binlog file position 0 694068425, file name /var/log/mysql/mysql-bin.000018 121024 11:55:30 InnoDB: Waiting for the background threads to start 121024 11:55:31 InnoDB: 1.1.8 started; log sequence number 18745216049 121024 11:55:31 [Note] Recovering after a crash using /var/log/mysql/mysql-bin 121024 11:55:31 [Note] Starting crash recovery... 121024 11:55:31 [Note] Crash recovery finished. 121024 11:55:34 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 121024 11:55:34 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 121024 11:55:34 [Note] Server socket created on IP: '0.0.0.0'. 121024 11:55:34 [Warning] 'user' entry 'root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:34 [Warning] 'user' entry '@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:34 [Warning] 'proxies_priv' entry '@ root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:34 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. 121024 11:55:34 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000399' at position 723815324, relay log './mysqld-relay-bin.000002' position: 22388051 121024 11:55:34 [Note] Slave I/O thread: connected to master 'replica@10.0.0.10:3306',replication started in log 'mysql-bin.000402' at position 664874322 121024 11:55:34 [Note] Event Scheduler: Loaded 0 events 121024 11:55:34 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.28-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution 09:55:34 UTC - 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=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=800 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1758110 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0xb3f6070 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 = 7fdabb199e88 thread_stack 0x60000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x7711ce] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65d21a] /lib/libpthread.so.0(+0xeff0)[0x7fdd1cbe2ff0] /lib/libc.so.6(+0x1071ba)[0x7fdd1b9731ba] /usr/local/mysql/bin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_LIST+0x4e)[0x5e334e] /usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x169)[0x542ad9] /usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x30f)[0x543edf] /usr/local/mysql/bin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x47)[0x544947] /usr/local/mysql/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xd2)[0x565942] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1158)[0x575828] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x578ab9] /usr/local/mysql/bin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x9c4)[0x6f9d14] /usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x11d)[0x51cb6d] /usr/local/mysql/bin/mysqld[0x522146] /usr/local/mysql/bin/mysqld(handle_slave_sql+0x8f5)[0x523495] /lib/libpthread.so.0(+0x68ca)[0x7fdd1cbda8ca] /lib/libc.so.6(clone+0x6d)[0x7fdd1b93bb6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7fdab000aa71): is an invalid pointer Connection ID (thread ID): 1 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. The "--memlock" argument, which was enabled, uses system calls that are unreliable and unstable on some operating systems and operating-system versions (notably, some versions of Linux). This crash could be due to use of those buggy OS calls. You should consider whether you really need the "--memlock" parameter and/or consult the OS distributer about "mlockall" bugs. 121024 11:55:35 mysqld_safe Number of processes running now: 0 121024 11:55:35 mysqld_safe mysqld restarted 121024 11:55:35 InnoDB: The InnoDB memory heap is disabled 121024 11:55:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121024 11:55:35 InnoDB: Compressed tables use zlib 1.2.3.4 121024 11:55:35 InnoDB: Initializing buffer pool, size = 6.0G 121024 11:55:36 InnoDB: Completed initialization of buffer pool 121024 11:55:36 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 121024 11:55:36 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: Last MySQL binlog file position 0 694068425, file name /var/log/mysql/mysql-bin.000018 121024 11:55:36 InnoDB: Waiting for the background threads to start 121024 11:55:37 InnoDB: 1.1.8 started; log sequence number 18745216049 121024 11:55:37 [Note] Recovering after a crash using /var/log/mysql/mysql-bin 121024 11:55:37 [Note] Starting crash recovery... 121024 11:55:37 [Note] Crash recovery finished. 121024 11:55:41 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 121024 11:55:41 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 121024 11:55:41 [Note] Server socket created on IP: '0.0.0.0'. 121024 11:55:41 [Warning] 'user' entry 'root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:41 [Warning] 'user' entry '@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:41 [Warning] 'proxies_priv' entry '@ root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:41 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. 121024 11:55:41 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000399' at position 723815324, relay log './mysqld-relay-bin.000002' position: 22388051 121024 11:55:41 [Note] Slave I/O thread: connected to master 'replica@10.0.0.10:3306',replication started in log 'mysql-bin.000402' at position 664905180 121024 11:55:41 [Note] Event Scheduler: Loaded 0 events 121024 11:55:41 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.28-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution 09:55:41 UTC - 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=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=800 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1758110 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0xd15b640 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 = 7fdbb4c4fe88 thread_stack 0x60000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x7711ce] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65d21a] /lib/libpthread.so.0(+0xeff0)[0x7fde16698ff0] /lib/libc.so.6(+0x1072c8)[0x7fde154292c8] /usr/local/mysql/bin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_LIST+0x4e)[0x5e334e] /usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x169)[0x542ad9] /usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x30f)[0x543edf] /usr/local/mysql/bin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x47)[0x544947] /usr/local/mysql/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xd2)[0x565942] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1158)[0x575828] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x578ab9] /usr/local/mysql/bin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x9c4)[0x6f9d14] /usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x11d)[0x51cb6d] /usr/local/mysql/bin/mysqld[0x522146] /usr/local/mysql/bin/mysqld(handle_slave_sql+0x8f5)[0x523495] /lib/libpthread.so.0(+0x68ca)[0x7fde166908ca] /lib/libc.so.6(clone+0x6d)[0x7fde153f1b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (d168bd1): /* Suppliertool: /BACKUP/var/kunden/webs/defshop/html_new/backend/cron_scripts/create_pixi_order.php:139 */ INSERT INTO `defshop-backend`.`suppliertool_items` (`ItemKey`,`SOrderRef`,`ArtName`,`ArtNr`,`Barcode`,`ItemNrInt`,`products_id`,`products_model`,`st_item_status`) VALUES ( 614574, 46090, 'Mitchell and Ness Commerative Finals Patch Chicago Bulls 1992 Cap White (Verstellbar)', 'NM09ZFINALS92CHIBWHT', '2009298600822', '2009298600822', 92986, 'NM09ZFINALS92CHIBWHT', 2) Connection ID (thread ID): 1 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. The "--memlock" argument, which was enabled, uses system calls that are unreliable and unstable on some operating systems and operating-system versions (notably, some versions of Linux). This crash could be due to use of those buggy OS calls. You should consider whether you really need the "--memlock" parameter and/or consult the OS distributer about "mlockall" bugs. 121024 11:55:42 mysqld_safe Number of processes running now: 0 121024 11:55:42 mysqld_safe mysqld restarted 121024 11:55:42 InnoDB: The InnoDB memory heap is disabled 121024 11:55:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121024 11:55:42 InnoDB: Compressed tables use zlib 1.2.3.4 121024 11:55:42 InnoDB: Initializing buffer pool, size = 6.0G 121024 11:55:42 InnoDB: Completed initialization of buffer pool 121024 11:55:42 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 121024 11:55:42 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: Last MySQL binlog file position 0 694068425, file name /var/log/mysql/mysql-bin.000018 121024 11:55:42 InnoDB: Waiting for the background threads to start 121024 11:55:43 InnoDB: 1.1.8 started; log sequence number 18745216049 121024 11:55:43 [Note] Recovering after a crash using /var/log/mysql/mysql-bin 121024 11:55:43 [Note] Starting crash recovery... 121024 11:55:43 [Note] Crash recovery finished. 121024 11:55:47 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 121024 11:55:47 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 121024 11:55:47 [Note] Server socket created on IP: '0.0.0.0'. 121024 11:55:47 [Warning] 'user' entry 'root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:47 [Warning] 'user' entry '@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:47 [Warning] 'proxies_priv' entry '@ root@def-db06' ignored in --skip-name-resolve mode. 121024 11:55:47 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=mysqld-relay-bin' to avoid this problem. 121024 11:55:47 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000399' at position 723815324, relay log './mysqld-relay-bin.000002' position: 22388051 121024 11:55:47 [Note] Slave I/O thread: connected to master 'replica@10.0.0.10:3306',replication started in log 'mysql-bin.000402' at position 664907603 121024 11:55:47 [Note] Event Scheduler: Loaded 0 events 121024 11:55:47 [Note] /usr/local/mysql/bin/mysqld: ready for connections. Version: '5.5.28-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution 09:55:47 UTC - 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=8388608 read_buffer_size=131072 max_used_connections=0 max_threads=800 thread_count=0 connection_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1758110 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0xbde1640 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 = 7f6e64ab6e88 thread_stack 0x60000 /usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x7711ce] /usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65d21a] /lib/libpthread.so.0(+0xeff0)[0x7f70c64ffff0] /lib/libc.so.6(+0x107b88)[0x7f70c5290b88] /usr/local/mysql/bin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_LIST+0x4e)[0x5e334e] /usr/local/mysql/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootP18Open_table_context+0x169)[0x542ad9] /usr/local/mysql/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjjP19Prelocking_strategy+0x30f)[0x543edf] /usr/local/mysql/bin/mysqld(_Z20open_and_lock_tablesP3THDP10TABLE_LISTbjP19Prelocking_strategy+0x47)[0x544947] /usr/local/mysql/bin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xd2)[0x565942] /usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1158)[0x575828] /usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x578ab9] /usr/local/mysql/bin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x9c4)[0x6f9d14] /usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x11d)[0x51cb6d] /usr/local/mysql/bin/mysqld[0x522146] /usr/local/mysql/bin/mysqld(handle_slave_sql+0x8f5)[0x523495] /lib/libpthread.so.0(+0x68ca)[0x7f70c64f78ca] /lib/libc.so.6(clone+0x6d)[0x7f70c5258b6d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7f6e50001011): is an invalid pointer Connection ID (thread ID): 1 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. The "--memlock" argument, which was enabled, uses system calls that are unreliable and unstable on some operating systems and operating-system versions (notably, some versions of Linux). This crash could be due to use of those buggy OS calls. You should consider whether you really need the "--memlock" parameter and/or consult the OS distributer about "mlockall" bugs. 121024 11:55:48 mysqld_safe Number of processes running now: 0 121024 11:55:48 mysqld_safe mysqld restarted 121024 11:55:48 InnoDB: The InnoDB memory heap is disabled 121024 11:55:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121024 11:55:48 InnoDB: Compressed tables use zlib 1.2.3.4 121024 11:55:48 InnoDB: Initializing buffer pool, size = 6.0G 121024 11:55:48 InnoDB: Completed initialization of buffer pool 121024 11:55:48 InnoDB: highest supported file format is Barracuda. InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 121024 11:55:48 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: Last MySQL binlog file position 0 694068425, file name /var/log/mysql/mysql-bin.000018 121024 11:55:49 InnoDB: Waiting for the background threads to start