Mysql Error 2355
error 2355 View as plain text Hi, What happens if you start the other Data node (nodeid 4 and only that one). Thanks, Johan Severalnines AB On Wed, Sep 5, 2012 at 9:40 AM, xgss2000
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Start data node without --initial mysql cluster up vote 0 down vote favorite I have setup a http://lists.mysql.com/cluster/8393 cluster with disk based tables, with 2 datanodes ,one mgmt , and 2 sql nodes. Cluster is working fine... So I just wanted to test its HA , so I manually killed one datanode with KILL command at a linux prompt and I connected to sql nodes and inserted some records into a table. I then tried to start datanode which I killed with this command bin/ndbd without using any --initial When http://stackoverflow.com/questions/20007671/start-data-node-without-initial-mysql-cluster I see the logs on managmnt node it shows the below error and data node is not starting: /Node 3: Forced node shutdown completed. Occurred during startphase 5. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'. But when I use --initial it starts then it means to do a clean start from start (which will be time consuming to copy all the data files what if we have 100G ?) But I want the data node to start copying the record from the point it stopped (killed) How do I do this? mysql mysql-cluster share|improve this question edited Mar 25 '14 at 0:08 KCD 3,68612442 asked Nov 15 '13 at 18:03 sai 11 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote You have hit a unrecoverable fault (for that node, not the whole cluster) so you have no choice but to rebuild it. To avoid this scenario, safely stop the node rather than killing the process. e.g. to stop node 3 run: ndb_mgm -e '3 stop' However to recover you will not lose data if nodes in that node group (you only have one group) are still up to recover data from. First start the other nodes in the node
external action needed'. View as plain text Hi Greet, This is the error log I am getting on data node. Time: Tuesday 27 April 2010 - 09:50:44 Status: Permanent error, http://lists.mysql.org/cluster/7602 external action needed Message: Failure to restore schema (Resource configuration error) http://mysql-cluster.1050023.n4.nabble.com/Problem-restarting-node-td4655228.html Error: 2355 Error data: Failure to recreate object during restart, error 721 Please follow instructions from 'perror --ndb 721' Error object: DBDICT (Line: 4131) 0x0000000a Program: ndbmtd Pid: 9710 thr: 0 Version: mysql-5.1.39 ndb-7.0.9b Trace: /usr/local/mysql/data/ndb_3_trace.log.23 /usr/local/mysql/data/ndb_3_trace.log.23_t1 /usr/local/mysql and this is the error mysql error message which is there on management node. -- Node 4: Forced node shutdown completed. Occured during startphase 4. Caused by error 2355: 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'. -- Regards, Manasi Save On Tue, 27 Apr 2010 16:07:04 0200, Geert Vanderkelen wrote: > > On Apr 27, 2010, at 16:03 , mysql error 2355 Manasi Save wrote: > > > I need an urgent help. Please provide me with some input on how to deal with this error. As my cluster stopped working completely. > > Well, a version might help, and/or cluster log maybe. Or tell us what happened. Like, did you change configuration. Just an error message is nothing to work with. > > -Geert > > > > > Thanks in Advance. > > -- > > Regards, > > Manasi Save > > > > On Tue, 27 Apr 2010 09:30:35 -0400, Manasi Save wrote: > > Dear All, > > > > When I restarted my server. I am getting 'Failure to restore schema(Resource configuration error). Permanent error, external action needed'. error after starting data node of restared server. > > > > Is there any way I can fix this error ASAP. > > > > Thanks in advance. > > > > Any input will be a great help. > > > > -- > Ge
Report Content as Inappropriate ♦ ♦ Problem restarting node Hi! I have an stupid problem with my MySQL cluster. It's version 5.5.27-ndb-7.2.8-cluster-gpl. I have two nodes and was working perfect. But, I need to change the DataMemory value. SO, i've changed it on the config.ini file, killed the ndb_mgmd daemon and restarted with the --reload option. Then, I've entered to the ndb_mgm tool and tried to restart the second node so it gets the new config. But, it don't start with this error: Time: Friday 24 May 2013 - 15:46:07 Status: Permanent error, external action needed Message: Invalid configuration received from Management Server (Configuration error) Error: 2350 Error data: Invalid file size for redo logfile, size only changable with --initial Error object: DBLQH (Line: 15227) 0x00000002 Program: ndbd Pid: 10960 Version: mysql-5.5.27 ndb-7.2.8 Trace: /var/lib/mysql-cluster/ndb_4_trace.log.9 [t1..t1] ***EOM*** It seems that the redo logfile size has been changed, but I have not changed it! I can't loose my data on the cluster, so I can't restart with --initial parameter. I don't really know what's happened. There is a way to know whats the older value or the value of the node was expecting ? Any idea ??? Thanks! -- MySQL Cluster Mailing List For list archives: http://lists.mysql.com/clusterTo unsubscribe: http://lists.mysql.com/cluster Andrew Morgan-5 Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ RE: Problem restarting node What parameters did you change in the config file? Andrew. > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] > Sent: 24 May 2013 19:06 > To: [hidden email] > Subject: Problem restarting node > > Hi! > > I have an stupid problem with my MySQL cluster. It's ver