From: Gowrynath Sivaganeshamoorthy Date: July 30 2004 9:18am Subject: Fault ID: 2350 (ndbd: Could not fetch configuration/invalid configuration) List-Archive: http://lists.mysql.com/cluster/225 Message-Id: <20040730111840.A17344@srv01.cluenet.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii folks, I've downloaded mysql-4.1.4-beta-nightly-20040727 and installed, as described in the cluster for mysql users documentation on a linux (redhat 9, 2.4.20-8smp) system. my config.ini: [COMPUTER] Id:1 HostName: localhost ByteOrder: Little [MGM] Id:1 ExecuteOnComputer: 1 [DB] Id: 2 NoOfReplicas: 1 ExecuteOnComputer: 1 FileSystemPath: /export/home/gowry/MySQL/ndb_data1 [API] Id: 3 ExecuteOnComputer: 1 [TCP DEFAULT] PortNumber: 10002 my Ndb.cfg: nodeid=1 host=127.0.0.1:2200 starting ndb_mgmd works, as it seems: $ /usr/local/mysql/libexec/ndb_mgmd -c config.ini NDB Cluster Management Server. Version 3.5.0 (beta) Command port: 2200, Statistics port: 0 NDB> but when I try to start ndbd, the following happens: $ /usr/local/mysql/libexec/ndbd Error handler shutting down system Error handler shutdown completed - exiting $ the error.log says: Date/Time: Friday 30 July 2004 - 11:16:10 Type of error: error Message: Invalid Configuration fetched from Management Server Fault ID: 2350 Problem data: Could not fetch configuration/invalid configuration Object of reference: Supplied node type(0) and config node type(2) don't match ProgramName: NDB Kernel ProcessID: 23410 TraceFile: NDB_TraceFile_1.trace ***EOM*** the trace file looks like: $ cat NDB_TraceFile_1.trace JAM CONTENTS up->down left->right ?=not block entry BLOCK ADDR ADDR ADDR ADDR ADDR ADDR ADDR ADDR BLOCK#0?000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 000000 [... zero's ...] any idea how to fix this? seems like that the process can't handle the configuration it gets from the management server? is my configuration not sane enough or something? thanks, --g.