Mysql Error 2353
me why I get problems when I have 2 ndbd nodes, and NoOfReplicas=1 and I try to start one of the ndbd nodes with : ndbd --initial -v --nowait-nodes=other_node I get hte error message : ------------- Node 2: Forced node shutdown completed. Occured during startphase 1. Caused by error 2353: 'Insufficent nodes for system restart(Restart error). Temporary error, restart node' -------------- looking in the ndb_2_error.log it says : Status: Temporary error, restart node Message: Insufficent nodes for system restart (Restart error) Error: 2353 Error data: Illegal initial start, no alive node in nodegroup 1 Error object: DBDIH (Line: 14646) 0x0000000a Program: ndbd Pid: 2910 Trace: /var/lib/mysql/ndb_2_trace.log.7 Version: mysql-5.1.35 ndb-7.0.7 I have googled it and it seemed to be a bug in the 6.something releases, and apparently was fixed... has it krept back in ? best regards, Richard -- Richard McCluskey Senior Engineer, go2 Media Inc. rmccluskey@stripped (617) 457-7870 ext 108 m.go2.com - The best entertainment guide on mobile. Thread• --nowait-nodes being ignored.RichardMcCluskey23Oct • Re: --nowait-nodes being ignored.AndrewHutchings23Oct • Re: --nowait-nodes being ignored.RichardMcCluskey23Oct • Re: --nowait-nodes being ignored.AndrewHutchings23Oct • Re: --nowait-nodes being ignored.JonStephens23Oct © 1995, 2016, Oracle Corporation and/or its affiliates Legal Policies Your Privacy Rights Terms of Use Contact Us Page generated in 0.009 sec. Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.
Email Updates: Status: Not a Bug Impact on me: None Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical) Version:5.0.40 OS:Linux Assigned to: View Add Comment Files Developer Edit Submission View Progress Log Contributions [25 May 2007 12:46] Geert Vanderkelen Description: (logs will be attached) 2007-05-25 11:34 - Ran out of DataMemory 11:51:02 - Should have set DataMemory higher, but instead did IndexMemory (don't ask me why..) 11:51:02 - Started rolling restart: node 3 shut http://lists.mysql.com/cluster/6967 down 12:06:16 - Node 3 forced shutdown during start phase 5 By mistake I used 5.0.41 version instead of 5.0.40, but got same result. Retried afterwards again with reverting IndexMemory and starting up the same version as node 4, but same error kept coming. Kinda ugly error in ndb_mgm: ndb_mgm> Node 3: Forced node shutdown completed. https://bugs.mysql.com/bug.php?id=28675 Occured during startphase 5. Initiated by signal 6. Caused by error 2303: 'System error, node killed during node restart by other node(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'. - Unknown error code: Unknown result: Unknown error code Node 3 error log: Time: Friday 25 May 2007 - 12:06:15 Status: Temporary error, restart node Message: System error, node killed during node restart by other node (Internal error, programming error or missing error message, please report a bug) Error: 2303 Error data: Killed by node 4 as copyfrag failed, error: 827 Error object: NDBCNTR (Line: 196) 0x0000000a Program: ./libexec/ndbd Pid: 25193 Trace: /data1/csc/16870/cluster/ndb_3_trace.log.1 Version: Version 5.0.40 ***EOM*** Doing a system restart, the same node 3 goes down with the error. How to repeat: - I have no good repeatable test case. - Some BLOB fields were used in the tables. Following config was used, with 2 data nodes: [NDBD DEFAULT] NoOfReplicas=2 DataMemory=2G IndexMemory=300M MaxNoOfOrderedIndexes = 256 Max
Email Updates: Status: Can't repeat Impact on me: None Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical) Version:5.0.67 OS:Linux (CentOs 5.2) Assigned to: Jonas Oreland Tags: https://bugs.mysql.com/bug.php?id=40229 2311, Internal error, selecting restart type, startphase 1, Temporary error Triage: Needs Triage: D2 (Serious) View Add Comment Files Developer Edit Submission View Progress Log Contributions [22 Oct 2008 4:39] James Knight Description: After attempting to start a cluster node, the node prompts with the following error and then terminates: "Node 3: Forced node shutdown completed. Occured during startphase 1. Caused by error 2311: mysql error 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'." At one point the cluster appeared to be completely operational - after a series of simulated power downs (force quit on the machines) the error appeared. [ndb_3_out] --- 2008-10-21 16:05:07 [ndbd] INFO -- Angel pid: 2500 ndb pid: 2501 2008-10-21 16:05:07 [ndbd] INFO -- NDB mysql error 2353 Cluster -- DB node 3 2008-10-21 16:05:07 [ndbd] INFO -- Version 5.0.67 -- 2008-10-21 16:05:07 [ndbd] INFO -- Configuration fetched at 192.168.1.161 port 1186 2008-10-21 16:05:08 [ndbd] INFO -- Start initiated (version 5.0.67) 2008-10-21 16:05:41 [ndbd] INFO -- Error handler startup shutting down system 2008-10-21 16:05:45 [ndbd] INFO -- Angel received ndbd startup failure count 1. 2008-10-21 16:05:45 [ndbd] INFO -- Error handler shutdown completed - exiting 2008-10-21 16:05:45 [ndbd] ALERT -- Node 3: Forced node shutdown completed. Occured during startphase 1. Caused by error 2311: 'Conflict when selecting restart type(Internal error, programming error or missing error message, please report a bug). Temporary error, restart node'. 2008-10-21 16:05:54 [ndbd] WARNING -- Unable to report shutdown reason to 192.168.1.160:1186: Could not connect to socket : Unable to connect with connect string: nodeid=0,192.168.1.160:1186 --- [ndb_3_error.log] --- Current byte-offset of file-pointer is: 568 Time: Tuesday 21 October 2008 - 16:05:41 Status: Temporary error, restart node Message: Conflict when selecting restart type (Internal error, programming error or missing error message, please report a bug) Error: 2311 Error data: Unable to start missing node group! starting: 0000000000000008 (missing fs for: 0000000000000000) Error object: QMGR (Line: 1402) 0x0000