140615 8:18:01 [Note] /usr/sbin/mysqld: Shutdown complete 140615 08:18:01 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 140615 08:18:03 mysqld_safe Starting mysqld daemon with databases from /mnt/scsi/mysql 140615 8:18:03 [Warning] option 'net_buffer_length': unsigned value 2097152 adjusted to 1048576 140615 8:18:03 [Warning] option 'max_binlog_size': unsigned value 2147483648 adjusted to 1073741824 140615 8:18:03 [Warning] Could not increase number of max_open_files to more than 165000 (request: 1048707) 140615 8:18:03 InnoDB: The InnoDB memory heap is disabled 140615 8:18:03 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140615 8:18:03 InnoDB: Compressed tables use zlib 1.2.3.4 140615 8:18:03 InnoDB: Using Linux native AIO 140615 8:18:03 InnoDB: Initializing buffer pool, size = 25.0G 140615 8:18:05 InnoDB: Completed initialization of buffer pool 140615 8:18:05 InnoDB: highest supported file format is Barracuda. 140615 8:18:06 InnoDB: Waiting for the background threads to start 140615 8:18:07 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-35.0 started; log sequence number 12541977526695 140615 8:18:07 [Note] Plugin 'FEEDBACK' is disabled. 140615 8:18:07 [Note] Server socket created on IP: '0.0.0.0'. 140615 8:18:07 [Note] Server socket created on IP: '0.0.0.0'. 140615 8:18:07 [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 '--log-basename=#' or '--relay-log=mysqld-relay-bin' to avoid this problem. 140615 8:18:07 [Note] Slave SQL thread initialized, starting replication in log 'bin-log.000007' at position 57330, relay log './mysqld-relay-bin.000772' position: 4 140615 8:18:07 [Note] Event Scheduler: Loaded 10 events 140615 8:18:07 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.5.38-MariaDB-1~precise-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 140615 8:18:07 [Note] Event Scheduler: scheduler thread started with id 3 140615 8:18:22 [ERROR] Slave I/O: error connecting to master 'slave_user@192.168.6.2:3306' - retry-time: 60 retries: 86400 message: Can't connect to MySQL server on '192.168.6.2' (110), Error_code: 2003 140615 8:18:45 [Warning] IP address '192.168.1.21' could not be resolved: Name or service not known 140615 15:06:35 [Warning] IP address '192.168.1.81' could not be resolved: Name or service not known 140615 20:10:36 [Warning] Event Scheduler: [csenki@192.168.1.%][cegek_teszt.e_napicsod_tabla_karbantartas] InnoDB: ignoring KEY_BLOCK_SIZE=8 unless ROW_FORMAT=COMPRESSED. 140615 22:00:00 [Warning] IP address '192.168.1.41' could not be resolved: Name or service not known 140615 23:10:03 [Warning] IP address '192.168.1.59' could not be resolved: Name or service not known 140616 8:15:02 [Warning] IP address '192.168.1.85' could not be resolved: Name or service not known 140616 9:22:16 [Warning] IP address '192.168.1.223' could not be resolved: Name or service not known 140616 9:30:39 [Warning] IP address '192.168.1.96' could not be resolved: Name or service not known 140616 12:50:03 [ERROR] 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. To report this bug, see http://kb.askmonty.org/en/reporting-bugs 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. Server version: 5.5.38-MariaDB-1~precise-log key_buffer_size=3221225470 read_buffer_size=8388608 max_used_connections=77 max_threads=122 thread_count=73 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 7270511 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0x7f31e15f1000 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 = 0x7f30f63fee20 thread_stack 0xc8000 /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xa7499b] /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x6ccf88] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f399f14fcb0] /lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x29f1)[0x7f399d93a3b1] /lib/x86_64-linux-gnu/libc.so.6(__fprintf_chk+0xeb)[0x7f399d9f880b] /usr/sbin/mysqld[0x846dcc] /usr/sbin/mysqld[0x847fda] /usr/sbin/mysqld[0x849778] /usr/sbin/mysqld[0x83ec6f] /usr/sbin/mysqld[0x8095bc] /usr/sbin/mysqld(_Z14ha_show_statusP3THDP10handlerton12ha_stat_type+0x217)[0x6d4017] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3f13)[0x59fcc3] /usr/sbin/mysqld[0x5a1934] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x159f)[0x5a301f] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1fb)[0x65323b] /usr/sbin/mysqld(handle_one_connection+0x4c)[0x6532bc] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f399f147e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f399d9e33fd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f3171026018): SHOW /*!50000 ENGINE*/ INNODB STATUS Connection ID (thread ID): 141550 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off 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. Writing a core file 140616 12:51:30 mysqld_safe Number of processes running now: 0 140616 12:51:30 mysqld_safe mysqld restarted 140616 12:51:31 [Warning] option 'net_buffer_length': unsigned value 2097152 adjusted to 1048576 140616 12:51:31 [Warning] option 'max_binlog_size': unsigned value 2147483648 adjusted to 1073741824 140616 12:51:31 [Warning] Could not increase number of max_open_files to more than 165000 (request: 1048707)