Sqlyog Reconnected

[SJet]

Since some time ( probably it was after upgrading to onr eofthe latest versions ) I and my colleague have the same problem.

After some time of inactivity Sqlyog is freezing after I try to run some query again.

In the history I can see

/*[13:19:44][76627 ms] SQLyog reconnected */

So more then one minute every time and so many times a day.

Very annoying.

Is there some property to change?

I could not find it.

According to one of topics I ran

SET @@session.wait_timeout = 28800

But I don't think that it is MySQL issue.

[peterlaursen]

Please execute “SHOW GLOBAL VARIABLES LIKE 'wait_timeout'”.  What does it return? My guess is that 'wait_timeout' setting on the server is low.  But it can of course also simply be connectivity issue.

However it seems you are using a rather old SQLyog version. If 'wait_timeout' is the reason you can work around it. Please read release notes for 8.13:

http://www.webyog.com/blog/2009/08/14/sqlyog-813-has-been-released/

“Added an option for user to specify the timeout setting for the session (note: it will work with MySQL 4.1 and up only as earlier versions do not support SESSION variables). Please see detailed note below.”

… and also this Blog:

http://www.webyog.com/blog/2009/09/02/“mysql-server-has-gone-away”-part-2-session-timeout/

[SJet]

'peterlaursen' wrote on '19:

Please execute “SHOW GLOBAL VARIABLES LIKE 'wait_timeout'”.  What does it return? My guess is that 'wait_timeout' setting on the server is low.  But it can of course also simply be connectivity issue.

However it seems you are using a rather old SQLyog version. If 'wait_timeout' is the reason you can work around it. Please read release notes for 8.13:

http://www.webyog.com/blog/2009/08/14/sqlyog-813-has-been-released/

“Added an option for user to specify the timeout setting for the session (note: it will work with MySQL 4.1 and up only as earlier versions do not support SESSION variables). Please see detailed note below.”

… and also this Blog:

http://www.webyog.com/blog/2009/09/02/“mysql-server-has-gone-away”-part-2-session-timeout/

Thank you for your reply.

SHOW GLOBAL VARIABLES LIKE 'wait_timeout' returns 28800

Also I'm using recent version 8.18.

[peterlaursen]

Are you using SSH-tunnel?

[SJet]

'peterlaursen' wrote on '20:

Are you using SSH-tunnel?

Not for the servers in question.

And my colleague does not use it at all.

[nithin]

Hello,

Please tell what type of connection you use: direct , remote or HTTP(If you use Enterprise version)?

MySQL server version?

Can you tell which version you were using before 8.18? And can you confirm you never faced this issue before?

And you no need to execute this query 'SET @@session.wait_timeout = 28800' manually. SQLyog provides this option while connecting. In Connection window you can see a group 'Session Idle timeout' and you can enter this 28800 to the textbox.

Thank you

Nithin

[nithin]

Also

After some time of inactivity SqLyog always got reconnected for any query?

If so can you try these queries and confirm the freezing happens all these.

(make sure while connecting in connection dialog you set the 'Session Idle Timeout is 28000')

i. SELECT 1;

ii. SELECT * from ;

iii. SELECT * from .;

Please check the 'History' whether 'Reconnected' is added for all these queries

Thank you

Nithin

[SJet]

'nithin' wrote on '21:

Also

After some time of inactivity SqLyog always got reconnected for any query?

If so can you try these queries and confirm the freezing happens all these.

(make sure while connecting in connection dialog you set the 'Session Idle Timeout is 28000')

i. SELECT 1;

ii. SELECT * from ;

iii. SELECT * from .;

Please check the 'History' whether 'Reconnected' is added for all these queries

Thank you

Nithin

Hello,

Even with SELECT 1;

I get reconnect

/*[9:51:50][81417 ms] SQLyog reconnected */

/*[9:51:50][ 15 ms]*/ SELECT 1;

So probably there is no need to test other queries.

It began still with the older version ( I guess 6.5.4 )

And remained after upgrade to 8.18.

About Mysql version. As I said the same problem we have with different servers.

These are the versions:

5.0.32-Debian_7etch8-log

5.0.51a-24+lenny2

One of the servers is on intranet , that exclude that it is a firewall issue.

I will try to use SSH tunnel now and will report the result.

[SJet]

'SJet' wrote on '21:

Hello,

Even with SELECT 1;

I get reconnect

/*[9:51:50][81417 ms] SQLyog reconnected */

/*[9:51:50][ 15 ms]*/ SELECT 1;

So probably there is no need to test other queries.

It began still with the older version ( I guess 6.5.4 )

And remained after upgrade to 8.18.

About Mysql version. As I said the same problem we have with different servers.

These are the versions:

5.0.32-Debian_7etch8-log

5.0.51a-24+lenny2

One of the servers is on intranet , that exclude that it is a firewall issue.

I will try to use SSH tunnel now and will report the result.

SSH tunneling did not help.

Same:

/*[11:00:18][77142 ms] SQLyog reconnected */

[peterlaursen]

We need to analyze the issue. Since 8.13 this error will only rarely come in HISTORY if SSH-tunnelling is not used.

We will provide you a special build that logs details like which error of MySQL caused this reconnection, query executed. Since you are getting this issue without SSH, we will provide you a Community build. Download from: 

http://www.webyog.com/downloads/betas/not_released/SQLyog821.3Community.exe

(note that you do not need overwrite existing installation.  You can install to a seperate folder)

Please reproduce the case and attach the log file created.

The log file name is (for unknown reason) 'slow_log.log' and it is stored in users 'AppData' folder (where also the sqlyog.ini file is).

You may create a ticket for privacy, of course.

[SJet]

