Bug #67033 Mysqld got signal 11 during NDB binlog setup after cluster failure
Submitted: 1 Oct 2012 11:07 Modified: 6 Jun 2016 14:25
Reporter: Przemysław Ołtarzewski Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S1 (Critical)
Version:7.2.7 OS:Solaris (5.10)
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: binlog, crash, Failure, mysqld, ndb, Signal 11, solaris

File: Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

[9 Oct 2012 10:23] Przemysław Ołtarzewski
Management server 1 logs

Attachment: ndb_1.tar.bz2 (application/bzip2, text), 146.61 KiB.

[9 Oct 2012 10:24] Przemysław Ołtarzewski
Management server 2 logs

Attachment: ndb_2.tar.bz2 (application/bzip2, text), 140.43 KiB.

[9 Oct 2012 10:24] Przemysław Ołtarzewski
Data node 11 logs

Attachment: ndb_11.tar.bz2 (application/bzip2, text), 148.68 KiB.

[9 Oct 2012 10:25] Przemysław Ołtarzewski
Data node 12 log files

Attachment: ndb_12.tar.bz2 (application/bzip2, text), 224.33 KiB.

[9 Oct 2012 10:25] Przemysław Ołtarzewski
Data node 21 logs

Attachment: ndb_21.tar.bz2 (application/bzip2, text), 294.89 KiB.

[9 Oct 2012 10:31] Przemysław Ołtarzewski
Data node 22 logs - part 1

Attachment: ndb_22_p1.tar.bz2 (application/bzip2, text), 485.79 KiB.

[9 Oct 2012 10:32] Przemysław Ołtarzewski
Data node 22 logs - part 2

Attachment: ndb_22_p2.tar.bz2 (application/bzip2, text), 206.12 KiB.

[9 Oct 2012 10:32] Przemysław Ołtarzewski
Cluster configuration file

Attachment: config.ini (application/octet-stream, text), 2.79 KiB.