| Bug #51054 | mysqld segfault after binlog enabled | ||
|---|---|---|---|
| Submitted: | 10 Feb 2010 10:15 | Modified: | 9 Sep 2010 17:06 |
| Reporter: | Pascal Schmiel | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S1 (Critical) |
| Version: | 5.1.37, 5.5.x, next-mr-merge | OS: | Linux (RHEL5) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[10 Feb 2010 10:15]
Pascal Schmiel
[10 Feb 2010 10:32]
Valeriy Kravchuk
I am not sure how crash while execuing SELECT query can be related to binlog being enabled... Anyway, please, try to repeat with a newer version, 5.1.43. In case of the same problem, please, send your my.cnf file content and EXPLAIN results for that crashing SELECT.
[10 Feb 2010 10:39]
Pascal Schmiel
I'm not sure if the SELECT query is the cause of the crash because it is executed about 20000 times / hour. nevertheless i will try an update asap.
[10 Feb 2010 16:12]
MySQL Verification Team
this looks alot like bug #39022 to me!
[11 Feb 2010 10:05]
Pascal Schmiel
we can now reproduce the bug. it occures when executing this query: DELETE FROM users.session_log WHERE (validto IS NULL or validto < '2010-02-11 00:00:00' ) AND timestamp not like '2010-02-11%; it is not reproducable in our development-system, i think because there are no deadlocks.
[1 Jun 2010 6:42]
Sveta Smirnova
Thank you for the feedback. As this really looks like bug #39022 which is fixed in 5.1.45 please upgrade to current version 5.1.47 and inform us if problem still exists.
[1 Jul 2010 23: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".
[7 Jul 2010 14:27]
Alfranio Tavares Correia Junior
Re-opening the bug as something similar is happening in pb. Please, take a look at http://tinyurl.com/2eaojup
[23 Jul 2010 15:28]
Sveta Smirnova
Alfranio, thank you for the feedback. Set to "Verified" as we have this crash repeated and documented on our boxes.
[30 Aug 2010 8:42]
Alfranio Tavares Correia Junior
HOW TO REPEAT
-------------
. Get mysql-next-mr.crash-safe.
. run:
#!/bin/bash
for i in `seq 1 300`; do
./mtr --parallel=auto --mem rpl_mixed_crash_safe rpl_stm_crash_safe rpl_row_crash_safe 2>&1 | tee output.log
res=`grep fail output.log`
if [ "!$res" != "!" ]; then
exit $?
fi
done
The test cases crash the slave periodically and verify if the safely recovery.
Sporadically, after a crash, there will be:
mysqld: /home/acorreia/workspace.sun/repository.mysql.new/bzrwork/wl-2775/mysql-next-mr-rpl-merge.crash-safe.2775/mysys/my_new.cc:51: int __cxa_pure_virtual(): Assertion `! "Aborted: pure virtual method called."' failed.
100830 4:56:00 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Compressed tables use zlib 1.2.3.3
100830 4:56:00 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
100830 4:56:00 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 4 row operations to undo
InnoDB: Trx id counter is 2900
InnoDB: Last MySQL binlog file position 0 636, file name ./slave-bin.000018
100830 4:56:00 InnoDB 1.2.0 started; log sequence number 1703595
100830 4:56:00 [Note] Recovering after a crash using slave-bin
100830 4:56:00 [Note] Starting crash recovery...
100830 4:56:00 [Note] Crash recovery finished.
InnoDB: Starting in background the rollback of uncommitted transactions
100830 4:56:00 InnoDB: Rolling back trx with id 2713, 4 rows to undo
[9 Sep 2010 16:45]
Alfranio Tavares Correia Junior
Hi all, After some tests, I've figured out that the new failure is not related to Innodb. We have the following stacktrace: /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(__cxa_pure_virtual+0x6f)[0xa3d523] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z23get_cached_table_accessP22st_grant_internal_infoPKcS2_+0x73)[0x54416d] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z11check_grantP3THDmP10TABLE_LISTbjb+0x18c)[0x546dcc] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z18check_table_accessP3THDmP10TABLE_LISTbjb+0x238)[0x5abc78] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z21mysql_execute_commandP3THD+0x740)[0x5ad8be] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x1c9)[0x5b4dad] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x9cf)[0x5b620b] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z10do_commandP3THD+0x227)[0x5b7603] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(_Z24do_handle_one_connectionP3THD+0x135)[0x686553] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(handle_one_connection+0x2d)[0x686619] /export/home2/tmp/ac230274/mysql-5.6.99-m5/sql/mysqld(pfs_spawn_thread+0x92)[0x9f5c2e] /lib64/libpthread.so.0[0x33d20062f7] /lib64/libc.so.6(clone+0x6d)[0x33d14d1b6d] Fatal signal 11 while backtracing The problem stems from the fact that destructor of both ACL_internal_schema_access and ACL_internal_table_access are called while exiting the server. Specifically, the test case explicitly crashes the server by calling abort() that calls handle_segfault() --> exit(1) While processing exit(1), associated handlers/callbacks are executed and destroy the ACL_internal_schema_access and ACL_internal_table_access. Meanwhile, another thread is able to start processing a statement and fails because the objects ACL_internal_schema_access and ACL_internal_table_access do not exist.
[9 Sep 2010 16:47]
Alfranio Tavares Correia Junior
I've made the following changes to the code to get the stacktrace:
int __cxa_pure_virtual()
{
DBUG_ENTER("__cxa_pure_virtual");
fprintf(stderr,"Aborted: pure virtual method called.\n");
fflush(stderr);
void *addrs[128];
char **strings= NULL;
int n= backtrace(addrs, array_elements(addrs));
strings= backtrace_symbols(addrs, n);
backtrace_symbols_fd(addrs, n, fileno(stderr));
fflush(stderr);
DBUG_RETURN(1);
}
mysql-test/suite/rpl/t/rpl_*_crash_safe-slave.opt
--skip-core-file --skip-slave-start --relay-log-info-repository=TABLE --relay-log-recovery=1
