MySQL Bugs: #71415: No message slogan found (Unable to store fragment during LCP. NDBFS Error: 873)

Bug #71415	No message slogan found (Unable to store fragment during LCP. NDBFS Error: 873)
Submitted:	18 Jan 2014 6:01	Modified:	10 Apr 2016 13:08
Reporter:	Benjamin Broich	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.56	OS:	Linux (2.6.37)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	dblhq, ndbfs, storage

Description:
For some reason sometimes one of two NDB Storage we are using stops with the following error message:

2014-01-17 22:21:05 [ndbd] INFO     -- Unable to store fragment during LCP. NDBFS Error: 873
2014-01-17 22:21:05 [ndbd] INFO     -- DBLQH (Line: 11639) 0x0000000a
2014-01-17 22:21:05 [ndbd] INFO     -- Error handler shutting down system
2014-01-17 22:21:06 [ndbd] INFO     -- Error handler shutdown completed - exiting
2014-01-17 22:21:06 [ndbd] ALERT    -- Node 41: Forced node shutdown completed. Caused by error 873: 'No message slogan found (please report a bug if you get this error code)(Unknown). Unknown'.

This happens on both nodes, but not at the same time. It is just some time Node41 and sometimes Node42, everytime with the same error.

After restarting the ndbd process it sometimes works without any problems to get the Node up and running again over ndb_mgm. But we also had the problem that after this we needed to start the node with --initial again.

Now this happens just sometimes (but too much often) every 2nd or 3rd day we have this problem.

Is there a way to investigate this? Please let me know if there are more details for getting into this.

How to repeat:
For the moment I have no clue how to repeat this.

Hi Benjamin,

are you still experiencing this problem? This type of ndb filesystem corruption should be fixed in 6.2 and newer releases, for sure should not happen with latest 7.4. 

let us know if you still experience this type of problems.

all best
Bogdan Kecman

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".