Bug #77014 | SIGSEGV for ndbmtd | ||
---|---|---|---|
Submitted: | 12 May 2015 10:54 | Modified: | 26 May 2015 13:36 |
Reporter: | Сергей Кукуев | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S2 (Serious) |
Version: | 7.4.4 | OS: | Linux (2.6.39-200.24.1.el6uek.x86_64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | ndbmtd, segmentation fault, Signal 11, SIGSEGV |
[12 May 2015 10:54]
Сергей Кукуев
[12 May 2015 11:01]
Сергей Кукуев
Error report uploaded to sftp.oracle.com file mysql-bug-data-77014.tar.bz2
[26 May 2015 13:32]
MySQL Verification Team
Hi, In order to investigate this further a full cluster logs are required. You can collect them using ndb_error_reporter tool. all best Bogdan Kecman
[26 May 2015 13:36]
Сергей Кукуев
Hi, Bogdan! I've already attached full logs from ndb_error_reporter - see comment from 12 of May
[26 May 2015 13:45]
MySQL Verification Team
Hi Sergey, Sorry I seen only the "messages" missed that one. Thanks for the report Bogdan Kecman
[7 Jul 2015 12:14]
Mikael Ronström
Posted by developer: Seen similar issues in test runs occasionally. This happens during the memory allocation phase of a data node start (ndbtmd start). Most likely some issue in interaction between OS and ndbmtd. Unfortunately we never get a core file which is analysable which seems kind of to be part of the problem.