forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › 6.0 Beta 4 – Error: Mysql Has Gone Away
- This topic is empty.
-
AuthorPosts
-
-
May 9, 2007 at 1:45 am #10326ZyclopsMember
I upgraded to SQLYog Enterprise v6.0 BETA 4 and around every 30 seconds I get the following:
Error Code : 2006
MySQL server has gone away
(0 ms taken)
I've never had this issue before.
Any ideas?
-
May 9, 2007 at 10:50 am #23973peterlaursenParticipant
Please give some details about the server and how you connect (direct, SSH, HTTP).
Does this occur completely random? Is it happening even if there is no activity? Any specific operation that seems to trigger this?
Also try to turn of auto-complete. The error message can came form any running thread/connection – also the autocomplete thread!
-
May 17, 2007 at 4:20 am #23974ZyclopsMemberpeterlaursen wrote on May 9 2007, 08:20 PM:Does this occur completely random? Is it happening even if there is no activity? Any specific operation that seems to trigger this?
It happens after there is no activity (but only for a very short amount of no activity i.e. 3 minutes or less).
peterlaursen wrote on May 9 2007, 08:20 PM:Please give some details about the server and how you connect (direct, SSH, HTTP).All my connections use SSH using a password.
peterlaursen wrote on May 9 2007, 08:20 PM:Also try to turn of auto-complete. The error message can came form any running thread/connection – also the autocomplete thread!I disabled autocomplete, that didn't fix the issue.
-
May 17, 2007 at 8:48 am #23975peterlaursenParticipant
We cannot reproduce. Not on this server (webyog.com) and not locally installed servers either. We tried to have a SSH connection idle for up to 30 minutes. When we after that do some operation from the GUI, the expected behaviour comes promptly.
Ther must be some time-out taking place on the server, so that the connection thread gets disabled. it is very unlikely that this is MySQL that does this (normally MySQL only closes connection threads after several hours – but neverthelesss you should check this setting). More likely it is a SSH (configuration) issue on the server. Do you have an option to check this?
There is no 'keep-alive' command like FTP 'NOOP' in SQL. Actually with SSH and direct connection we do nothing when the connection is idle (with HTTP connection 'keep-alive' packets are sent however, but that is totally controlled by the webserver itself!) an there should be no reason to do it.
One more question: is this happening with 6.0 beta only and not 5.x ?
We can try to reproduce the issue when connected to your server. You will have to arrange temporary remote access then. We do not need access to any data. Just create an empty database and a MySQL user having all privileges to that database only. Also you can create a new SSH/OS user for this so that we cannot access system files and files belonging to other users.
If you want us to try this, you can create a ticket with the necessary connetion details
-
-
AuthorPosts
- You must be logged in to reply to this topic.