Turns out my issue was a mis-configured resolv.conf file that the sys
admin here fixed.
But other things I was told by MySQL was:
1) make sure the SQL node can access DNS server
2) you can start mysql on the SQL node using the skip-name-resolve
option will will bypass DNS lookups.
-----Original Message-----
From: Tom.Hanlon@stripped [mailto:Tom.Hanlon@stripped]
Sent: Tuesday, October 06, 2009 10:05 PM
To: Mike Kirby
Cc: cluster@stripped
Subject: Re: cant connect remotely to cluster 7.07
I also experienced this issue. I will read the bug report.
Mike Kirby wrote:
> I upgraded to 5.1.35-ndb-7.0.7 today and everything seemed okay. I
> could connect to the db locally. But then tried to connect remotely
and
> got the error: ERROR 1042 (HY000): Can't get hostname for your
address.
>
>
>
> I read one bug report that mentioned the same error and I guess the
> resolution was to add the hostname and IP of the box I am connecting
> from, into the hosts file on the SQL node. This seemed to resolve the
> issue. But this is really not a good solution and curious is there
are
> other known workarounds. This works okay for the application, since
> that IP and hostname wont change, but I also have developer who need
to
> connect from there machine for running adhoc queries etc. Not to
> mention, in my prod env. we have many more hosts that run the
> application, and this could turn out to be a nightmare.
>
>
>
> Anyone experience this issue or know of any other workarounds?
>
>
>
> Thanks
>
> Mike
>
>
