Your message dated Wed, 29 Sep 2010 12:29:17 +0200
with message-id <[email protected]>
and subject line #585477 is not RC as it is ~bpo
has caused the Debian Bug report #585477,
regarding mysql-server-5.1: mysqld can't start [initgroups()] with libnss-mysql
enabled
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
585477: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585477
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-5.1
Version: 5.1.47-1~bpo50+1
Severity: grave
Justification: renders package unusable
After upgrade from 5.1.45-1~bpo50+1, the mysqld server can't start when
libnss-mysql (currently 1.5-1
installed) is enabled on /etc/nsswitch.conf. Before the upgrade, the server
started just fine. The 5.1.47
can be started by disabling mysql in /etc/nsswitch.conf.
Failing nsswitch.conf:
passwd: compat mysql
group: compat mysql
shadow: compat mysql
Starting OK nsswitch.conf:
passwd: compat
group: compat
shadow: compat
mysql log :
Jun 10 15:46:14 herodes mysqld_safe: Starting mysqld daemon with databases from
/var/lib/mysql
Jun 10 15:46:14 herodes mysqld: 100610 15:46:14 - mysqld got signal 11 ;
Jun 10 15:46:14 herodes mysqld: This could be because you hit a bug. It is also
possible that this binary
Jun 10 15:46:14 herodes mysqld: or one of the libraries it was linked against
is corrupt, improperly built,
Jun 10 15:46:14 herodes mysqld: or misconfigured. This error can also be caused
by malfunctioning hardware.
Jun 10 15:46:14 herodes mysqld: We will try our best to scrape up some info
that will hopefully help
diagnose
Jun 10 15:46:14 herodes mysqld: the problem, but since we have already crashed,
something is definitely
wrong
Jun 10 15:46:14 herodes mysqld: and this may fail.
Jun 10 15:46:14 herodes mysqld:
Jun 10 15:46:14 herodes mysqld: key_buffer_size=0
Jun 10 15:46:14 herodes mysqld: read_buffer_size=131072
Jun 10 15:46:14 herodes mysqld: max_used_connections=0
Jun 10 15:46:14 herodes mysqld: max_threads=2000
Jun 10 15:46:14 herodes mysqld: threads_connected=0
Jun 10 15:46:14 herodes mysqld: It is possible that mysqld could use up to
Jun 10 15:46:14 herodes mysqld: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_threads =
4372593 K
Jun 10 15:46:14 herodes mysqld: bytes of memory
Jun 10 15:46:14 herodes mysqld: Hope that's ok; if not, decrease some variables
in the equation.
Jun 10 15:46:14 herodes mysqld:
Jun 10 15:46:14 herodes mysqld: thd: 0x0
Jun 10 15:46:14 herodes mysqld: Attempting backtrace. You can use the following
information to find out
Jun 10 15:46:14 herodes mysqld: where mysqld died. If you see no messages after
this, something went
Jun 10 15:46:14 herodes mysqld: terribly wrong...
Jun 10 15:46:14 herodes mysqld: stack_bottom = (nil) thread_stack 0x30000
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29)
[0x7fe93adee0b9]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(handle_segfault+0x36a)
[0x7fe93ab0294a]
Jun 10 15:46:14 herodes mysqld: /lib/libpthread.so.0 [0x7fe93a365a80]
Jun 10 15:46:14 herodes mysqld:
/usr/sbin/mysqld(thd_increment_bytes_received+0x12) [0x7fe93aaebd72]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld [0x7fe93aaf5d7f]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(my_net_read+0x195)
[0x7fe93aaf6395]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(cli_safe_read+0x2a)
[0x7fe93ac9246a]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(mysql_real_connect+0x1c2)
[0x7fe93ac930b2]
Jun 10 15:46:14 herodes mysqld: /lib/libnss_mysql.so.2 [0x7fe93a64eb05]
Jun 10 15:46:14 herodes mysqld: /lib/libnss_mysql.so.2 [0x7fe93a64eefc]
Jun 10 15:46:14 herodes mysqld: /lib/libnss_mysql.so.2 [0x7fe93a64f1e4]
Jun 10 15:46:14 herodes mysqld:
/lib/libnss_mysql.so.2(_nss_mysql_initgroups_dyn+0xa2) [0x7fe93a64fa52]
Jun 10 15:46:14 herodes mysqld: /lib/libc.so.6 [0x7fe938e85c3c]
Jun 10 15:46:14 herodes mysqld: /lib/libc.so.6(initgroups+0x6c) [0x7fe938e85e1c]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld [0x7fe93ab044d3]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld(main+0x1d5) [0x7fe93ab07ba5]
Jun 10 15:46:14 herodes mysqld: /lib/libc.so.6(__libc_start_main+0xe6)
[0x7fe938e091a6]
Jun 10 15:46:14 herodes mysqld: /usr/sbin/mysqld [0x7fe93aa2c469]
Jun 10 15:46:14 herodes mysqld: The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
Jun 10 15:46:14 herodes mysqld: information that should help you find out what
is causing the crash.
Jun 10 15:46:14 herodes mysqld:
Jun 10 15:46:14 herodes mysqld: This crash occured while the server was calling
initgroups(). This is
Jun 10 15:46:14 herodes mysqld: often due to the use of a mysqld that is
statically linked against glibc
Jun 10 15:46:14 herodes mysqld: and configured to use LDAP in
/etc/nsswitch.conf. You will need to either
Jun 10 15:46:14 herodes mysqld: upgrade to a version of glibc that does not
have this problem (2.3.4 or
Jun 10 15:46:14 herodes mysqld: later when used with nscd), disable LDAP in
your nsswitch.conf, or use a
Jun 10 15:46:14 herodes mysqld: mysqld that is not statically linked.
Jun 10 15:46:14 herodes mysqld_safe: mysqld from pid file
/var/run/mysqld/mysqld.pid ended
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-bpo.3-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_CL, LC_CTYPE=es_CL (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages mysql-server-5.1 depends on:
ii adduser 3.110 add and remove users and groups
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii libc6 2.7-18lenny4 GNU C Library: Shared libraries
ii libdbi-perl 1.605-1 Perl5 database interface by Tim Bu
ii libgcc1 1:4.3.4-6~bpo50+1 GCC support library
ii libmysqlclient16 5.1.47-1~bpo50+1 MySQL database client library
ii libstdc++6 4.3.4-6~bpo50+1 The GNU Standard C++ Library v3
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii mysql-client-5.1 5.1.47-1~bpo50+1 MySQL database client binaries
ii mysql-common 5.1.47-1~bpo50+1 MySQL database common files, e.g.
ii mysql-server-core-5.1 5.1.47-1~bpo50+1 MySQL database server binaries
ii passwd 1:4.1.1-6+lenny1 change and administer password and
ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction
ii psmisc 22.6-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
Versions of packages mysql-server-5.1 recommends:
ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-3 A simple mail user agent
ii libhtml-template-p 2.9-1 HTML::Template : A module for usin
Versions of packages mysql-server-5.1 suggests:
pn tinyca <none> (no description available)
-- debconf information:
mysql-server/error_setting_password:
mysql-server-5.1/start_on_boot: true
mysql-server-5.1/postrm_remove_databases: false
mysql-server-5.1/nis_warning:
mysql-server-5.1/really_downgrade: false
mysql-server/password_mismatch:
mysql-server/no_upgrade_when_using_ndb:
--- End Message ---
--- Begin Message ---
Version: 5.1.49-1
Hi,
I am hereby closing bug #585477 as it affects a backported package. As
mentionned in the rules for backports, those bugs should not be reported in the
BTS.
Please reopen with correct versioning if this bug is reproducible on the
Squeeze/Sid package.
Cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
[email protected]
--- End Message ---
