Bug #41216 | mysql random crash | ||
---|---|---|---|
Submitted: | 4 Dec 2008 6:43 | Modified: | 8 Jan 2009 9:36 |
Reporter: | Kelvin Liang | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.1.30 | OS: | Linux (CentOS 5.2 (AMD x86-64)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash |
[4 Dec 2008 6:43]
Kelvin Liang
[4 Dec 2008 9:46]
Sveta Smirnova
Thank you for the report. But version 5.1.28 is a bit old. Please try current version 5.1.30 and if problem still exists provide more information about your machine: how much physical RAM it has, OS version, MySQL configuration file. Would be good if you could run debug version (mysqld-debug) and get core file.
[7 Dec 2008 8:32]
Kelvin Liang
I have upgrade the MySQL to 5.1.30, but it still crash after a few days. The err message is: /usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x2e)[0x837bde] /usr/local/mysql/libexec/mysqld(handle_segfault+0x322)[0x5976f2] /lib64/libpthread.so.0[0x3f1700de80] /usr/local/mysql/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x570)[0x6184b0] /usr/local/mysql/libexec/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x169)[0x618a09] /usr/local/mysql/libexec/mysqld[0x5a1cec] /usr/local/mysql/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x1807)[0x5a7197] 081207 13:08:33 - mysqld got signal 11 ; 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=536870912 read_buffer_size=2097152 max_used_connections=636 max_threads=1500 threads_connected=395 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6683522 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2aad0ce255b0 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... stack_bottom = 0x466b40f0 thread_stack 0x40000 /usr/local/mysql/libexec/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x228)[0x5ad3c8] /usr/local/mysql/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x3f1)[0x5ad7c1] /usr/local/mysql/libexec/mysqld(_Z10do_commandP3THD+0xe4)[0x5ae934] /usr/local/mysql/libexec/mysqld(handle_one_connection+0x5d7)[0x59f697] /lib64/libpthread.so.0[0x3f17006307] /lib64/libc.so.6(clone+0x6d)[0x3f164d1ded] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x2aacf6e82ba0 is an invalid pointer thd->thread_id=1554424 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. 081207 13:08:35 mysqld_safe Number of processes running now: 0 081207 13:08:35 mysqld_safe mysqld restarted My Server has 16G RAM and 2 CPU(Quad-Core AMD Opteron Processor 2352). The binaries are built on: CXX=gcc ./configure \ --prefix=/usr/local/mysql --enable-assembler \ --with-charset=utf8 \ --with-extra-charsets=gbk,gb2312,latin1 \ --localstatedir=/opt/mysql-data \ --with-mysqld-user=mysql --enable-large-files --with-big-tables \ --without-debug \ --with-mysqld-ldflags=-all-static \ --with-client-ldflags=-all-static \ --enable-thread-safe-client \ --with-innodb --with-fast-mutexes
[7 Dec 2008 11:54]
Kelvin Liang
die again :( /usr/local/mysql/libexec/mysqld(my_print_stacktrace+0x2e)[0x837bde] 081207 19:18:41 - mysqld got signal 11 ; 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=536870912 read_buffer_size=2097152 max_used_connections=516 max_threads=1500 threads_connected=376 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6683522 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2aacfc2ddce0 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... stack_bottom = 0x49fe10f0 thread_stack 0x40000 /usr/local/mysql/libexec/mysqld(handle_segfault+0x322)[0x5976f2] /lib64/libpthread.so.0[0x3f1700de80] /usr/local/mysql/libexec/mysqld(_Z9lex_startP3THD+0x116)[0x4dfb86] /usr/local/mysql/libexec/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x35)[0x5ad1d5] /usr/local/mysql/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x3f1)[0x5ad7c1] /usr/local/mysql/libexec/mysqld(_Z10do_commandP3THD+0xe4)[0x5ae934] /usr/local/mysql/libexec/mysqld(handle_one_connection+0x5d7)[0x59f697] /lib64/libpthread.so.0[0x3f17006307] /lib64/libc.so.6(clone+0x6d)[0x3f164d1ded] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x2aacf58cd800 is an invalid pointer thd->thread_id=330330 thd->killed=NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. mysqld: my_new.cc:50: int __cxa_pure_virtual(): Assertion `"Pure virtual method called." == "Aborted"' failed. 081207 19:18:42 mysqld_safe Number of processes running now: 0 081207 19:18:42 mysqld_safe mysqld restarted
[8 Dec 2008 9:28]
Sveta Smirnova
Thank you for the feedback. Could you please try to locate query which causes crash? You can do it in 2 ways: 1. Run mysqld-debug instead of mysqld and get core file, then send us both core file and mysqld-debug file. 2. More difficult way if you can not run mysqld-debug, for example, because performance reason. Enable query logging (probably general log could help, but even better if you do it at application level), then locate query which fails. Thanks in advance.
[9 Jan 2009 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".