# 5.5.25a server crash when replication starts **URL:** \ **Category:** Other MySQL® Questions\ **Created:** [December 6, 2012, 2:56am UTC](https://forums.percona.com/t/5-5-25a-server-crash-when-replication-starts/1943 "2012-12-06T02:56:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![heaje](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@heaje](https://forums.percona.com/u/heaje)\ **Post date:** [December 6, 2012, 2:56am UTC](https://forums.percona.com/t/5-5-25a-server-crash-when-replication-starts/1943/1 "2012-12-06T02:56:36Z")
In the last 1.5 weeks, we’ve started running into a very strange issue where we have 5 different slaves that will suddenly completely crash in the middle of replication. Once that happens, we can never successfully get replication going again without completely re-initializing the slave. This happens at minimum every 24 hours. I’ve already verified that these slaves are not overloaded in the slightest. There’s plenty of free memory and CPU is no where close to being fully utilized. Once the crash happens, MySQL will never be able to start again until it is started with “skip-slave-start”. Once the command for “start slave” is issued, the server immediately crashes. I have looked in the relay logs on the slave and in the binary logs on the master and I cannot see anything wrong at all with the queries being sent to the slave. Here are the crash details from the logs. The messages appear immediately after the slave connects to the master to start replication. 08:14:48 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 key\_buffer\_size=8388608 read\_buffer\_size=131072 max\_used\_connections=5 max\_threads=200 thread\_count=4 connection\_count=4 It is possible that mysqld could use up to key\_buffer\_size + (read\_buffer\_size + sort\_buffer\_size)\*max\_threads = 445843 K bytes of memory Hope that’s ok; if not, decrease some variables in the equation. Thread pointer: 0x24622950 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 = 4bef40e8 thread\_stack 0x40000 /opt/apps/ms/mysql/sbin/mysqld(my\_print\_stacktrace+0x2e)[0x7 b346e] /opt/apps/ms/mysql/sbin/mysqld(handle\_fatal\_signal+0x3e2)[0x 688dd2] /lib64/libpthread.so.0[0x39cc00eb10] /lib64/libc.so.6(strcmp+0x2)[0x39cb879232] /opt/apps/ms/mysql/sbin/mysqld(_ZN5TABLE4initEP3THDP10TABLE_ LIST+0x4d)[0x5f153d] /opt/apps/ms/mysql/sbin/mysqld(\_Z10open\_tableP3THDP10TABLE\_L ISTP11st\_mem\_rootP18Open\_table\_context+0x130)[0x53fe60] /opt/apps/ms/mysql/sbin/mysqld(\_Z11open\_tablesP3THDPP10TABLE \_LISTPjjP19Prelocking\_strategy+0x2c1)[0x542841] /opt/apps/ms/mysql/sbin/mysqld(\_Z20open\_and\_lock\_tablesP3THD P10TABLE\_LISTbjP19Prelocking\_strategy+0x51)[0x543371] /opt/apps/ms/mysql/sbin/mysqld(\_Z12mysql\_insertP3THDP10TABLE \_LISTR4ListI4ItemERS3\_IS5\_ES6\_S6\_15enum\_duplicatesb+0xd8)[0x 567638] /opt/apps/ms/mysql/sbin/mysqld(\_Z21mysql\_execute\_commandP3TH D+0x226d)[0x57831d] /opt/apps/ms/mysql/sbin/mysqld(\_Z11mysql\_parseP3THDPcjP12Par ser\_state+0x3db)[0x57c6fb] /opt/apps/ms/mysql/sbin/mysqld(\_ZN15Query\_log\_event14do\_appl y\_eventEPK14Relay\_log\_infoPKcj+0xe45)[0x738bf5] /opt/apps/ms/mysql/sbin/mysqld(\_Z26apply\_event\_and\_update\_po sP9Log\_eventP3THDP14Relay\_log\_info+0x14d)[0x516ccd] /opt/apps/ms/mysql/sbin/mysqld[0x51fad5] /opt/apps/ms/mysql/sbin/mysqld(handle\_slave\_sql+0xc6a)[0x520 e0a] /lib64/libpthread.so.0[0x39cc00673d] /lib64/libc.so.6(clone+0x6d)[0x39cb8d3d1d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (2462fdb0): ▒▒▒ Connection ID (thread ID): 77 Status: NOT\_KILLED ---
**Author:** ![miguelangelnieto](https://avatars.discourse-cdn.com/v4/letter/m/b9e5f3/32.png) [@miguelangelnieto](https://forums.percona.com/u/miguelangelnieto)\ **Post date:** [December 6, 2012, 4:27am UTC](https://forums.percona.com/t/5-5-25a-server-crash-when-replication-starts/1943/2 "2012-12-06T04:27:46Z")
Hi, This crash is caused by the following bug: > **[Bug #1053342 “Slave server crash after an update statement” : Bugs : Percona...](https://bugs.launchpad.net/percona-server/+bug/1053342)** > > 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-wild-ignore-table or replicate-ignore-table on my.cnf > > MASTER:... That bug is solved in the latest Percona Server 5.5.28-29.1 There is a workaround, disable the replication filters on the slave. For example: replicate-wild-ignore-table replicate-ignore-table replicate-do-table and so on. Comment those variables on my.cnf and start the server again. Anyway, an upgrade is recommended. Regards. ---
**Author:** ![heaje](https://avatars.discourse-cdn.com/v4/letter/h/e56c9b/32.png) [@heaje](https://forums.percona.com/u/heaje)\ **Post date:** [December 6, 2012, 9:28am UTC](https://forums.percona.com/t/5-5-25a-server-crash-when-replication-starts/1943/3 "2012-12-06T09:28:57Z")
Thanks a ton for giving me that info! I had done considerable amounts of searching, but had not found that bug. I’ll be doing an upgrade today 🙂