ELF>@@ H\$Hl$؉Ld$Ll$Lt$L|$Hht"1f.1IIHl$ ILLd$H?HMfD$ 00D$"fD$00D$f$00N4:D$II)LILH?N,2H*II)LHLH?HH)LH4RHHH)HJIIT$L I)L)JIHT$L I)L)AHLH111HHp1H51H51H015151HHHHi.HHpHHH1H 1=HmHXA=t!AtAtA1Hu`1HEhH}`=FH1L11uX==ubus=%AG=&A011=u1t1@Hƿ111HH5tHHYFatal signal %d while backtracing %s:%s:%s UTC - mysqld got signal %d ; 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. It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = %lu K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 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... Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Connection ID (thread ID): %lu 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. This crash occured while the server was calling initgroups(). This is often due to the use of a mysqld that is statically linked against glibc and configured to use LDAP in /etc/nsswitch.conf. You will need to either upgrade to a version of glibc that does not have this problem (2.3.4 or later when used with nscd), disable LDAP in your nsswitch.conf, or use a mysqld that is not statically linked. You are running a statically-linked LinuxThreads binary on an NPTL system. This can result in crashes on some distributions due to LT/NPTL conflicts. You should either build a dynamically-linked binary, or force LinuxThreads to be used with the LD_ASSUME_KERNEL environment variable. Please consult the documentation for your distribution on how to do that. 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. %skey_buffer_size=%lu read_buffer_size=%ld max_used_connections=%lu max_threads=%u thread_count=%u connection_count=%u Thread pointer: 0x%p NOT_KILLEDUNKNOWNKILL_BAD_DATAKILL_CONNECTIONKILL_QUERYKILLED_NO_VALUEQuery (%p): Status: %s Writing a core file GCC: (GNU) 4.4.7 20120313 (Red Hat 4.4.7-11)zRx $RLXp.symtab.strtab.shstrtab.rela.text.data.bss.rodata.str1.8.rodata.str1.1.comment.note.GNU-stack.rela.eh_frame @R &,12@2 O0.Xm@h  w0  8 #R7MSXet,=N\qsignal_handler.cc_ZL10segfaultedhandle_fatal_signalmy_safe_printf_stderr_exittimemy_safe_itoadflt_key_cacheglobal_system_variablesmax_used_connectionsthread_schedulerthread_countconnection_countmax_connectionsTHR_THDpthread_getspecifictest_flagsmy_safe_print_strcalling_initgroupsthd_lib_detectedlocked_in_memorymy_write_coremy_thread_stack_sizemy_print_stacktraceld_assume_kernel_is_set&3 8 B ^g(L] (d i Pn u z 8       .  H  X  i  , $/C H M T Z_e     h            *7@M _ p            ~     2!? D I