Thomas van Gulick wrote:
> I have been buggering the list with my segfault problems for some time, but
> I believe I have found the real problem now. They are easily reproducable on
> my system. Here is my setup:
> utumno, gateway with two ethernet devices, 126.96.36.199 (frontend) and
> 192.168.1.1 (backend). The host itself is called 'utumno'. There is also
> 'angband', on 192.168.1.4, which is on my backend network.
> I have been developping my application on angband for the past months. What
> it does is start 2 threads, which connect to mysqld on utumno and angband
> and perform identical tasks. No problems here, all worked fine. It connects
> using mysql_real_connect with 192.168.1.4 and 188.8.131.52 as hostnames.
> I then moved to utumno for final testing, and the same program segfaults all
> the time. I traced it down to the mysql_real_connect and played with the
> hostname argument. It worked fine for 192.168.1.4, utumno, localhost,
> angband but NOT for 184.108.40.206.
> Since this does not happen on angband, I assume it has to do with the fact I
> have two ethernet devices.
> Hope this helps....
This is definetly an DNS problem.
Perhaps you are asking the wrong nameserver?
Or do you have the IP 220.127.116.11 defined in your hosts file on the utumno server?