Package: mysql-server-5.0
Version: 5.0.32-3
Followup-For: Bug #407597
Since several days my webserver crashes, giving error messages about lost
contact with mysql server.
Pinpointing the problem revealed that a specific SQL query caused the server to
be killed.
The query (on a joomla webserver database) was:
SELECT menutype, COUNT(id) AS numitems FROM jos_menu WHERE published = 1
GROUP BY menutype;
Executing this query from the mysql client commandline gives the following
error message:
ERROR 2013 (HY000): Lost connection to MySQL server during query
This error gets logged in /var/log/daemon.log as:
Feb 11 18:59:37 meter mysqld[10667]: mysqld got signal 11;
Feb 11 18:59:37 meter mysqld[10667]: This could be because you hit a bug.
It is also possible that this binary
Feb 11 18:59:37 meter mysqld[10667]: or one of the libraries it was linked
against is corrupt, improperly built,
Feb 11 18:59:37 meter mysqld[10667]: or misconfigured. This error can also
be caused by malfunctioning hardware.
Feb 11 18:59:37 meter mysqld[10667]: We will try our best to scrape up some
info that will hopefully help diagnose
Feb 11 18:59:37 meter mysqld[10667]: the problem, but since we have already
crashed, something is definitely wrong
Feb 11 18:59:37 meter mysqld[10667]: and this may fail.
Feb 11 18:59:37 meter mysqld[10667]:
Feb 11 18:59:37 meter mysqld[10667]: key_buffer_size=16777216
Feb 11 18:59:37 meter mysqld[10667]: read_buffer_size=131072
Feb 11 18:59:37 meter mysqld[10667]: max_used_connections=1
Feb 11 18:59:37 meter mysqld[10667]: max_connections=100
Feb 11 18:59:37 meter mysqld[10667]: threads_connected=1
Feb 11 18:59:37 meter mysqld[10667]: It is possible that mysqld could use
up to
Feb 11 18:59:37 meter mysqld[10667]: key_buffer_size + (read_buffer_size +
sort_buffer_size)*max_connections = 233983 K
Feb 11 18:59:37 meter mysqld[10667]: bytes of memory
Feb 11 18:59:37 meter mysqld[10667]: Hope that's ok; if not, decrease some
variables in the equation.
Feb 11 18:59:37 meter mysqld[10667]:
Feb 11 18:59:40 meter mysqld_safe[10959]: Number of processes running now: 0
Feb 11 18:59:40 meter mysqld_safe[10961]: restarted
Feb 11 18:59:45 meter mysqld[10964]: 070211 18:59:45 InnoDB: Database was
not shut down normally!
Feb 11 18:59:45 meter mysqld[10964]: InnoDB: Starting crash recovery.
Feb 11 18:59:45 meter mysqld[10964]: InnoDB: Reading tablespace information
from the .ibd files...
Feb 11 18:59:45 meter mysqld[10964]: InnoDB: Restoring possible
half-written data pages from the doublewrite
Feb 11 18:59:45 meter mysqld[10964]: InnoDB: buffer...
Feb 11 18:59:46 meter mysqld[10964]: 070211 18:59:46 InnoDB: Starting log
scan based on checkpoint at
Feb 11 18:59:46 meter mysqld[10964]: InnoDB: log sequence number 0 43675.
Feb 11 18:59:46 meter mysqld[10964]: InnoDB: Doing recovery: scanned up to
log sequence number 0 43675
Feb 11 18:59:47 meter mysqld[10964]: 070211 18:59:47 InnoDB: Started; log
sequence number 0 43675
Feb 11 18:59:47 meter mysqld[10964]: 070211 18:59:47 [Note] Recovering
after a crash using /var/log/mysql/mysql-bin
Feb 11 18:59:47 meter mysqld[10964]: 070211 18:59:47 [Note] Starting crash
recovery...
Feb 11 18:59:47 meter mysqld[10964]: 070211 18:59:47 [Note] Crash recovery
finished.
Feb 11 18:59:48 meter mysqld[10964]: 070211 18:59:48 [Note]
/usr/sbin/mysqld: ready for connections.
Feb 11 18:59:48 meter mysqld[10964]: Version: '5.0.32-Debian_3-log'
socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
If the query is reduced to "select menutype, id from jos_menu where published =
1;", the query succeeds and returns 11 rows from the table:
+----------+----+
| menutype | id |
+----------+----+
| mainmenu | 1 |
| mainmenu | 3 |
| mainmenu | 32 |
| mainmenu | 24 |
| usermenu | 21 |
| usermenu | 16 |
| mainmenu | 27 |
| usermenu | 28 |
| usermenu | 30 |
| usermenu | 33 |
| usermenu | 34 |
+----------+----+
As a personal fix, I transferred the mysql database to a i386 server, (also
running the latest Etch updates). This works OK.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm (armv5tel)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-ixp4xx
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages mysql-server-5.0 depends on:
ii adduser 3.102 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries
ii libdbi-perl 1.53-1 Perl5 database interface by Tim Bu
ii libgcc1 1:4.1.1-21 GCC support library
ii libmysqlclient15off 5.0.32-3 mysql database client library
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libreadline5 5.2-2 GNU readline and history libraries
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-12 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip
ii mysql-client-5.0 5.0.32-3 mysql database client binaries
ii mysql-common 5.0.32-3 mysql database common files (e.g.
ii passwd 1:4.0.18.1-6 change and administer password and
ii perl 5.8.8-7 Larry Wall's Practical Extraction
ii psmisc 22.3-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages mysql-server-5.0 recommends:
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
-- debconf information:
mysql-server-5.0/really_downgrade: false
mysql-server-5.0/need_sarge_compat: false
mysql-server-5.0/start_on_boot: true
mysql-server/error_setting_password:
mysql-server-5.0/nis_warning:
mysql-server-5.0/postrm_remove_databases: false
mysql-server-5.0/need_sarge_compat_done: true
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
