[debian-mysql] Bug#585392: mysql-server: MySQL Server segfaults after upgrade

Andreas Gohr andi at splitbrain.org
Thu Jun 10 08:02:00 UTC 2010


Package: mysql-server
Version: 5.0.51a-24+lenny4
Severity: grave
Justification: renders package unusable


After upgrading from 5.0.51a-24+lenny3 to 5.0.51a-24+lenny4 the server
started to segfault. Downgrading to lenny3 solved the problem for me.

>From the syslog:

Jun 10 09:46:06 gir mysqld[25223]: 100610  9:46:06  InnoDB: Started; log
sequence number 0 43655
Jun 10 09:46:06 gir mysqld[25223]: 100610  9:46:06 [Note]
/usr/sbin/mysqld: ready for connections.
Jun 10 09:46:06 gir mysqld[25223]: Version: '5.0.51a-24+lenny4'  socket:
'/var/run/mysqld/mysqld.sock'  port: 3306  (Debian
)
Jun 10 09:46:06 gir mysqld[25223]: 100610  9:46:06 - mysqld got signal
11;
Jun 10 09:46:06 gir mysqld[25223]: This could be because you hit a bug.
It is also possible that this binary
Jun 10 09:46:06 gir mysqld[25223]: or one of the libraries it was linked
against is corrupt, improperly built,
Jun 10 09:46:06 gir mysqld[25223]: or misconfigured. This error can also
be caused by malfunctioning hardware.
Jun 10 09:46:06 gir mysqld[25223]: We will try our best to scrape up
some info that will hopefully help diagnose
Jun 10 09:46:06 gir mysqld[25223]: the problem, but since we have
already crashed, something is definitely wrong
Jun 10 09:46:06 gir mysqld[25223]: and this may fail.
Jun 10 09:46:06 gir mysqld[25223]: 
Jun 10 09:46:06 gir mysqld[25223]: key_buffer_size=16777216
Jun 10 09:46:06 gir mysqld[25223]: read_buffer_size=131072
Jun 10 09:46:06 gir mysqld[25223]: max_used_connections=1
Jun 10 09:46:06 gir mysqld[25223]: max_connections=100
Jun 10 09:46:06 gir mysqld[25223]: threads_connected=1
Jun 10 09:46:06 gir mysqld[25223]: It is possible that mysqld could use
up to 
Jun 10 09:46:06 gir mysqld[25223]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 233983 K
Jun 10 09:46:06 gir mysqld[25223]: bytes of memory
Jun 10 09:46:06 gir mysqld[25223]: Hope that's ok; if not, decrease some
variables in the equation.
Jun 10 09:46:06 gir mysqld[25223]: 
Jun 10 09:46:06 gir mysqld[25223]: thd=0x2344020
Jun 10 09:46:06 gir mysqld[25223]: Attempting backtrace. You can use the
following information to find out
Jun 10 09:46:06 gir mysqld[25223]: where mysqld died. If you see no
messages after this, something went
Jun 10 09:46:06 gir mysqld[25223]: terribly wrong...
Jun 10 09:46:06 gir mysqld[25223]: Cannot determine thread,
fp=0x2344020, backtrace may not be correct.
Jun 10 09:46:06 gir mysqld[25223]: Bogus stack limit or frame pointer,
fp=0x2344020, stack_bottom=0x44050000, thread_stack=
131072, aborting backtrace.
Jun 10 09:46:06 gir mysqld[25223]: Trying to get some variables.
Jun 10 09:46:06 gir mysqld[25223]: Some pointers may be invalid and
cause the dump to abort...
Jun 10 09:46:06 gir mysqld[25223]: thd->query at (nil)  is invalid
pointer
Jun 10 09:46:06 gir mysqld[25223]: thd->thread_id=1
Jun 10 09:46:06 gir mysqld[25223]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Jun 10 09:46:06 gir mysqld[25223]: information that should help you find
out what is causing the crash.


-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages mysql-server depends on:
ii  mysql-server-5.0       5.0.51a-24+lenny3 MySQL database server binaries

mysql-server recommends no packages.

mysql-server suggests no packages.

-- no debconf information





More information about the pkg-mysql-maint mailing list