Comment 2 for bug 1384845

Revision history for this message
monty solomon (monty+launchpad) wrote :

*** glibc detected *** /usr/sbin/mysqld: double free or corruption (fasttop): 0x00007fe33047f040 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x76166)[0x7fe71c04c166]
/lib64/libldap-2.4.so.2(ldap_pvt_tls_set_option+0x244)[0x7fe3edfcfc74]
/lib64/libldap-2.4.so.2(ldap_set_option+0xd6)[0x7fe3edfc54b6]
/lib64/security/pam_ldap.so(+0x2a8f)[0x7fe3ee1eba8f]
/lib64/security/pam_ldap.so(+0x5428)[0x7fe3ee1ee428]
/lib64/security/pam_ldap.so(+0x56c1)[0x7fe3ee1ee6c1]
/lib64/security/pam_ldap.so(+0x66f3)[0x7fe3ee1ef6f3]
/lib64/security/pam_ldap.so(pam_sm_authenticate+0x2fc)[0x7fe3ee1ef9fc]
/lib64/libpam.so.0(+0x2cee)[0x7fe71973acee]
/lib64/libpam.so.0(pam_authenticate+0x40)[0x7fe71973a600]
/usr/lib64/mysql/plugin/auth_pam.so(authenticate_user_with_pam_server+0xda)[0x7fe6df2cf55a]
/usr/sbin/mysqld[0x660ddd]
/usr/sbin/mysqld(_Z16acl_authenticateP3THDj+0xf11)[0x675f61]
/usr/sbin/mysqld[0x6a2393]
/usr/sbin/mysqld(_Z16login_connectionP3THD+0x42)[0x6a3de2]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x24)[0x6a4534]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x136)[0x6a4856]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6a4970]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0xb0dc13]
/lib64/libpthread.so.0(+0x79d1)[0x7fe71d99f9d1]
/lib64/libc.so.6(clone+0x6d)[0x7fe71c0beb6d]

12:09:07 UTC - mysqld got signal 6 ;
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=291
max_threads=502
thread_count=132
connection_count=132
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 715477 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x160c1cb0
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 = 7fe339851d40 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x8bb80c]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x6504b9]
/lib64/libpthread.so.0(+0xf710)[0x7fe71d9a7710]
/lib64/libc.so.6(gsignal+0x35)[0x7fe71c008925]
/lib64/libc.so.6(abort+0x175)[0x7fe71c00a105]
/lib64/libc.so.6(+0x70837)[0x7fe71c046837]
/lib64/libc.so.6(+0x76166)[0x7fe71c04c166]
/lib64/libldap-2.4.so.2(ldap_pvt_tls_set_option+0x244)[0x7fe3edfcfc74]
/lib64/libldap-2.4.so.2(ldap_set_option+0xd6)[0x7fe3edfc54b6]
/lib64/security/pam_ldap.so(+0x2a8f)[0x7fe3ee1eba8f]
/lib64/security/pam_ldap.so(+0x5428)[0x7fe3ee1ee428]
/lib64/security/pam_ldap.so(+0x56c1)[0x7fe3ee1ee6c1]
/lib64/security/pam_ldap.so(+0x66f3)[0x7fe3ee1ef6f3]
/lib64/security/pam_ldap.so(pam_sm_authenticate+0x2fc)[0x7fe3ee1ef9fc]
/lib64/libpam.so.0(+0x2cee)[0x7fe71973acee]
/lib64/libpam.so.0(pam_authenticate+0x40)[0x7fe71973a600]
/usr/lib64/mysql/plugin/auth_pam.so(authenticate_user_with_pam_server+0xda)[0x7fe6df2cf55a]
/usr/sbin/mysqld[0x660ddd]
/usr/sbin/mysqld(_Z16acl_authenticateP3THDj+0xf11)[0x675f61]
/usr/sbin/mysqld[0x6a2393]
/usr/sbin/mysqld(_Z16login_connectionP3THD+0x42)[0x6a3de2]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x24)[0x6a4534]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x136)[0x6a4856]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6a4970]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0xb0dc13]
/lib64/libpthread.so.0(+0x79d1)[0x7fe71d99f9d1]
/lib64/libc.so.6(clone+0x6d)[0x7fe71c0beb6d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 153631
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
141023 12:09:07 mysqld_safe Number of processes running now: 0
141023 12:09:07 mysqld_safe mysqld restarted