Package: mysql-server-4.1 Version: 4.1.11a-4sarge3 Followup-For: Bug #368627
I just upgraded my MySQL to version 4.1.11a-4sarge3 using 'apt-get upgrade'. It now refuses to start, with a stack trace very similar to the original submitter of bug 368627. It has been working fine for months prior to the upgrade. apt-get also upgraded libc6, I don't know if this is relevant, as I've had no issues with any other installed packages. I have tried removing and reinstalling mysql-server-4.1 and related packages such as libmysqlclient14 with no success. I also tried removing and installing the previous version (4.1.11a-4sarge2) but this fails as well. I checked the consistency of the tables (as suggested on the mysql website) using myisamchk but no errors were reported there. Here's the stack trace: May 30 17:37:10 muntfish mysqld_safe[2844]: mysqld got signal 11; May 30 17:37:10 muntfish mysqld_safe[2844]: This could be because you hit a bug. It is also possible that this binary May 30 17:37:10 muntfish mysqld_safe[2844]: or one of the libraries it was linked against is corrupt, improperly built, May 30 17:37:10 muntfish mysqld_safe[2844]: or misconfigured. This error can also be caused by malfunctioning hardware. May 30 17:37:10 muntfish mysqld_safe[2844]: We will try our best to scrape up some info that will hopefully help diagnose May 30 17:37:10 muntfish mysqld_safe[2844]: the problem, but since we have already crashed, something is definitely wrong May 30 17:37:10 muntfish mysqld_safe[2844]: and this may fail. May 30 17:37:10 muntfish mysqld_safe[2844]: May 30 17:37:10 muntfish mysqld_safe[2844]: key_buffer_size=16777216 May 30 17:37:10 muntfish mysqld_safe[2844]: read_buffer_size=131072 May 30 17:37:10 muntfish mysqld_safe[2844]: max_used_connections=0 May 30 17:37:10 muntfish mysqld_safe[2844]: max_connections=100 May 30 17:37:10 muntfish mysqld_safe[2844]: threads_connected=0 May 30 17:37:10 muntfish mysqld_safe[2844]: It is possible that mysqld could use up to May 30 17:37:10 muntfish mysqld_safe[2844]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K May 30 17:37:10 muntfish mysqld_safe[2844]: bytes of memory May 30 17:37:10 muntfish mysqld_safe[2844]: Hope that's ok; if not, decrease some variables in the equation. May 30 17:37:10 muntfish mysqld_safe[2844]: May 30 17:37:10 muntfish mysqld_safe[2844]: thd=(nil) May 30 17:37:10 muntfish mysqld_safe[2844]: Attempting backtrace. You can use the following information to find out May 30 17:37:10 muntfish mysqld_safe[2844]: where mysqld died. If you see no messages after this, something went May 30 17:37:10 muntfish mysqld_safe[2844]: terribly wrong... May 30 17:37:10 muntfish mysqld_safe[2844]: Cannot determine thread, fp=0x422e67d8, backtrace may not be correct. May 30 17:37:10 muntfish mysqld_safe[2844]: Stack range sanity check OK, backtrace follows: May 30 17:37:10 muntfish mysqld_safe[2844]: 0x81893bf May 30 17:37:10 muntfish mysqld_safe[2844]: 0x4004baf8 May 30 17:37:10 muntfish mysqld_safe[2844]: (nil) May 30 17:37:10 muntfish mysqld_safe[2844]: New value of fp=(nil) failed sanity check, terminating stack trace! May 30 17:37:10 muntfish mysqld_safe[2844]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved May 30 17:37:10 muntfish mysqld_safe[2844]: stack trace is much more helpful in diagnosing the problem, so please do May 30 17:37:10 muntfish mysqld_safe[2844]: resolve it May 30 17:37:10 muntfish mysqld_safe[2844]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains May 30 17:37:10 muntfish mysqld_safe[2844]: information that should help you find out what is causing the crash. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.14.3-mb Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages mysql-server-4.1 depends on: ii adduser 3.63 Add and remove users and groups ii debconf 1.4.30.13 Debian configuration management sy ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libdbi-perl 1.46-6 Perl5 database interface by Tim Bu ii libgcc1 1:3.4.3-13 GCC support library ii libmysqlclient14 4.1.11a-4sarge3 mysql database client library ii libncurses5 5.4-4 Shared libraries for terminal hand ii libreadline4 4.3-11 GNU readline and history libraries ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3 ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra di mailx 1:8.1.2-0.20040524cvs-4 A simple mail user agent ii mysql-client-4.1 4.1.11a-4sarge3 mysql database client binaries ii mysql-common-4.1 4.1.11a-4sarge3 mysql database common files (e.g. ii passwd 1:4.0.3-31sarge5 change and administer password and ii perl 5.8.4-8sarge4 Larry Wall's Practical Extraction ii psmisc 21.5-1 Utilities that use the proc filesy ii zlib1g 1:1.2.2-4.sarge.2 compression library - runtime -- debconf information: mysql-server-4.1/start_on_boot: true mysql-server-4.1/postrm_remove_databases: false * mysql-server-4.1/mysql_install_db_notes: mysql-server-4.1/mysql_update_hints1: mysql-server-4.1/nis_warning: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
