MySQL 5.0.22 Crash on Ubuntu 6.06.2 LTS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mysql-dfsg-5.0 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Dapper |
Invalid
|
Medium
|
Unassigned |
Bug Description
System info:
root@cmdb:~# dpkg -l mysql-server-5.0
ii mysql-server-5.0 5.0.22-
root@cmdb:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 6.06.2 LTS
Release: 6.06
Codename: dapper
Using the following query triger the crash on the dapper 6.06.2 machine:
Result from MySQL 5.0.22 (Ubuntu)
root@localhost:
ERROR 2013 (HY000): Lost connection to MySQL server during query
root@localhost:
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 1
Current database: *** NONE ***
+------
| User |
+------
| debian-sys-maint |
| root |
+------
5 rows in set (0.00 sec)
However, the issue does not exist in Debian:
Result from MySQL 5.0.81 (Debian)
root@localhost:
ERROR 1054 (42S22): Unknown column 'mu.user' in 'order clause'
More debug info:
Jun 23 16:09:57 cmdb mysqld[21409]: mysqld got signal 11;
Jun 23 16:09:57 cmdb mysqld[21409]: This could be because you hit a bug. It is also possible that this binary
Jun 23 16:09:57 cmdb mysqld[21409]: or one of the libraries it was linked against is corrupt, improperly built,
Jun 23 16:09:57 cmdb mysqld[21409]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jun 23 16:09:57 cmdb mysqld[21409]: We will try our best to scrape up some info that will hopefully help diagnose
Jun 23 16:09:57 cmdb mysqld[21409]: the problem, but since we have already crashed, something is definitely wrong
Jun 23 16:09:57 cmdb mysqld[21409]: and this may fail.
Jun 23 16:09:57 cmdb mysqld[21409]:
Jun 23 16:09:57 cmdb mysqld[21409]: key_buffer_
Jun 23 16:09:57 cmdb mysqld[21409]: read_buffer_
Jun 23 16:09:57 cmdb mysqld[21409]: max_used_
Jun 23 16:09:57 cmdb mysqld[21409]: max_connections=100
Jun 23 16:09:57 cmdb mysqld[21409]: threads_connected=1
Jun 23 16:09:57 cmdb mysqld[21409]: It is possible that mysqld could use up to
Jun 23 16:09:57 cmdb mysqld[21409]: key_buffer_size + (read_buffer_size + sort_buffer_
Jun 23 16:09:57 cmdb mysqld[21409]: bytes of memory
Jun 23 16:09:57 cmdb mysqld[21409]: Hope that's ok; if not, decrease some variables in the equation.
Jun 23 16:09:57 cmdb mysqld[21409]:
Jun 23 16:09:57 cmdb mysqld[21409]: thd=0x8b0e230
Jun 23 16:09:57 cmdb mysqld[21409]: Attempting backtrace. You can use the following information to find out
Jun 23 16:09:57 cmdb mysqld[21409]: where mysqld died. If you see no messages after this, something went
Jun 23 16:09:57 cmdb mysqld[21409]: terribly wrong...
Jun 23 16:09:57 cmdb mysqld[21409]: Cannot determine thread, fp=0xb1037d48, backtrace may not be correct.
Jun 23 16:09:57 cmdb mysqld[21409]: Stack range sanity check OK, backtrace follows:
Jun 23 16:09:57 cmdb mysqld[21409]: 0x818a089
Jun 23 16:09:57 cmdb mysqld[21409]: 0xffffe420
Jun 23 16:09:57 cmdb mysqld[21409]: 0x8b9e4f0
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d24e4
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d2877
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81d40cd
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81e6609
Jun 23 16:09:57 cmdb mysqld[21409]: 0x8279856
Jun 23 16:09:57 cmdb mysqld[21409]: 0x827b172
Jun 23 16:09:57 cmdb mysqld[21409]: 0x827afae
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81c2c21
Jun 23 16:09:57 cmdb mysqld[21409]: 0x819d205
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a2ce7
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a32b1
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a43ec
Jun 23 16:09:57 cmdb mysqld[21409]: 0x81a4d98
Jun 23 16:09:57 cmdb mysqld[21409]: 0xb7ed1341
Jun 23 16:09:57 cmdb mysqld[21409]: 0xb7d224ee
Jun 23 16:09:57 cmdb mysqld[21409]: New value of fp=(nil) failed sanity check, terminating stack trace!
Jun 23 16:09:57 cmdb mysqld[21409]: Please read http://
Jun 23 16:09:57 cmdb mysqld[21409]: stack trace is much more helpful in diagnosing the problem, so please do
Jun 23 16:09:57 cmdb mysqld[21409]: resolve it
Jun 23 16:09:57 cmdb mysqld[21409]: Trying to get some variables.
Jun 23 16:09:57 cmdb mysqld[21409]: Some pointers may be invalid and cause the dump to abort...
Jun 23 16:09:57 cmdb mysqld[21409]: thd->query at 0x8b15f40 = SELECT * FROM (SELECT c.cid,sd.
,sd.height-
stid=st.stid LEFT JOIN location l ON c.lid=l.lid WHERE NOT st.name IN('Fased Out') UNION SELECT '0' AS cid,re.type AS hostname,r.name AS rack,l.name AS location,
ht,IF(re.
ERE rid=66 ORDER BY bottom_height
Jun 23 16:09:57 cmdb mysqld[21409]: thd->thread_id=8
Jun 23 16:09:57 cmdb mysqld[21409]: The manual page at http://
Jun 23 16:09:57 cmdb mysqld[21409]: information that should help you find out what is causing the crash.
Jun 23 16:09:57 cmdb mysqld_safe[21530]: Number of processes running now: 0
Jun 23 16:09:57 cmdb mysqld_safe[21532]: restarted
Jun 23 16:09:57 cmdb mysqld[21535]: 090623 16:09:57 InnoDB: Started; log sequence number 0 43655
Jun 23 16:09:57 cmdb mysqld[21535]: 090623 16:09:57 [Note] Recovering after a crash using /var/log/
Jun 23 16:09:57 cmdb mysqld[21535]: 090623 16:09:57 [Note] Starting crash recovery...
Jun 23 16:09:57 cmdb mysqld[21535]: 090623 16:09:57 [Note] Crash recovery finished.
Jun 23 16:09:57 cmdb mysqld[21535]: 090623 16:09:57 [Note] /usr/sbin/mysqld: ready for connections.
Jun 23 16:09:57 cmdb mysqld[21535]: Version: '5.0.22-
root@cmdb:~# zcat /usr/share/
root@cmdb:~# resolve_stack_dump -s ./mysqld.sym mysql.stacktrace2
0x818a089 handle_segfault + 639
0xffffe420 _end + -140740944
0x8b9e4f0 _end + 5666688
0x81d24e4 _Z18find_
0x81d2877 _Z11setup_
0x81d40cd _ZN4JOIN7prepar
0x81e6609 _Z12mysql_
0x8279856 _ZN18st_
0x827b172 _Z21mysql_
0x827afae _Z20mysql_
0x81c2c21 _Z20open_
0x819d205 _Z21mysql_
0x81a2ce7 _Z11mysql_
0x81a32b1 _Z16dispatch_
0x81a43ec _Z10do_commandP3THD + 134
0x81a4d98 handle_
0xb7ed1341 _end + -1349933615
0xb7d224ee _end + -1351698562
Hi,
On Thu, Jun 25, 2009 at 06:15:29PM -0000, Shang Wu wrote: (none)> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION SELECT mu.user FROM mysql.user mu ORDER BY mu.user) a; (none)> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION SELECT mu.user FROM mysql.user mu) a;
>
> Using the following query triger the crash on the dapper 6.06.2 machine:
> Result from MySQL 5.0.22 (Ubuntu)
> root@localhost:
> ERROR 2013 (HY000): Lost connection to MySQL server during query
> root@localhost:
> ERROR 2006 (HY000): MySQL server has gone away
> No connection. Trying to reconnect...
> Jun 23 16:09:57 cmdb mysqld[21409]: thd->query at 0x8b15f40 = SELECT * FROM (SELECT c.cid,sd. hostname, r.name AS rack,l.name AS location, r.rid,sd. height AS top_height,m.height AS height, IF(m.height< sd.height m.height, '0') AS bottom_ height, st.name AS status FROM chassis c LEFT JOIN serverdetail sd ON sd.sid=c.sid LEFT JOIN rack r ON c.rid=r.rid LEFT JOIN model m ON m.mid=c.mid LEFT JOIN status st ON c. r.rid,re. start AS top_height, re.height AS heig height< re.start, re.start- re.height, '0') AS bottom_height,'N/A' AS status FROM rackextras re LEFT JOIN rack r ON r.rid=re.rid LEFT JOIN location l ON l.lid=r.lid ORDER BY r.rid,re. bottom_ height) a WH
> ,sd.height-
> stid=st.stid LEFT JOIN location l ON c.lid=l.lid WHERE NOT st.name IN('Fased Out') UNION SELECT '0' AS cid,re.type AS hostname,r.name AS rack,l.name AS location,
> ht,IF(re.
> ERE rid=66 ORDER BY bottom_height
These two queries don't look the same - or the log files don't
correspond. Could specify which query causes the bug? If the latter,
please attach a dump of the sql database to be able to reproduce it.
status incomplete
-- www.ubuntu. com
Mathias Gug
Ubuntu Developer http://