Brand new node in established cluster stuck at phase 2

[Darren Landrum]

Okay, after the adventure in solving my last problem, this will hopefully be the last time I need to bug any of you.

Now, the new cluster node (replacing an old node, by the way) is stuck in startup phase 2, which reading the docs, means it's looking for an arbitrator node. Since the rest of the cluster is up, hasn't this election already happened?

I started the new NDB node with the --initial flag. Perhaps I didn't want this? Should I start it as normal?

Here's the outputs so far...

Cluster management node log:

-----
2006-02-20 13:09:25 [MgmSrvr] INFO -- Mgmt server state: nodeid 3 reserved for ip x.x.x.58, m_reserved_nodes 0000000000001e0a.
2006-02-20 13:09:25 [MgmSrvr] INFO -- Node 1: Node 3 Connected
2006-02-20 13:09:26 [MgmSrvr] INFO -- Mgmt server state: nodeid 3 freed, m_reserved_nodes 0000000000001e02.
2006-02-20 13:09:28 [MgmSrvr] INFO -- Node 3: Start phase 0 completed
2006-02-20 13:09:28 [MgmSrvr] INFO -- Node 3: Communication to Node 4 opened
2006-02-20 13:09:28 [MgmSrvr] INFO -- Node 3: Communication to Node 5 opened
2006-02-20 13:09:28 [MgmSrvr] INFO -- Node 3: Communication to Node 6 opened
2006-02-20 13:10:00 [MgmSrvr] INFO -- Node 3: Start phase 1 completed
-----

Here's the command line's output on the node server itself:

-----
node_srv sbin # ndbd-500 --initial --nodaemon
2006-02-20 13:09:25 [ndbd] INFO -- Angel pid: 2309 ndb pid: 24287
2006-02-20 13:09:25 [ndbd] INFO -- NDB Cluster -- DB node 3
2006-02-20 13:09:25 [ndbd] INFO -- Version 5.0.18 --
2006-02-20 13:09:25 [ndbd] INFO -- Configuration fetched at x.x.x.57 port 1186
2006-02-20 13:09:25 [ndbd] INFO -- Start initiated (version 5.0.18)
-----

That's where it's currently hung at. Thank you all for your help.