- Returning an error from ndbcluster_init() will only
   lead to a warning being printed by the MySQL Server
   and the next plugin to be loaded. I.e the error
   is more or less silently ignored.
 - Handle the problem by printing an error to the log
   and then exit the MySQL Server in case an error is detected
   in ndbcluster_init(). Errors like this should be rare, but
   better to have a disctinct behaviour than allowing 
   the MySQL Server to continue start.
 - Workaround is to start the server "anyway" is to use --skip-ndbcluster 
 - Remove code which tries to cleanup failed ndbcluster_init