<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi there,<br>
<br>
Same problem here as well.<br>
debian 7 amd64 fully updated !<br>
msql 5.5 + libnss-mysql-bg --> mysql crash when starting.<br>
<br>
i testes by replacing mysql 5.5 with percona : same issue :<br>
<br>
<blockquote><tt>/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</tt><tt><br>
</tt><tt>11:46:45 UTC - mysqld got signal 11 ;</tt><tt><br>
</tt><tt>This could be because you hit a bug. It is also possible
that this binary</tt><tt><br>
</tt><tt>or one of the libraries it was linked against is corrupt,
improperly built,</tt><tt><br>
</tt><tt>or misconfigured. This error can also be caused by
malfunctioning hardware.</tt><tt><br>
</tt><tt>We will try our best to scrape up some info that will
hopefully help</tt><tt><br>
</tt><tt>diagnose the problem, but since we have already crashed,</tt><tt><br>
</tt><tt>something is definitely wrong and this may fail.</tt><tt><br>
</tt><tt>Please help us make Percona Server better by reporting
any</tt><tt><br>
</tt><tt>bugs at <a class="moz-txt-link-freetext" href="http://bugs.percona.com/">http://bugs.percona.com/</a></tt><tt><br>
</tt><tt><br>
</tt><tt>key_buffer_size=0</tt><tt><br>
</tt><tt>read_buffer_size=131072</tt><tt><br>
</tt><tt>max_used_connections=0</tt><tt><br>
</tt><tt>max_threads=152</tt><tt><br>
</tt><tt>thread_count=0</tt><tt><br>
</tt><tt>connection_count=0</tt><tt><br>
</tt><tt>It is possible that mysqld could use up to</tt><tt><br>
</tt><tt>key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads = 332624 K bytes of memory</tt><tt><br>
</tt><tt>Hope that's ok; if not, decrease some variables in the
equation.</tt><tt><br>
</tt><tt><br>
</tt><tt>Thread pointer: 0x0</tt><tt><br>
</tt><tt>Attempting backtrace. You can use the following
information to find out</tt><tt><br>
</tt><tt>where mysqld died. If you see no messages after this,
something went</tt><tt><br>
</tt><tt>terribly wrong...</tt><tt><br>
</tt><tt>stack_bottom = 0 thread_stack 0x30000</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7d0cce]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x6b8641]</tt><tt><br>
</tt><tt>/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7fbaef7d8030]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(thd_increment_bytes_received+0x1a)[0x59ac1a]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld[0x552e35]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(my_net_read+0x179)[0x5538f9]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(cli_safe_read+0x2a)[0x69a96a]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(mysql_real_connect+0x2ee)[0x69cc2e]</tt><tt><br>
</tt><tt>/usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x2bc5)[0x7fbaecab3bc5]</tt><tt><br>
</tt><tt>/usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x2f5c)[0x7fbaecab3f5c]</tt><tt><br>
</tt><tt>/usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(+0x324e)[0x7fbaecab424e]</tt><tt><br>
</tt><tt>/usr/lib/x86_64-linux-gnu/libnss_mysql.so.2(_nss_mysql_initgroups_dyn+0xa1)[0x7fbaecab4bf1]</tt><tt><br>
</tt><tt>/lib/x86_64-linux-gnu/libc.so.6(+0xa94e2)[0x7fbaee3c94e2]</tt><tt><br>
</tt><tt>/lib/x86_64-linux-gnu/libc.so.6(initgroups+0x63)[0x7fbaee3c96f3]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld[0x54ba3e]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x854)[0x551814]</tt><tt><br>
</tt><tt>/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7fbaee33eead]</tt><tt><br>
</tt><tt>/usr/sbin/mysqld[0x54776d]</tt><tt><br>
</tt><tt>You may download the Percona Server operations manual by
visiting</tt><tt><br>
</tt><tt><a class="moz-txt-link-freetext" href="http://www.percona.com/software/percona-server/">http://www.percona.com/software/percona-server/</a>. You may
find information</tt><tt><br>
</tt><tt>in the manual which will help you identify the cause of
the crash.</tt><tt><br>
</tt><tt><br>
</tt><tt>This crash occured while the server was calling
initgroups(). This is</tt><tt><br>
</tt><tt>often due to the use of a mysqld that is statically
linked against</tt><tt><br>
</tt><tt>glibc and configured to use LDAP in /etc/nsswitch.conf.</tt><tt><br>
</tt><tt>You will need to either upgrade to a version of glibc
that does not</tt><tt><br>
</tt><tt>have this problem (2.3.4 or later when used with nscd),</tt><tt><br>
</tt><tt>disable LDAP in your nsswitch.conf, or use a mysqld that
is not statically linked.</tt><tt><br>
</tt></blockquote>
<br>
I confirm nscd workaround the problem but it is not a solution for
me as nscd causing others issues elsewhere. <br>
<br>
@almighty debian maintainer : could you please investigate.<br>
<br>
Cdt, Aurélien<br>
<br>
</body>
</html>