Bug #67651 Mysql-Cluster failed startinbg in Phase 4
Submitted: 20 Nov 2012 13:07 Modified: 4 Feb 2013 8:41
Reporter: Dominique Daue Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Cluster: Disk Data Severity:S1 (Critical)
Version:7.2.8 OS:Linux
Assigned to: CPU Architecture:Any

[20 Nov 2012 13:07] Dominique Daue
Description:
mysql cluster node doesn't want to start 

ndb_2_out.log :

RESTORE table: 3 8 rows applied
RESTORE table: 4 24 rows applied
RESTORE table: 4 31 rows applied
RESTORE table: 5 10 rows applied
RESTORE table: 5 10 rows applied
RESTORE table: 6 0 rows applied
RESTORE table: 6 0 rows applied
2012-11-20 13:56:54 [ndbd] INFO     -- Error 1227 (line: 1258) during restore of  0/T7F0
2012-11-20 13:56:54 [ndbd] INFO     -- RESTORE (Line: 1283) 0x00000002
2012-11-20 13:56:54 [ndbd] INFO     -- Error handler shutting down system       
2012-11-20 13:56:54 [ndbd] INFO     -- Error handler shutdown completed - exiting
2012-11-20 13:56:54 [ndbd] ALERT    -- Node 2: Forced node shutdown completed. Occured during startphase 4. Caused by error 2352: 'Invalid LCP(Ndbd file system inconsistency error, please report a bug). Ndbd file system error, restart node initial'.

How to repeat:
based on our data
[4 Jan 2013 8:41] Umesh Shastry
Looking at the error:

# bin/perror --ndb 1227
NDB error code 1227: Invalid schema version: Permanent error: Schema error
MySQL error code 1227 (ER_SPECIFIC_ACCESS_DENIED_ERROR): Access denied; you need (at least one of) the %-.128s privilege(s) for this operation

This seems to be result of copying files, could you please elaborate the sequence of steps you performed before hitting this issue? This 
will help us understand the problem better.

Could you please attach the cluster logs? Preferably using the ndb_error_reporter utility:

  http://dev.mysql.com/doc/refman/5.5/en/mysql-cluster-programs-ndb-error-reporter.html

Regards,
Umesh
[5 Feb 2013 1:00] Bugs System
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".