#1914 SSH Tunnel - not enough time allowed to make Plink connection

[Anonymous]

Originally created by: charles....@gmail.com

What exact steps will reproduce the problem?
1. Define a SSH Tunnel to server with a slow connection
2. Open the connection

What was the expected output?
Expected the MySQL connection to occur after the plink connection has been
made.

What happened instead?
The MySQL connection is attempted whilst plink is still negotiating,
causing Heidi to return a SQL connection error.

Suggested fix (optional)?
Suggested by anse on the forum: "There should be some loop which detects
if plink is still running."

Note that prior to the release of 5.1, the first connection attempt failed
whilst the second succeeded.  I believe this was because after the first
failed attempt, plink was left running allowing enough time for it to
connect so then the second attempt would work.  5.1 implemented a change
that forced plink.exe to close after a failed MySQL connection so now I
can't connect at all.

Version used?
HeidiSQL revision: 5.1.0.3297
MySQL Server version: 5.0.67
Operating system: Windows XP

[Anonymous]

Originally posted by: a...@anse.de

Hmm.. Not sure how to fix that. The very first to be done is of course making the
plink window visible again.

Then, plink asks me "Store key in cache? (y/n)". Doing nothing here,
GetExitCodeProcess() on the plink process returns 259 (= "No more data available").
Looks reasonable so far. Then, if I press "y<Return>", plink establishes the
connection. But the ExitCode is still 259, making it impossible to detect for Heidi
if plink was successful. Hmm...

Labels: Severity-Broken
Status: Accepted

[Anonymous]

Originally posted by: a...@anse.de

Btw, here's a listing of all exitcodes:
http://www.hiteksoftware.com/knowledge/articles/049.htm

[Anonymous]

Originally posted by: b...@mbpirkle.com

Is it possible to increase the timeout?  While perhaps not a 100% fix, it might give some of us a better chance.  Especially if this is as simple as bumping a constant, it the attempt would be greatly appreciated.

In my experience, I can usually try a few times and eventually get a connection.  However, if my Internet connection is being used for much else, I often can't connect at all.  (I work remotely from the company servers, using a rather slow DSL connection shared by two other users.  Unfortunately, that's the best Internet access available in my location.)

Thanks!

[Anonymous]

Originally posted by: a...@anse.de

Of course - [r3508] increases the wait interval from 1 to 4 seconds. Should help out until we find a working solution.

[Anonymous]

Originally posted by: b...@mbpirkle.com

Thank you - that did the trick for me!

[Anonymous]

Originally posted by: jan.nigg...@gmail.com

Can't test at the moment, but I'm confident that it's fixed. Thank you!

[Anonymous]

Originally posted by: franz.eh...@googlemail.com

works for me the most of the time, had some sort of time out only once.

[Anonymous]

Originally posted by: a...@anse.de

Thanks for the update. I'll close this issue although I the solution is not very nice. But I'm lacking a better idea and if that workaround does it, ho-hum.

Status: Fixed