Slave server crash after an update statement
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
George Ormond Lorch III | ||
5.5 |
Fix Released
|
High
|
George Ormond Lorch III |
Bug Description
The latest 5.5.27-28.1 Percona Server crashes when the following list of things happens:
- execute a update statement using a variable
- slave server has replicate-
MASTER: 5.5.24-rel26.0-log
(default sandbox my.cnf)
[mysql]
prompt='mysql [\h] {\u} (\d) > '
#
[client]
user = msandbox
password = msandbox
port = 5524
socket = /tmp/mysql_
[mysqld]
user = root
port = 5524
socket = /tmp/mysql_
basedir = /root/5.5.24
datadir = /root/sandboxes
tmpdir = /root/sandboxes
pid-file = /root/sandboxes
#log-slow-queries = /root/sandboxes
#log = /root/sandboxes
#
# additional options passed through 'my_clause'
#
log-error=
server_id=1
log-bin=a
SLAVE: 5.5.27-28.1 Percona Server
root@debian:
[mysqld]
datadir=
innodb_
innodb_
server_id=2
replicate-
replicate-
master> create database mytest;
master> use mytest;
master> create table t (i int, a char(10), b char(11));
master> insert into t values (1,'xxx','yyy');
master> update mytest.t set a='xxx'
then, restart the MASTER:
master> use mytest;
master> update mytest.t set i=1;
master> update mytest.t set a='xxx'
then, on the SLAVE:
slave> stop slave;
slave> start slave;
slave> show slave status\G
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/
ERROR:
Can't connect to the server
1:04:07 UTC - 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_
read_buffer_
max_used_
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2b04580
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 = 7f9e92a59ea8 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2b436a0): ?6?
Connection ID (thread ID): 1
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting
http://
in the manual which will help you identify the cause of the crash.
Related branches
- Laurynas Biveinis (community): Approve
-
Diff: 11 lines (+1/-1)1 file modifiedPercona-Server/sql/log_event.h (+1/-1)
tags: | added: i25112 |
tags: | added: replication |
summary: |
- Server crash after an update statement + Slave server crash after an update statement |
description: | updated |
I've reinstalled everything again and now following the same procedure it doesn't crash, seems that something is messing.