Bug #40688 | mysql crash | ||
---|---|---|---|
Submitted: | 13 Nov 2008 6:49 | Modified: | 9 Jan 2009 7:57 |
Reporter: | Bartek okan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.1.31 | OS: | Linux (centos 5) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash, MySQL, replication |
[13 Nov 2008 6:49]
Bartek okan
[13 Nov 2008 6:54]
MySQL Verification Team
Hi Bartek, please send output of: show create table smf_sessions; select @@global.binlog_format; thanks,
[13 Nov 2008 7:10]
Bartek okan
+--------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +--------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | smf_sessions | CREATE TABLE `smf_sessions` ( `session_id` char(32) NOT NULL DEFAULT '', `last_update` int(10) unsigned NOT NULL, `data` mediumtext NOT NULL, PRIMARY KEY (`session_id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 | +--------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec) select @@global.binlog_format; +------------------------+ | @@global.binlog_format | +------------------------+ | STATEMENT | +------------------------+ hmm is it because of statement ? hmm.. should i switch to mixed ?
[13 Nov 2008 15:13]
Bartek okan
shit stoped after switching to MIXED but yet old bug come back i dont remember its number: Last_SQL_Error: Could not execute Delete_rows event on table testing.mybb_sessions; Can't find record in 'mybb_sessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log mysqlbin.000005, end_log_pos 586265043 | mybb_sessions | CREATE TABLE `mybb_sessions` ( `sid` varchar(32) NOT NULL DEFAULT '', `uid` int(10) unsigned NOT NULL DEFAULT '0', `ip` varchar(40) NOT NULL DEFAULT '', `time` bigint(30) NOT NULL DEFAULT '0', `location` varchar(150) NOT NULL DEFAULT '', `useragent` varchar(100) NOT NULL DEFAULT '', `anonymous` int(1) NOT NULL DEFAULT '0', `nopermission` int(1) NOT NULL DEFAULT '0', `location1` int(10) NOT NULL DEFAULT '0', `location2` int(10) NOT NULL DEFAULT '0', `loginattempts` tinyint(2) NOT NULL DEFAULT '1', `failedlogin` bigint(30) NOT NULL DEFAULT '0', PRIMARY KEY (`sid`), KEY `location1` (`location1`), KEY `location2` (`location2`), KEY `time` (`time`), KEY `uid` (`uid`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 | bin=MIXED replication between two 5.1.31 (bzr) (centos 5 64bit ) if you need any other information like just ask
[13 Nov 2008 20:20]
Bartek okan
http://bugs.mysql.com/bug.php?id=40004 - still exist Could not execute Update_rows event on table test.e107_online; handler error HA_ERR_END_OF_FILE; the event's master log mysqlbin.000005, end_log_pos 993011008 and for about 10 hours replication goes to hell, just more ane more of those error shows up, and it is impossible to recover from it exist in 5.1.28(bin)/5.1.29(bin)/5.1.30(bzr)/5.1.31(bzr) all daabases such as *online*, *session* getting crazy with MIXED replication i can`t use STATEMENT because server instantly crush after each 5 minutes of runing... when sever is runned standalone (without replication), its ok... when i try to setup master-to-master: -HA_ERR_END_OF_FILE -HA_ERR_KEY_NOT_FOUND Those two error on tables like *online*, *session* which in structure are very close to example higher.. broke the replication to death :)
[17 Nov 2008 20:40]
Bartek okan
are there any work around it ? It crash under 5.0 GA too its about month from first statemnt of this bug, you state that is fixed.. but isn`t ? is there any ETA for it, this is very serious cricital bug...
[9 Dec 2008 7:57]
Valeriy Kravchuk
Nobody claimed that this bug (repeatable on both 5.1 and 5.0 with statement-based replication) is fixed. We can not even repeat it in our environment yet. Please, send your entire my.cnf, the results of SHOW GLOBAL STATUS and the results of: free Linux command. As for bug #40004, indeed, we claimed it is fixed in 5.1.30 and newer versions. It is NOT related directly to this report (you have primary key and use statement-based replication), but if you have a repeatable test case for bug #40004 send it here and I'll reopen it.
[10 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".