Your message dated Fri, 23 Mar 2007 02:06:38 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: mysql-server-5.0
Version: 5.0.18-9
Severity: normal


The following problem is reproducable.

mysql> flush logs;
ERROR 2013 (HY000): Lost connection to MySQL server during query

In syslog:

Mar 30 09:16:58 druifje mysqld[10664]: mysqld got signal 11;
Mar 30 09:16:58 druifje mysqld[10664]: This could be because you hit a bug. It 
is also possible that this binary
Mar 30 09:16:58 druifje mysqld[10664]: or one of the libraries it was linked 
against is corrupt, improperly built,
Mar 30 09:16:58 druifje mysqld[10664]: or misconfigured. This error can also be 
caused by malfunctioning hardware.
Mar 30 09:16:58 druifje mysqld[10664]: We will try our best to scrape up some 
info that will hopefully help diagnose
Mar 30 09:16:58 druifje mysqld[10664]: the problem, but since we have already 
crashed, something is definitely wrong
Mar 30 09:16:58 druifje mysqld[10664]: and this may fail.
Mar 30 09:16:58 druifje mysqld[10664]:
Mar 30 09:16:58 druifje mysqld[10664]: key_buffer_size=16777216
Mar 30 09:16:58 druifje mysqld[10664]: read_buffer_size=131072
Mar 30 09:16:58 druifje mysqld[10664]: max_used_connections=1
Mar 30 09:16:58 druifje mysqld[10664]: max_connections=100
Mar 30 09:16:58 druifje mysqld[10664]: threads_connected=1
Mar 30 09:16:58 druifje mysqld[10664]: It is possible that mysqld could use up 
to
Mar 30 09:16:58 druifje mysqld[10664]: key_buffer_size + (read_buffer_size + 
sort_buffer_size)*max_connections = 233983 K
Mar 30 09:16:58 druifje mysqld[10664]: bytes of memory
Mar 30 09:16:58 druifje mysqld[10664]: Hope that's ok; if not, decrease some 
variables in the equation.
Mar 30 09:16:58 druifje mysqld[10664]:
Mar 30 09:16:58 druifje mysqld[10664]: thd=0x8b06db0
Mar 30 09:16:58 druifje mysqld[10664]: Attempting backtrace. You can use the 
following information to find out
Mar 30 09:16:58 druifje mysqld[10664]: where mysqld died. If you see no 
messages after this, something went
Mar 30 09:16:58 druifje mysqld[10664]: terribly wrong...
Mar 30 09:16:58 druifje mysqld[10664]: Cannot determine thread, fp=0xb0d3775c, 
backtrace may not be correct.
Mar 30 09:16:58 druifje mysqld[10664]: Stack range sanity check OK, backtrace 
follows:
Mar 30 09:16:58 druifje mysqld[10664]: 0x818f37c
Mar 30 09:16:58 druifje mysqld[10664]: 0xffffe420
Mar 30 09:16:58 druifje mysqld[10664]: 0x863bfc4
Mar 30 09:16:58 druifje mysqld[10664]: 0x82019ac
Mar 30 09:16:58 druifje mysqld[10664]: 0x8202b47
Mar 30 09:16:58 druifje mysqld[10664]: 0x819f627
Mar 30 09:16:58 druifje mysqld[10664]: 0x81a9257
Mar 30 09:16:58 druifje mysqld[10664]: 0x81a9fd8
Mar 30 09:16:58 druifje mysqld[10664]: 0x81aa924
Mar 30 09:16:58 druifje mysqld[10664]: 0xb7facced
Mar 30 09:16:58 druifje mysqld[10664]: 0xb7deddde
Mar 30 09:16:58 druifje mysqld[10664]: New value of fp=(nil) failed sanity 
check, terminating stack trace!
Mar 30 09:16:58 druifje mysqld[10664]: Please read 
http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow 
instructions on how to resolve the stack trace. Resolved
Mar 30 09:16:58 druifje mysqld[10664]: stack trace is much more helpful in 
diagnosing the problem, so please do
Mar 30 09:16:58 druifje mysqld[10664]: resolve it
Mar 30 09:16:58 druifje mysqld[10664]: Trying to get some variables.
Mar 30 09:16:58 druifje mysqld[10664]: Some pointers may be invalid and cause 
the dump to abort...
Mar 30 09:16:58 druifje mysqld[10664]: thd->query at (nil)  is invalid pointer
Mar 30 09:16:58 druifje mysqld[10664]: thd->thread_id=5
Mar 30 09:16:58 druifje mysqld[10664]: The manual page at 
http://www.mysql.com/doc/en/Crashing.html contains
Mar 30 09:16:58 druifje mysqld[10664]: information that should help you find 
out what is causing the crash.
Mar 30 09:16:58 druifje mysqld_safe[10717]: Number of processes running now: 0
Mar 30 09:16:58 druifje mysqld_safe[10719]: restarted

Stack trace:

0x818f37c handle_segfault + 668
0xffffe420 _end + -140762576
0x863bfc4 my_fast_mutexattr + 0
0x82019ac _ZN9MYSQL_LOG22purge_logs_before_dateEl + 92
0x8202b47 _ZN9MYSQL_LOG16rotate_and_purgeEj + 199
0x819f627 _Z20reload_acl_and_cacheP3THDmP13st_table_listPb + 471
0x81a9257 _Z16dispatch_command19enum_server_commandP3THDPcj + 2343
0x81a9fd8 _Z10do_commandP3THD + 136
0x81aa924 handle_one_connection + 2100
0xb7facced _end + -1349055747
0xb7deddde _end + -1350886418

The server is hardly used. Recently I turned off binary logging to circumvent 
the binary logging bug as was reported in #341128.

Restarting the server doesn't help.

Thanks for maintaining mysql!

Willem

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.9
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mysql-server-5.0 depends on:
ii  adduser                       3.85       Add and remove users and groups
ii  debconf [debconf-2.0]         1.4.72     Debian configuration management sy
ii  libc6                         2.3.6-3    GNU C Library: Shared libraries an
ii  libdbi-perl                   1.50-2     Perl5 database interface by Tim Bu
ii  libgcc1                       1:4.0.3-1  GCC support library
ii  libmysqlclient15              5.0.18-9   mysql database client library
ii  libncurses5                   5.5-1      Shared libraries for terminal hand
ii  libreadline5                  5.1-6      GNU readline and history libraries
ii  libstdc++6                    4.0.3-1    The GNU Standard C++ Library v3
ii  libwrap0                      7.6.dbs-9  Wietse Venema's TCP wrappers libra
ii  mysql-client-5.0              5.0.18-9   mysql database client binaries
ii  mysql-common                  5.0.18-9   mysql database common files (e.g. 
ii  passwd                        1:4.0.14-9 change and administer password and
ii  perl                          5.8.8-3    Larry Wall's Practical Extraction 
ii  psmisc                        22.2-1     Utilities that use the proc filesy
ii  zlib1g                        1:1.2.3-11 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/start_on_boot: true
  mysql-server-5.0/mysql_update_hints1:
  mysql-server-5.0/nis_warning:
  mysql-server-5.0/postrm_remove_databases: false
  mysql-server-5.0/no_upgrade_with_isam_tables:
* mysql-server-5.0/mysql_install_db_notes:


--- End Message ---
--- Begin Message ---
Version 5.0.32-1

This bug is fixed in 5.0.32 according to MySQL.

bye,

-christian-


--- End Message ---

Reply via email to