distal-attribute
distal-attribute
distal-attribute
distal-attribute

connection duration

JamieEff posted 1 year ago in General
Hey

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
ansgar posted 1 year ago
What reason does the server give you for that disconnect? Isn't there a real error message in the SQL log?
JamieEff posted 1 year ago
I dont get a reason...as you can see from the screenshot, it becomes disconnected but the time period is incredibly short...
JamieEff posted 1 year ago
sorry, heres the link to the screenshotL http://imgur.com/a0gbVZi
ansgar posted 1 year ago
Please scroll to the left before making a screeny. I assume there is some disconnect message.
JamieEff posted 1 year ago
sorry, do you mean like this? http://imgur.com/d7fFPjd
ansgar posted 1 year ago
Yes, thank you.

I was hoping there was more information than "Connection closed..". Could it be the previous query causes your disconnect?

SHOW CREATE TABLE db.service_contents



Please try manually, in a query tab.
ansgar posted 1 year ago
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)
JamieEff posted 1 year ago
sorry ansgar .... you'll have to give me some more info on what I need to do / where I need to put it etc

this is the result of the manual attempt: http://imgur.com/atiKytP

ansgar posted 1 year ago
You have blacked out your database name, so I called it "db"smileYou should of course replace "db" with your database name where the table "service_contents" resides.

The libmysql.dll needs to be placed into the folder where you have installed HeidiSQL. Exit HeidiSQL before doing that.
JamieEff posted 1 year ago
oops sorry here you go: http://imgur.com/4QRvjlg
kalvaro posted 1 year ago
@JamieEff, please note you can just use the clipboard to copy text from the log pane (Ctrl+C, Ctrl+V).
JamieEff posted 1 year ago

ansgar wrote: 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....
JamieEff posted 1 year ago
hey ansgar... just wondering if you have had a chance to investigate this?
ansgar posted 1 year ago
I cannot reproduce that all here, on various computers and different MySQL servers.

So I guess we have an issue with your particular server here. Please try out if you get the same disconnect when you're on a different MySQL server. Hope you have one available?
JamieEff posted 1 year ago
nope well.. the only other one I have is localhost that I use xampp on... will that do?
JamieEff posted 1 year ago
i tred localhost and it doesnt happen on that... but it didnt happen on my live server until I updated... can I get a rollback to an earlier version? I tried 4521 but it still happened in that version so would neeed to be earlier than that....
ansgar posted 1 year ago
Watch out for previous builds on the download page - I'm always keeping the previous 30 build files.

ansgar posted 1 year ago
You could be so nice and tell us the version of the MySQL server on which you encounter the disconnects.
JamieEff posted 1 year ago
sure, here it is: MySQL version 5.1.59-rel13.0-log

also FYI, I have managed to install 8.0.0.4521 and this is not experiencing the disconnect that I have had in the recent version(s)
ansgar posted 1 year ago
Ah, makes sense. I assume you have downloaded the installer, not just the heidisql.exe?

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.
JamieEff posted 1 year ago

JamieEff wrote:

ansgar wrote: 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)
JamieEff posted 1 year ago
ok... just tried doing what you suggested and its back to disconnecting....
ansgar posted 1 year ago
Come on, be more exact please. HeidiSQL revision and libmysql.dll version (can be checked by hovering your mouse over the status bar panel with the MySQL version on it)
JamieEff posted 1 year ago
ansgar.... just because you know your way around how to debug somethign doesnt mean I do... I am trying to give you the info but if I just h appoen not to give you all the info its not because I am trying to be awkward.......its because I do,nt know what I need to post

OK?

JamieEff posted 1 year ago
8.1.0.4545
5.5.32-MariaDB
ansgar posted 1 year ago
Being most detailed when asking for help is a basic rule in a forum. So..

5.5.32 should have been ok as you reported r4521 works for you. Shit.

When you now download the heidisql.exe build of r4521 and put it into your program directory it works?

JamieEff posted 1 year ago
4521 with 5.5.32-MariaDB works fine
ansgar posted 1 year ago
Super. I should now check what else could have caused your disconnection problem. Gimme some time please.
Eric_Allison posted 10 months ago
I also have this exact issue. Seems to work fine with a local mySQL database, but when working on a remote DB, if I run a query, or attempt to view the "Data" tab, I get the following message in the log:
/* 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.
teells85 posted 9 months ago
I am also having this same issue. I also followed the following recommendations and to no avail.

ansgar wrote: 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.
ansgar posted 9 months ago
"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.
Eric_Allison posted 9 months ago
I've also tried the above older versions of libmysql.dll with no success.

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) ;)
teells85 posted 9 months ago

ansgar wrote: "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.
af888 posted 7 months ago
I am having the same issue!! Any suggestions?

I am running the latest version of Heidi SQL on 64 bit system with no libmysql.dll changes and when I view the data page, it is disconnecting within 10 seconds.
AdmiralNines posted 6 months ago
Just wanted to throw my hat in the ring. Same problem. Eventually I want to pull away from Hostgator as they're downtime has been terrible this last year and their scruples (sneaking ads in, shutting sites down without warning) have become questionable.

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.

Paskainos posted 5 months ago
I struggled with this issue in recent months and had tried everything outlined above, none of which worked to fix the problem. Here's what worked: simply increasing the

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.
Paskainos posted 5 months ago
It's also probably worth mentioning, if you change variables in my.cnf, remember to restart MySQL for the change(s) to take effect.

Please login to leave a reply, or register at first.