connection duration
I have noticed with the recent update to 8.1.0.4545 that when connected to a database (particularly in the 'Data' view of a table) that it disconnects very quickly.
is there any way to change this?
Thanks
J
Or even this one: http://heidisql.googlecode.com/svn-history/r4244/trunk/out/libmysql.dll (MariaDB 5.2.10)
this is the result of the manual attempt: http://imgur.com/atiKytP
The libmysql.dll needs to be placed into the folder where you have installed HeidiSQL. Exit HeidiSQL before doing that.
Also, you could try to use an older libmysql.dll. There are quite a few situations in which that file shows some incompatibility. Perhaps this one: http://heidisql.googlecode.com/svn-history/r4245/trunk/out/libmysql.dll (C 6.0.2)
Or even this one: http://heidisql.googlecode.com/svn-history/r4244/trunk/out/libmysql.dll (MariaDB 5.2.10)
neither of these have helped I'm afraid....
The r4521 installer has a newer libmysql.dll than the 8.1 release has. In r4532 I downgraded that libmysql to fix issue #3343 (malformed packet error). In your case, the older libmysql is causing your disconnect for some reason.
I asked you to exchange your libmsql.dll above, but I guess you did not place the downloaded .dll into your c:\program files\heidisql\ directory.
After r4521, there was no connection driver specific modification to the HeidiSQL code. So I'm quite sure the libmysql was causing your disconnects.
If you now make a copy of your current libmysql.dll in your HeidiSQL directory, then install HeidiSQL 8.1 again, overwrite the libmysql.dll with your copy afterwards, you should be able to get all running.
Also, you could try to use an older libmysql.dll. There are quite a few situations in which that file shows some incompatibility. Perhaps this one: http://heidisql.googlecode.com/svn-history/r4245/trunk/out/libmysql.dll (C 6.0.2)
Or even this one: http://heidisql.googlecode.com/svn-history/r4244/trunk/out/libmysql.dll (MariaDB 5.2.10)
neither of these have helped I'm afraid....
Hey ansgar, as you can see from the above quote, I did try that after you asked me too but it didnt work.
I will make a copy of my dll and try that route now
thanks for all your help (small donation made btw)
OK?
/* Connection to xxx.xxx.xxx.xxx closed at 2014-01-10 08:18:43 */
I can re-run my query and it will connect again, but 10 seconds after the query runs, the connection is closed again making it difficult/impossible to work with the query results as the data gets grayed out upon disconnect.
Also, you could try to use an older libmysql.dll. There are quite a few situations in which that file shows some incompatibility. Perhaps this one: http://heidisql.googlecode.com/svn-history/r4245/trunk/out/libmysql.dll (C 6.0.2)
Or even this one: http://heidisql.googlecode.com/svn-history/r4244/trunk/out/libmysql.dll (MariaDB 5.2.10)
When trying this I get the following Error: "Cannot find a usable libmysql.dll. Please launch heidisql.exe from the directory where you have installed it." which does provides the same error when attempting to connect to the remote database.
I am currently running HeidiSQL 8.3.0.4718 with libmysql.dll 5.3.12.3621.
Using Heidi with a remote server is very difficult with it like this.
I'm not sure if it's related or just a coincidence, but it seems the disconnects seem to happen only when Heidi's log shows something to do with Percona (It's a MySQL DB on HostGator):
/* Connecting to 192.xxx.xxx.xxx via Percona (TCP/IP), username xxxxxxxxx, using password: Yes ... */
I've tried connecting to those hosts with other MySQL GUI tools and none disconnect like Heidi does. (However, I put up with the disconnect because Heidi is waaay better than the alternatives in my opinion) ;)
"Cannot find a usable libmysql.dll" means the dll is a) not a libmysql at all but a totally wrong one, or b) (most likely for you) 32bit and you're running HeidiSQL 64bit, or vice versa. The above dll links are older than the point where Heidi got available as 64bit executable.
Ok, I was attempting to run them on a 32bit OS, so that explains that. I agree with you Eric_Allison that heidi is a great tool and I guess either I'll put up with the disconnect or migrate from a hostgator shared webhost to my own vps.
But until I do, this disconnect issue makes HeidiSQL completely unusuable. I don't even get enough time to make a single edit. Barely enough time to even get to see the data. It shuts me out in seconds.
interactive_timeout
variable (either in my.cnf or via phpMyAdmin ยป Variables, etc.).My
interactive_timeout
was set to 10 (i.e. 10 seconds) and I bumped it to the default - 28800 (8 hours) per the documentation:http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_interactive_timeout
Also, while I was in my.cnf, I bumped the
wait_timeout
up from 30 to the default 28800 also, for good measure based on their related nature per the documentation:http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar_wait_timeout
It's perhaps important to note however, increasing the
interactive_timeout
variable alone fixed the problem.Lastly, it was a Hostgator VPS account on which the issue occured. But I find that point merely incidental to the underlying issue. I mention it only for others who've encountered the same issue.
Please login to leave a reply, or register at first.