Le 17.09.2014 17:33, Don Armstrong a écrit :
On Wed, 17 Sep 2014, berenger.morel@neutralite.org wrote:Le 16.09.2014 19:46, Don Armstrong a écrit : >Most likely, you've created a configuration where the machine in >question is unable to access 3306. I do not think so, since the isql command (which uses odbc driver) works, and is configured to use port 3306.In the future, these details would be helpful.
I have said in my first post:
but when it connect through the mysql program, there is no prompt. Through the odbc program (isql), it works fine (we fill mysql's parameters with some greps of the odbc's configuration)
>You can also telnet 10.6.0.3 3306; (or use nc) from the afflicted >machine to see if it even connects to mysql at all.I already did some nc on the target: nc 10.6.0.3 -p 3306. It was how Iguessed the mysql server's version.If you are able to successfully use nc from the target machine, and you can talk to the server, and get a response from it, then it's unlikelyto be the network. [You were able to run nc and get an echo back from the server, right? You should see something like this: $ echo asdf|nc localhost 3306|hexdump -C 00000000 54 00 00 00 0a 35 2e 35 2e 33 38 2d 30 2b 77 68 |T....5.5.38-0+wh| 00000010 65 65 7a 79 31 00 37 03 00 00 49 2e 45 54 55 30 |eezy1.7...I.ETU0| 00000020 2c 2d 00 ff f7 08 02 00 0f 80 15 00 00 00 00 00 |,-..............| 00000030 00 00 00 00 00 3d 2a 57 5b 43 7b 62 58 75 62 6c |.....=*W[C{bXubl| 00000040 77 00 6d 79 73 71 6c 5f 6e 61 74 69 76 65 5f 70 |w.mysql_native_p| 00000050 61 73 73 77 6f 72 64 00 21 00 00 01 ff 84 04 23 |assword.!......#| 00000060 30 38 53 30 31 47 6f 74 20 70 61 63 6b 65 74 73 |08S01Got packets|00000070 20 6f 75 74 20 6f 66 20 6f 72 64 65 72 | out of order|0000007d ]
With hexdump (I must admit I did not used hexdump. Still not very used to that kind of stuff... and anyway I only wanted to know if yes or no the server actually can reply):
00000000 28 00 00 00 0a 33 2e 32 33 2e 34 39 00 5f 2e 03 |(....3.23.49._..| 00000010 00 7b 3c 57 23 43 6b 71 74 00 2c 20 08 02 00 00 |.{<W#Ckqt., ....| 00000020 00 00 00 00 00 00 00 00 00 00 00 00 |............|
0000002c
1: Every 1,0s: netstat -np|grep 3306 Wed Sep 17 14:20:05 2014 tcp 0 0 10.6.0.200:43622 10.6.0.3:3306 TIME_WAIT - tcp 0 0 10.6.0.200:43621 10.6.0.3:3306 ESTABLISHED 21326/isql tcp 0 0 10.6.0.200:43620 10.6.0.3:3306 ESTABLISHED 21312/mysqlThis shows mysql has an established connection to the remote machine. Itdoesn't show at all what the remote machine is doing. Have you examined the logs on the remote machine?
Unfortunately, I does not have access to this remote machine. Which does not help, but I am trying to determine if, yes or no, the problem come from the mysql server or from "my" mysql client.
Considering that we have the same situation on other LANs (I mean, we have a computer that I can access on other LANs where there is a mysql server that we can not administrate too) but the problem can not be reproduced there. From what I have guessed through netcat and uname, the LAN where that problem occur is the oldest: kernel 2.6.22 and mysql server probably at version 3.23.49 (since netcat sends this number when trying to connect). There is another LAN where the kernel is 2.6.26 and mysql server 3.23.58 (still according to nc and uname) which is the second oldest, and there things works perfectly. I have checked the mysql-client's version, and it's the same. Configuration files relating to isql and mysql are also identical, except about the server's address, but I can't see how it could be the problem.
Thanks for help.