[debian-mysql] Bug#711715: mysql-server-5.5: Segfault with libnss-mysql-bg enabled

[Aurélien Lemaire]

Hi there,

Same problem here as well.
debian 7 amd64 fully updated !
msql 5.5 + libnss-mysql-bg --> mysql crash when starting.

i testes by replacing mysql 5.5 with percona : same issue :

    /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql
    --plugin-dir=/usr/lib/mysql/plugin --user=mysql
    --log-error=/var/lib/mysql/stmicro-auth.err
    --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock
    --port=3306
    11:46:45 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.
    Please help us make Percona Server better by reporting any
    bugs at http://bugs.percona.com/

    key_buffer_size=0
    read_buffer_size=131072
    max_used_connections=0
    max_threads=152
    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 = 332624
    K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.

    Thread pointer: 0x0
    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 = 0 thread_stack 0x30000
    /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7d0cce]
    /usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6b8641]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7fbaef7d8030]
    /usr/sbin/mysqld(thd_increment_bytes_received+0x1a)[0x59ac1a]
    /usr/sbin/mysqld[0x552e35]
    /usr/sbin/mysqld(my_net_read+0x179)[0x5538f9]
    /usr/sbin/mysqld(cli_safe_read+0x2a)[0x69a96a]
    /usr/sbin/mysqld(mysql_real_connect+0x2ee)[0x69cc2e]
    /usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x2bc5)[0x7fbaecab3bc5]
    /usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x2f5c)[0x7fbaecab3f5c]
    /usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x324e)[0x7fbaecab424e]
    /usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(_nss_mysql_initgroups_dyn+0xa1)[0x7fbaecab4bf1]
    /lib/x86_64-linux-gnu/libc.so.6(+0xa94e2)[0x7fbaee3c94e2]
    /lib/x86_64-linux-gnu/libc.so.6(initgroups+0x63)[0x7fbaee3c96f3]
    /usr/sbin/mysqld[0x54ba3e]
    /usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x854)[0x551814]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7fbaee33eead]
    /usr/sbin/mysqld[0x54776d]
    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.

    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.


I confirm nscd workaround the problem but it is not a solution for me as nscd
causing others issues elsewhere.

@almighty debian maintainer  : could you please investigate.

Cdt, Aurélien

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20140310/da516c2b/attachment.html>