Description:
Run "slave stop"
mysqld.err:
080115 16:22:29 [Note] Slave I/O thread killed while reading event
080115 16:22:29 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000015', position 252956652
080115 16:22:29 [Note] Slave SQL thread exiting, replication stopped in log 'mysql-bin.000014' at position 473388048
Run "slave start"
mysqld.err:
080115 16:42:10 [Note] Slave I/O thread: connected to master 'replica@10.29.30.70:3306', replication started in log 'mysql-bin.000015' at position 252956652
080115 16:42:10 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000014' at position 473388048, relay log './mysqld-relay-bin.00001
0' position: 473388185
080115 16:42:10 - 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=402653184
read_buffer_size=6287360
max_used_connections=7
max_connections=448
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3012860 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x97faef8
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...
Cannot determine thread, fp=0xa3d912b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817ebb0
0x828f00e
0x828f205
0x81e9c02
0x81e9dca
0x816889a
0x8168c50
0x8168cbe
0x8107726
0x81b5b06
0x81e4ed4
0x819605a
0x8199861
0x8200fc1
0x820176e
0x82695da
0xb7d414bb
0xb7b7b76e
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9218930 = INSERT INTO TUTILM (SWINSTPRODID,SWPRODRELEASEID,SWSORTMSINSTPRODID,SWMASTERINSTPRODID,SWPARENTINSTPRODID,SWCUSTOMERID,SWSITEID,SWRE
GIONID,SWNODEID,SWPERSONID,SWDEPARTMENTID,SWOWNERSHIP,SWAGREEMENTID,SWDISTRIBUTOR,SWDISTCONTACT,SWPRIMARYCONTACT,SWREP,SWREPCONTACT,SWSYSTEMID,SWPOSITION,SWOR
DER,SWLEVEL,SWTOPLEVELPOSITION,SWENVIRONMENT,SWPLATFORM,SWNETWORK,SWOS,SWUI,SWOSVERSION,SWSTATUS,SWTYPE,SWAUTHCODE,SWDATEINSTALLED,SWDATESHIPPED,SWWARRANTY,SW
LASTSUPPORTDATE,SWLOCATION,SWNOTE,SWPONUMBER,SWPURCHASEDATE,SWPURCHASEPRICE,SWQUANTITY,SWSERIALNUMBER,SWASSETTAG,SWSONUMBER,SWCURRENTLYINST,SWAGRACTIVEFLAG,SW
EUPREFCURCODE,SWMASTERVER,SWCREATEDBY,SWDATECREATED,SWITEMTYPE,SWPROVISIONEDLEVEL,SWRECID,SWRECSERVID,SWOSSSYSID,SWTCACCOUNTID,SWTCAVAILABLE,SWTCORDERID,SWSPA
CCOUNTID,SWSPADDRESSID,SWSPCANCELDATE,SWSPCANCELORDERID,SWSPCUSTOMERTYPE,SWSPDISCOUNT,SWSPINSTSITETYPE,SWSPNONRECCHARGE,SWSPORDERID,SWSPORDERLINEID,SWSPRECURC
HARGE,TEBNUMCONTRATO,TEBNUMORDEN,TEBDATEORDEN,TEBNUMQT,TEBNUMLP,TEBCONCENTRADOR,TEBDATEINSTALL,TEBDATE
thd->thread_id=5165
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
080115 16:44:14 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...
080115 16:44:16 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 76684.
InnoDB: Doing recovery: scanned up to log sequence number 0 76684
InnoDB: Last MySQL binlog file position 0 160783318, file name /var/run/mysqld/mysqld-bin.000007
080115 16:44:16 InnoDB: Started; log sequence number 0 76684
080115 16:44:17 [Warning] 'db' entry 'sgp root@security.tdatabrasil.net.br' ignored in --skip-name-resolve mode.
080115 16:44:17 [Warning] 'db' entry 'sgo root@security.tdatabrasil.net.br' ignored in --skip-name-resolve mode.
080115 16:44:17 [Warning] 'db' entry 'relatorios root@security.tdatabrasil.net.br' ignored in --skip-name-resolve mode.
080115 16:44:17 [Warning] 'db' entry 'manut root@security.tdatabrasil.net.br' ignored in --skip-name-resolve mode.
080115 16:44:17 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.44-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.0.44-r2
080115 16:46:03 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000014' at position 473388048, relay log './mysqld-relay-bin.00000
1' position: 4
080115 16:46:03 [Note] Slave I/O thread: connected to master 'replica@10.29.30.70:3306', replication started in log 'mysql-bin.000014' at position 473388048
080115 16:46:04 [ERROR] Slave: Error 'Table 'sgo.TUTILM' doesn't exist' on query. Default database: 'sgo'. Query: 'INSERT INTO TUTILM (SWINSTPRODID,SWPRODRELE
ASEID,SWSORTMSINSTPRODID,SWMASTERINSTPRODID,SWPARENTINSTPRODID,SWCUSTOMERID,SWSITEID,SWREGIONID,SWNODEID,SWPERSONID,SWDEPARTMENTID,SWOWNERSHIP,SWAGREEMENTID,S
WDISTRIBUTOR,SWDISTCONTACT,SWPRIMARYCONTACT,SWREP,SWREPCONTACT,SWSYSTEMID,SWPOSITION,SWORDER,SWLEVEL,SWTOPLEVELPOSITION,SWENVIRONMENT,SWPLATFORM,SWNETWORK,SWO
S,SWUI,SWOSVERSION,SWSTATUS,SWTYPE,SWAUTHCODE,SWDATEINSTALLED,SWDATESHIPPED,SWWARRANTY,SWLASTSUPPORTDATE,SWLOCATION,SWNOTE,SWPONUMBER,SWPURCHASEDATE,SWPURCHAS
EPRICE,SWQUANTITY,SWSERIALNUMBER,SWASSETTAG,SWSONUMBER,SWCURRENTLYINST,SWAGRACTIVEFLAG,SWEUPREFCURCODE,SWMASTERVER,SWCREATEDBY,SWDATECREATED,SWITEMTYPE,SWPROV
ISIONEDLEVEL,SWRECID,SWRECSERVID,SWOSSSYSID,SWTCACCOUNTID,SWTCAVAILABLE,SWTCORDERID,SWSPACCOUNTID,SWSPADDRESSID,SWSPCANCELDATE,SWSPCANCELORDERID,SWSPCUSTOMERT
YPE,SWSPDISCOUNT,SWSPINSTSITETYPE,SWSPNONRECCHARGE,SWSPORDERID,SWSPORDERLINEID,SWSPRECURCHARGE,TEBN
080115 16:46:04 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log
'mysql-bin.000014' position 473388410
080115 16:54:24 [Note] Slave I/O thread killed while reading event
080115 16:54:24 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000014', position 966498619
sgo.TUTILM is a temporary table
"slave stop" command is killing temporary tables on slave server?
How to repeat:
run 'slave stop'
wait
run 'slave start'
mysqld on slave server crash if exists tmp tables in memory
