Re: Auto installer stuck at "Starting node 2 (ndbmtd)" with 29%

[Mikael Ronström]

No need to wait, it won't start if it hasn't come up after 3 hours
in an initial start.

The most common reason for this type of problem is that there is
a firewall preventing communication between node id 1 and 2.

If you have firewalls it is usually a good idea to set
ServerPort in NDBD section to a port number (I use 11860) and
ensure that this is open in the firewalls.

Since you use MCC to start, it is possible that it is already using
11860 for ServerPort. So then it is sufficient to ensure that this
port is open.