This is a very neat way of tackling the issue, keeping most connections fast - but the non-muxable connections (like yours) will be a little bit slower to set up.
That makes multiple SSH connections a bit slower, which isn't ideal, but will fix issues like this. Disable muxing, as the build above does.It seems that muxing is causing a variety of odd errors. Just to eliminate the alternatives, could you possibly download a previous build (3904?) from and just try connecting with that? No need to replace your existing nightly - running the old one from the disk image should be fine!
#MYSQL COULD NOT START SSH TUNNEL MANAGER CODE#
But looking at the code again I can't see any problems at once: the SSH tunnel's initial setup hasn't changed at all, it's only if the SSH tunnel unexpectedly exits before a connection is established that a new retry with some changes are made. The log window being empty is a little odd, but if it's a MySQL connection error, that's possible - I thought the log window was only accessible for SSH errors, unless you kept it open.ĭamien: It's possible that it's connected - the timing certainly seems suspicious.
#MYSQL COULD NOT START SSH TUNNEL MANAGER PRO#
Is there any chance you could try to set up a tunnel manually, and connect Sequel Pro manually through that, and see if that succeeds with two separate connections? So the SSH connection is succeeding, but the subsequent MySQL connection is failing. Mysql5 Ver 14.14 Distrib 5.1.65, for apple-darwin9.8.0 (powerpc) using readline 6.2 $ sw_vers -productVersion xcodebuild -version | head -n1 uname -p ssh -V I expect ssh tunneled two connection to the same host.ĭebug1: Reading configuration data /Users/brad/.ssh/configĭebug1: Reading configuration data /etc/ssh_config What is the expected output? What do you see instead?
0 kommentar(er)
