From: Wouter de Jong
Date: September 2 2004 8:45am
Subject: Re: Can't Init  Database
List-Archive: http://lists.mysql.com/cluster/546
Message-Id: <20040902084529.GB25559@widexs.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Thu, Sep 02, 2004 at 12:35:18PM +0530, Sharad Maloo wrote:
> 
> Hello,

Hi Sharad,

> 
> I am quite new to the cluster list, excuse me if this has been posted 
> earlier. 
> 
> I get this error when I run the mysqld_safe process. 
> ----
> frm the .err file. 

<..errmsg..>

> ------- 

<..config..>

For some reason, I have the same:

040902 09:18:33  mysqld started
040902  9:18:33  InnoDB: Started; log sequence number 0 43634


040902  9:19:34  Can't init databases
040902  9:19:34  Aborting

040902  9:19:34  InnoDB: Starting shutdown...
040902  9:19:37  InnoDB: Shutdown completed; log sequence number 0 43634
040902  9:19:37  /usr/local/mysql41/libexec/mysqld: Shutdown complete

040902 09:19:42  mysqld ended


I've started the ndb_mgmd first, and then my ndbd nodes.
Here's the result:

NDB> show
Cluster Configuration
---------------------
4 NDB Node(s)
DB node:        8  (Version: 3.5.0)
DB node:        4  (Version: 3.5.0)
DB node:        6  (Version: 3.5.0)
DB node:        2  (Version: 3.5.0)

2 API Node(s)
API node:       3  (not connected) 
API node:       5  (not connected) 

1 MGM Node(s)
MGM node:       1  (Version: 3.5.0)


The API Nodes just don't come up, and are bailing out with above error message.
Note that this is with a TCP-transport, cause I have my Management 
node running on a dedicated machine. The API-nodes run on the same servers (2) as 
the NDB-nodes.

> ------------
> 
> Any inputs will be appreciated.

I don't have a solution as of yet, hopefully someone else :)
 
> Thanks aprior,
> Sharad Maloo

-- 
WideXS                          http://www.widexs.nl
Wouter de Jong                  System-Administrator
Tel +31 (0)23 5698070           Fax +31 (0)23 5698099
Bijlmermeerstraat 62,           2131 HG  HOOFDDORP, NL