Your message dated Fri, 23 Mar 2007 01:56:21 +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
Version: 5.0.32-6
Severity: important
architecture : arm
debian-version : sid
Everything worked fine until the last upgrade (today).
The mysqld server crashes when certain queries are performed on the
database (most queries except very simple queries with few lines/columns).
It seems that the "group by" command generates a crash.
mysql> SELECT * FROM phpwebgallery_categories;
shows 70 lines
mysql> SELECT * FROM phpwebgallery_categories GROUP BY id_uppercat;
ERROR 2013 (HY000): Lost connection to MySQL server during query
phpwebgallery_categories is a table and not a view.
It looks like this bug :
http://bugs.mysql.com/bug.php?id=25172
Patch seems to be included in 5.0.36
I tried to downgrade to 5.0.32-5, but I had the same pb (which is normal
if it corresponds to the bug I found on mysql website, as it is
present from 5.0.30)
I tried to downgrade to 4.1_4.1.11a but I faced too many dependencies pb.
I have only 32Mo of memory, and I tried to adjust parameters to fit with
that but I still have the pb.
Anyway, I had no problems with my settings with the previous version of
mysql.
Here is a sample of syslog between the last restart and the crash :
Feb 18 22:57:45 localhost mysqld_safe[27179]: started
Feb 18 22:57:48 localhost mysqld[27182]: 070218 22:57:48 InnoDB:
Started; log sequence number 0 43675
Feb 18 22:57:49 localhost mysqld[27182]: 070218 22:57:49 [Note]
/usr/sbin/mysqld: ready for connections.
Feb 18 22:57:49 localhost mysqld[27182]: Version: '5.0.32-Debian_6-log'
socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch
distribution
Feb 18 22:57:53 localhost /etc/mysql/debian-start[27238]: Upgrading
MySQL tables if necessary.
Feb 18 22:57:56 localhost /etc/mysql/debian-start[27246]: Checking for
crashed MySQL tables.
Feb 18 22:58:25 localhost mysqld[27182]: mysqld got signal 11;
Feb 18 22:58:25 localhost mysqld[27182]: This could be because you hit a
bug. It is also possible that this binary
Feb 18 22:58:25 localhost mysqld[27182]: or one of the libraries it was
linked against is corrupt, improperly built,
Feb 18 22:58:25 localhost mysqld[27182]: or misconfigured. This error
can also be caused by malfunctioning hardware.
Feb 18 22:58:25 localhost mysqld[27182]: We will try our best to scrape
up some info that will hopefully help diagnose
Feb 18 22:58:25 localhost mysqld[27182]: the problem, but since we have
already crashed, something is definitely wrong
Feb 18 22:58:25 localhost mysqld[27182]: and this may fail.
Feb 18 22:58:25 localhost mysqld[27182]:
Feb 18 22:58:25 localhost mysqld[27182]: key_buffer_size=4194304
Feb 18 22:58:25 localhost mysqld[27182]: read_buffer_size=1044480
Feb 18 22:58:25 localhost mysqld[27182]: max_used_connections=2
Feb 18 22:58:25 localhost mysqld[27182]: max_connections=3
Feb 18 22:58:25 localhost mysqld[27182]: threads_connected=1
Feb 18 22:58:25 localhost mysqld[27182]: It is possible that mysqld
could use up to
Feb 18 22:58:25 localhost mysqld[27182]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 10227 K
Feb 18 22:58:25 localhost mysqld[27182]: bytes of memory
Feb 18 22:58:25 localhost mysqld[27182]: Hope that's ok; if not,
decrease some variables in the equation.
Feb 18 22:58:25 localhost mysqld[27182]:
Feb 18 22:58:25 localhost mysqld_safe[27258]: Number of processes
running now: 0
Feb 18 22:58:25 localhost mysqld_safe[27260]: restarted
Feb 18 22:58:27 localhost mysqld[27263]: 070218 22:58:27 InnoDB:
Started; log sequence number 0 43675
Feb 18 22:58:27 localhost mysqld[27263]: 070218 22:58:27 [Note]
Recovering after a crash using /var/log/mysql/mysql-bin
Feb 18 22:58:27 localhost mysqld[27263]: 070218 22:58:27 [Note] Starting
crash recovery...
Feb 18 22:58:27 localhost mysqld[27263]: 070218 22:58:27 [Note] Crash
recovery finished.
Feb 18 22:58:27 localhost mysqld[27263]: 070218 22:58:27 [Note]
/usr/sbin/mysqld: ready for connections.
Feb 18 22:58:27 localhost mysqld[27263]: Version: '5.0.32-Debian_6-log'
socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch
distribution
Regards
Martin Riondet
--- End Message ---
--- Begin Message ---
This bug is supposed to be fixed in 5.0.32 according to MySQL.
bye,
-christian-
--- End Message ---
