Hi Christoph,
My best guess is that you have not supplied the connect string to the mysql servers when
starting those. The mysql server on s3 has then used the default connection at localhost
and port 2200 (changed to port 1186 in newer versions) which can be seen by that it is
listed as 127.0.0.1 in the SHOW command.
mysqld --ndb_connectstring="s3.domain.de:2200" other_parameters
should solve this.
http://dev.mysql.com/doc/mysql/en/MySQL_Cluster_Connectstring.html
is the manual info on this topic (although connectstring => ndb_connectstring)
The MySQL server needs to know where to find the cluster. It does so by contacting the
management server. This means that the management server needs to be pointed out
to the MySQL Server which is done by the --ndb_connectstring parameter. The same
applies when you are starting the ndbd nodes but in this case the ndbd node also found
the management server using the default connect string (=localhost:2200).
If that was not your problem then I would check if s1 can ping s3.domain.de, if that is not
the case then /etc/hosts is a place to look, there might also be security issues involved.
Rgrds Mikael
PS: Pls refrain from strong language
Christoph Süß wrote:
> Hi Mikael,
>
> when i put in ndb_mgm and type SHOW i get "not
> connected" from s1 and s2.
>
> And if i create a table on s2 with the engine
> NDBCLUSTER he gives me an error that means theres
> no connection to the cluster.
>
> Where the hell is the problem ?!
>
> Thanks,
> Christoph