| Bug #17156 | mysql server crashes | ||
|---|---|---|---|
| Submitted: | 6 Feb 2006 14:42 | Modified: | 16 Mar 2006 14:47 |
| Reporter: | Zeki TURAN | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.0.18 | OS: | Linux (debian 3.1) |
| Assigned to: | CPU Architecture: | Any | |
[6 Feb 2006 14:42]
Zeki TURAN
[6 Feb 2006 14:58]
Valeriy Kravchuk
Thank you for a problem report. Sorry, but wee need those SELECT statement that lead to the crash to be able to repeat it. Is there anything in your error log besides the stack trace you had resolved?
[6 Feb 2006 16:13]
Zeki TURAN
The sql command which causes this problam is: 060206 17:58:35 mysqld started 060206 17:58:35 InnoDB: Started; log sequence number 0 43655 060206 17:58:35 [Note] /sh_sys/mysql-5.0.18/libexec/mysqld: ready for connections. Version: '5.0.18' socket: '/tmp/mysql.sock' port: 3306 Source distribution mysqld got signal 6; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=2 max_connections=2500 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2234588 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x89bf778 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x5f300e84, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8161c1d 0xffffe420 0x402a1cec 0x401d9005 0x401df657 0x401dfaf2 0x83b1ca0 0x81b6ca4 0x81ac7a7 0x8252e6d 0x81ac8d0 0x81a89b2 0x8175d2c 0x817e610 0x8174493 0x8173fdd 0x81733b2 0x4003fcfd 0x4024a13e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x89cabf0 = SELECT `NICKS`.`NICK`, `USERS_PICS`.`ID`, `USERS_PICS`.`ST`, `USERS_PICS`.`GOSTERIM`, `USERS_PICS`.`GOSTERIMIP`, `USERS_PICS`.`USER_ID`, `USERS_PICS`.`NAME`, `USERS_PICS`.`DESCT`, `USERS_PICS`.`CDATE`, `USERS_PICS`.`ONAYLAYAN`, `USERS_PICS`.`SONISLEM`, `USERS_PICS`.`HIT`, Count(`USERS_PICS_COMMENT`.`PICTURE_ID`) AS `COUNT_COMMENT` FROM `NICKS` Inner Join `USERS_PICS` ON `USERS_PICS`.`USER_ID` = `NICKS`.`USER_ID` Inner Join `USERS_PICS_COMMENT` ON `USERS_PICS`.`ID` = `USERS_PICS_COMMENT`.`PICTURE_ID` WHERE `USERS_PICS`.`ST` = 3 AND `USERS_PICS_COMMENT`.`DATE_CONFIRM` IS NULL GROUP BY `NICKS`.`NICK`, `USERS_PICS`.`ID`, `USERS_PICS`.`ST`, `USERS_PICS`.`GOSTERIM`, `USERS_PICS`.`GOSTERIMIP`, `USERS_PICS`.`USER_ID`, `USERS_PICS`.`NAME`, `USERS_PICS`.`DESCT`, `USERS_PICS`.`CDATE`, `USERS_PICS`.`ONAYLAYAN`, `USERS_PICS`.`SONISLEM`, `USERS_PICS`.`HIT` thd->thread_id=3 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Note: This sql crashed the mysql server two times until now.
[7 Feb 2006 8:45]
Valeriy Kravchuk
Send, please, SHOW CREATE TABLE and SHOW TABLE STATUS results for the tables used in that SELECT: `NICKS`, `USERS_PICS`, and `USERS_PICS_COMMENT`.
[10 Feb 2006 14:07]
Valeriy Kravchuk
Thank you for the additional information. Where had you created your original tables? On MySQL server version 4.x.y or 3.23.x (not 5.0.x) and then just copied them to 5.0.18, right? Please, confirm or deny.
[10 Feb 2006 14:53]
Zeki TURAN
Yes you are right. Original databases created on mysql server version 4.x.y and then I just copied them to 5.0.18.
[16 Feb 2006 14:47]
Valeriy Kravchuk
The only right way to upgrade is with dump in 4.x.y and restore in 5.0.x. You will not get that crash, as you already proved by your tests.
Anyway, I had created the tables like in your private message, in 4.1.19-BK put a few rows of data, then copied to 5.1.19-BK and executed the same query as in your original post. It does not crash:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.19
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> show tables like 'N%';
+---------------------+
| Tables_in_test (N%) |
+---------------------+
| NICKS |
+---------------------+
1 row in set (0.00 sec)
mysql> show tables like 'U%';
+---------------------+
| Tables_in_test (U%) |
+---------------------+
| USERS_PICS |
| USERS_PICS_COMMENT |
+---------------------+
2 rows in set (0.00 sec)
mysql> SELECT `NICKS`.`NICK`, `USERS_PICS`.`ID`, `USERS_PICS`.`ST`, `USERS_PICS`.`GOSTERIM`, `USERS_PICS`.`GOSTERIMIP`, `USERS_PICS`.`USER_ID`, `USERS_PICS`.`NAME`, `USERS_PICS`.`DESCT`, `USERS_PICS`.`CDATE`, `USERS_PICS`.`ONAYLAYAN`, `USERS_PICS`.`SONISLEM`, `USERS_PICS`.`HIT`, Count(`USERS_PICS_COMMENT`.`PICTURE_ID`) AS `COUNT_COMMENT` FROM `NICKS` Inner Join `USERS_PICS` ON `USERS_PICS`.`USER_ID` = `NICKS`.`USER_ID` Inner Join `USERS_PICS_COMMENT` ON `USERS_PICS`.`ID` = `USERS_PICS_COMMENT`.`PICTURE_ID` WHERE `USERS_PICS`.`ST` = 3 AND `USERS_PICS_COMMENT`.`DATE_CONFIRM` IS NULL GROUP BY `NICKS`.`NICK`, `USERS_PICS`.`ID`,
`USERS_PICS`.`ST`, `USERS_PICS`.`GOSTERIM`, `USERS_PICS`.`GOSTERIMIP`, `USERS_PICS`.`USER_ID`, `USERS_PICS`.`NAME`, `USERS_PICS`.`DESCT`, `USERS_PICS`.`CDATE`, `USERS_PICS`.`ONAYLAYAN`, `USERS_PICS`.`SONISLEM`, `USERS_PICS`.`HIT`\G
*************************** 1. row ***************************
NICK: openxs
ID: 2
ST: 3
GOSTERIM: 0
GOSTERIMIP:
USER_ID: 2
NAME: Valeriy K.
DESCT:
CDATE: 0000-00-00 00:00:00
ONAYLAYAN: 0
SONISLEM: 0000-00-00 00:00:00
HIT: 0
COUNT_COMMENT: 1
*************************** 2. row ***************************
NICK: vk
ID: 1
ST: 3
GOSTERIM: 0
GOSTERIMIP:
USER_ID: 1
NAME: Valeriy
DESCT:
CDATE: 0000-00-00 00:00:00
ONAYLAYAN: 0
SONISLEM: 0000-00-00 00:00:00
HIT: 0
COUNT_COMMENT: 1
2 rows in set (0.00 sec)
So, please, try to create as small set of data as possible (in MySQL 4.x.y) that gives this crash in your environment, and upload it to the report.
[17 Mar 2006 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
