Lost Connection In Ssh Tunnel (error 2013)

[uyuni]

This happens only in an SSH tunnel and it happens in all versions incl. 6.0 beta4.

My SSH connection obviously has a timeout and when the timeout has occured and there is no connection anymore SQLYog does not try to connect again. Why not? It would be so much easier if SQLYog immediately reconnects. No I have to close the window and open the connection again. My Queries and my history is gone!

[peterlaursen]

Did you try to 'connect using the same details' from the 'file' menu  (or just CTRL+N) ?

that should connect createing a new window and it should not be necessary to close the existing one!

Quote:

My Queries and my history is gone!

yes, of course if you close the window!  You will have to save the queries (to a file or a favorite).  History can be copied to clipboard and saved to a file.

You claim that SQLyog does not TRY to reconnect.  How can you tell?  Maybe it tries but it cannot?

I will discuss with developers and get a detailed undestanding of how reconnection works, when it works and when it does not and what you can or cannot expect!  I will reply here and/or write a FAQ on this!

[uyuni]

As long as the old window (with the timeout-connection) is not closed I cannot do Ctrl-N because this results in the error attached.

When I click Refresh Object Browser the error 2006-mysql server has gone away appears.

Emilio

[DonQuichote]

I am having the same problem (SQLyog Trial 6.0 beta4)

– New connection.

On the main tab, I leave the defaults. (which is ok. These credentials exist on the remote server)

On the SSH tab, I give the remote location, with the same username and password I would normally use with putty.

As local port, I choose 2202.

When I click “test connection”, I get the error “Connection lost during query (2013)”.

Further test. I cancel the open connection dialog and start putty.

I log in with the usual credentials.

I click “change settings…”->Tunnels.

I create a port forward: 127.0.0.1:3306 is forwarded to 2202.

I return to SQLyog and log in with a new connection, this time without enabling SSH and with port 2202.

No problems whatsoever. I see the databases and can access the data.

Am I doing anything wrong?

[peterlaursen]

I cananot see anything wrong!

Could you arrange remote acces to that server.  We only need access to a 'silly' databases.

Do not write details here but create a ticket with details

[DonQuichote]

peterlaursen wrote on May 8 2007, 01:38 PM:

I cananot see anything wrong!

Could you arrange remote acces to that server. We only need access to a 'silly' databases.

Do not write details here but create a ticket with details

Even better: I just found out what the problem was. The remote database is on a linux server, where localhost is not the same as 127.0.0.1. So replacing the default “localhost” with “127.0.0.1” solved the problem.

[peterlaursen]

OK .. thx for the feedback.

Yes we should always remember that a computer can have a non-typical host's configuration!

[DonQuichote]

peterlaursen wrote on May 9 2007, 11:49 AM:

Yes we should always remember that a computer can have a non-typical host's configuration!

It's a Linux thing. “localhost” refers to a “named pipe”, whereas “127.0.0.1” will result in using a tcp connection. I should have realised this earlier.

[peterlaursen]

There are no 'named pipes' in Linux I think.  But there are 'sockets'. I do think however some distros ((k/x)ububtu ??)  has 'cloned' the Windows 'named pipes' concept.

It also depends on the client type.  With PHP 'localhost' will force a socket connection, 127.0.0.1 a tcp-connection. (the host file is overridden).  This should not be the case with the C-API as compiled into SQLyog and SJA.

But if you know more about those issues than I (and that would not be hard!) 

you are welcome to propose improvements to the FAQ's on connection issues!

[DonQuichote]

peterlaursen wrote on May 10 2007, 10:33 AM:

But if you know more about those issues than I (and that would not be hard!)

you are welcome to propose improvements to the FAQ's on connection issues!

I am far from an expert also, but I encountered some thing about it in the MySQL documentation: http://dev.mysql.com/doc/refman/5.1/en/can…-to-server.html

I hope it makes sense.

[uyuni]

This topic is still not solved (sqlyog 6.05).

When my connection over an SSH-tunnel is idle for 10 minutes I get the message “Error No 2006. MySQL server has gone away.”

I cannot reconnect with 'connect using the same details' from the 'file' menu because the local port is already used for SSH-forwarding.

It would be very nice if you could detect this error internally and close and reconnect the connection automatically!

Emilio

[peterlaursen]

You will find another recent discussion here if you search a little!

The way we currently reconnect with SSH will work if connection is lost between mysql and sshd. Not if it is lost between plink and sshd. We will research if/how we could possible re-instantiate plink too when connection is SSH type.

[rikdavis]

My situation is similar, but even more bewildering.

At my company, I just had our network admin clone one of our existing servers. (Of which I can connect to without any issues)

On this new clone, different internal and external IP, I can connect to the server via SSH using Putty and get in just fine. If I try to use the exact same credentials on SqlYog, I get the following error;

SSH Error: Unable to open connection:

Host does not exist

I find this quite disturbing considering that all of my other connections in SqlYog work just fine. Including the one to the system that the clone was made from.

• iptables are wide open
• No firewall on my workstation
• No network firewall rules that would prevent this new server from being seen
• Co-workers can connect using their SqlYogs (Version differences [mine] = 10.51, [theirs] = 10.11)

I'm wondering if this is a bug as of this latest release as I have never had any issues prior to upgrading to this version.

[sathish]

Hello,

You get this error only when your SSH host address is wrong. Could you please double check your connection details or enter the connection details again in SSH tab and MySQL tab in the connection manager. If you are still having issues we would like to have a shared session in order to check this issue. You can create a private ticket by sending a mail to [email protected].

Regards,

Sathish

[Author]

Posts