'peterlaursen' wrote on '21:

We need to analyze the issue. Since 8.13 this error will only rarely come in HISTORY if SSH-tunnelling is not used.

We will provide you a special build that logs details like which error of MySQL caused this reconnection, query executed. Since you are getting this issue without SSH, we will provide you a Community build. Download from: 

http://www.webyog.com/downloads/betas/not_released/SQLyog821.3Community.exe

(note that you do not need overwrite existing installation.  You can install to a seperate folder)

Please reproduce the case and attach the log file created.

The log file name is (for unknown reason) 'slow_log.log' and it is stored in users 'AppData' folder (where also the sqlyog.ini file is).

You may create a ticket for privacy, of course.

Thank you.

I've insatalled it and will inform you further.

[SJet]

'peterlaursen' wrote on '21:

We need to analyze the issue. Since 8.13 this error will only rarely come in HISTORY if SSH-tunnelling is not used.

We will provide you a special build that logs details like which error of MySQL caused this reconnection, query executed. Since you are getting this issue without SSH, we will provide you a Community build. Download from: 

http://www.webyog.com/downloads/betas/not_released/SQLyog821.3Community.exe

(note that you do not need overwrite existing installation.  You can install to a seperate folder)

Please reproduce the case and attach the log file created.

The log file name is (for unknown reason) 'slow_log.log' and it is stored in users 'AppData' folder (where also the sqlyog.ini file is).

You may create a ticket for privacy, of course.

So far the content of the file is:

______________ select 1 Error code = 2013 querycount = 0 SQLyog reconnected

______________ select 1 Error code = 2013 querycount = 0 SQLyog reconnected

______________ select 1 Error code = 2013 querycount = 0 SQLyog reconnected

While history is

/*[15:38:49][ 16 ms]*/ SET NAMES 'utf8';

/*[15:38:49][ 0 ms]*/ SET sql_mode='';

/*[15:38:49][ 0 ms]*/ SHOW DATABASES;

/*[15:38:52][ 0 ms]*/ USE `SIS`;

/*[15:38:57][ 0 ms]*/ SELECT 1;

/*[15:45:40][ 0 ms]*/ SELECT 1;

/*[15:45:43][ 16 ms]*/ SELECT 1;

/*[15:57:58][76503 ms] SQLyog reconnected */

/*[15:57:58][ 0 ms]*/ SELECT 1;

/*[16:10:15][76503 ms] SQLyog reconnected */

/*[16:10:15][ 0 ms]*/ SELECT 1;

/*[16:50:44][76519 ms] SQLyog reconnected */

/*[16:50:44][ 0 ms]*/ SELECT 1;

[peterlaursen]

error 2013 is described in MySQL manual here: http://dev.mysql.com/doc/refman/5.0/en/error-messages-client.html#error_cr_server_lost

You tell that this happened after upgrade – but are you sure that not the old version has the same problem? If you have the older version (btw: what was it?) could you try install it again?

You can also tell the server version (though probably not important)

[SJet]

'SJet' wrote on '21:

It began still with the older version ( I guess 6.5.4 )

And remained after upgrade to 8.18.

About Mysql version. As I said the same problem we have with different servers.

These are the versions:

5.0.32-Debian_7etch8-log

5.0.51a-24+lenny2

[nithin]

Can you check whether the server got restarted or not when it show 'Reconnected' for a query? You can confirm it from the 'Info tab', select the Server(root) node in Object browser(left pane) and select the Info tab in HTML mode. It gives the server Up-time information.

see the image attached.

[SJet]

'nithin' wrote on '22:

Can you check whether the server got restarted or not when it show 'Reconnected' for a query? You can confirm it from the 'Info tab', select the Server(root) node in Object browser(left pane) and select the Info tab in HTML mode. It gives the server Up-time information.

see the image attached.

MySQL Server: 5.0.32-Debian_7etch8-log, Running for: 7 days 23 hrs 50 mins 15 secs

MySQL Server: 5.0.51a-24+lenny2, Running for: 83 days 14 hrs 22 mins 22 secs

[peterlaursen]

The connection to the server gets closed before result is received. Even with very simple queries. The error is generated by the MySQL client (C-API/libmysql) compiled inth SQLyog. Note that this means that is is official MySQL code that returns the error – not our code (all 4 digit errors are MySQL serrros – 1xxx are server errors and 2xxx are client errors. Any client would face same issue when connecting to/from same host.  Could you verify by trying another client (Query Browser for instance) on same machine as SQLyog ?

I do not think it is an issue with MySQL, but rather a networking issue.  Do you know of any changes in the setup?  New routers/switches/firmware etc. ? Same host as always? 

Also if you have an option to try another server could you see if it repeats itself with another server.

If we can have access to this server we can try from our end.  We will net need access to data.  Create an empty database (or with a small silly table we can test with) and a user who only has access to this database.  Post authentication details in a ticket for privacy.

By I am as sure as can be, that this is not an issue with SQLyog, and it is accidental that the problem occurs at about same time as you upgrade the program. This should rather be communicated with the support on the host (but before doing so it is a good idea to verify that not only a single program is affected).

A few links to other people facing this problem (but you will find lots similar):

http://www.vbulletin.com/forum/showthread.php?48697-Error-2013-but-server-up-for-6-days&postid=310265

http://veblog.wordpress.com/2007/07/31/mysql-error-2013/

[SJet]

Unfortunately I did not post the follow-up.

After some investigation we found the evil. It is Kaspersky antivirus. Anyhow when we turn it off the problem does not come up.

Still we did not found which exactly setting causes the reconnect.

So for the time being one turns Kaspersky off. Other learn to live with reconnections.

[Author]

Posts