[lazylester]

Ritesh wrote on Apr 9 2006, 09:43 PM:

The strange thing is that we are not able to reproduce it at our test servers so kind of difficult to find out 🙁

Ritesh, you mention “servers” and I'm wondering if you are connecting from sqlyog running on one server to a tunnel client on another server? If so, this is not the situation in which I see the problem, mysql and sqlyog are running on the same machine when I see the problem, have you tried this?

Suggest you download Instant Rails, as that's what I'm using, that package includes mysql.

Les

[lazylester]

Next day now (so my computer was rebooted).

beta5 hangs but beta6 (after reinstallation) connects fine. I suppose the key piece of information now is “does beta 6 ever hang”, or has the problem been fixed as a happy but unintentional byproduct of fixing some other problem.

[lazylester]

Ritesh wrote on Apr 8 2006, 05:01 AM:

We have made no changes to the connection code except one issue with HTTP Tunneling which sometimes slowed down the processing.

Ritesh, I was curious about your comment… so I decided to go back and re-install V5.1Beta5, and it's now working! Prior to the installation of beta6, beta5 was “hanging” every time when trying to connect to a local server (although the “test connection” worked).

It may be that the problem still exists in beta6, but the installation process (whether beta5 or beta6) seems to resolve the problem?

stand by for further developments, I guess

[lazylester]

Peter, Ritesh,

I just noticed that beta 6 is available. I tried it and it can connect OK on the local machine. Perhaps the problem has been solved?

[lazylester]

peterlaursen wrote on Apr 7 2006, 06:02 AM:

@Les: Could I ask you to try

1) making a completely fresh install (just install once more to another folder and run from here) and see if the problem persists.

2) renaming the sqlyog.ini file. SQLyog will then start building a fresh one.

OK, I tried both of your suggestion, Peter,

the problem persists under both test conditions

You may duplicate my environment by downloading “Instant Rails”. It doesn't “install” in the traditional way but you just copy it to your disk. The evironment is not changed in any way, so it's very low risk. You can delete it when you're done and your machine will be back to the same as before.

[lazylester]

Ritesh wrote on Apr 6 2006, 10:02 PM:

This is indeed a bug and has been fixed in BETA 6 (official news is out in another half an hour). We are still not able to reproduce the hang problem though.

Anybody who can give us temporary access to the effected server? This is a sincere request as we are just unable to reproduce this error. We have 10 MySQL servers starting from v3.23.58 to 5.1.6 installed at our end and we are able to connect to them without any problem.

Ritesh, I think you may be missing an important piece of information regarding this bug. MySQL is running on my local PC, I don't know how to give you temporary access, it's not a publicly accessible web server. Have you tried using sqlyog locally on one of the servers, not remotely?

Les

[lazylester]

Chris Owens wrote on Apr 6 2006, 04:25 PM:

Clicking test connection returns connection successful for me too. It crashes as soon as I try to really connect.

Chris, when you say “it crashes” do you mean that it just “hangs” and doesn't respond except to the “close” X in the top right corner?

[lazylester]

peterlaursen wrote on Apr 6 2006, 05:56 PM:

That is the crazy thing about this crash phenomenon that it is never reproducable .. 🙁

The lack of repeatability is itself a clue about the nature of the problem!!

[lazylester]

Ritesh, as I noted elsewhere, but also here as it's “on topic”, I have seen the “sudden shutdown” problem when configuring the checkbox to disable autocomplete. The moment I clicked the checkbox, sqlyog vanishes without trace.

This is not repeatable!!

[lazylester]

Ritesh, I have more information for you…

1. The “cannot connect on local machine” problem exists again today. By this I mean that I cannot connect every time to a mySQL server that is running on the same PC as sqlyog. There's no tunnel. However when I test the connection it ALWAY returns “connection successful”. Occasionally (rarely) I DO succeed in connecting.

2. When I cannot connect, sqlyog “hangs” and has to be closed down. I use the X in the top right corner of the sqlyog window, it's still active, even though the title bar at the top of the sqlyog window says SQLyog Enterprise – MySQL GUI (Not Responding).

3. When I shut down mysqlyog, the OS gives me the warning screen and I click “End Now” then the OS gives me the dialog box: “You chose to end the nonresponsive program, SQLyogEnt.exe” and asks if I'd like to “tell Microsoft about this problem”.

4. It sends two files to Microsoft (with an error report?). These files are SQLyogEnt.exe.mdmp and appcompat.txt, I can send you these files if they are of any use to you.

5. I tried to configure sqlyog to disable autocomplete. But the moment I clicked the checkbox to disable autocomplete, sqlyog disappeared suddenly. This is A DIFFERENT problem that is being discussed elsewhere on this forum.

[lazylester]

Ritesh,

I too am not running mySQL on a server but on my own pc (at the moment anyway, of course, this wasn't the case when you and I were working on the base64 problem). So access is not possible.

I'm running Instant Rails, which includes mySQL 4.1.9-max, and I'm using sqlyog 5.1 beta 5 on winxp

It has been well behaved since I rebooted a couple of days ago, so not much new information except to say it happened once and let's watch for it again!

Les

[lazylester]

Ritesh wrote on Apr 3 2006, 10:16 PM:

Do you face the crashing bug other than data tab too?

Hi Ritesh

I'm sorry I'm not very informative on this. When you use the term “data tab” I assume you mean the tab labelled “Table Data” right?

I will try to pay attention to what I click to trigger the shutdown, but it always seem to take me by surprise!

Ritesh wrote on Apr 3 2006, 10:16 PM:

We have fixed many crashing bugs regarding DATA TAB in the last two betas and current RC1 which is under development.

I'm using beta 5, and I'm not clear whether you mean that the “many crashing bugs” are in beta 5 or the fixes are in beta 5. So I wanted you to know that I have beta 5 and I've seen the crash.

Les

[lazylester]

Peter, Ritesh,

I hadn't been around these parts for a few days, and didn't notice that you guys were discussing the problem I had reported. It hasn't (yet) resurfaced. I'll be sure to let you know if it does.

I actually logged on here again to report another prob, but first let me go see if anyone else has seen it (I have a vague recollection I saw someone report this) else I'll start a new thread.

cheers

Les

[lazylester]

Well, today the problem is not present. It seems a pc reboot fixed the problem. Can't say whether that points to sqlyog or the mysql that I'm running. I suppose the problem is now documented on this forum, so if someone else runs into it, we will see a trend.

Suggest you don't pursue this problem until/unless it comes up again. Thanks much

[lazylester]

peterlaursen wrote on Apr 1 2006, 06:25 PM:

Does this bundle include a command-line or another client from where you can do the same? At least you should be able to to so from a Ruby script.

If the MySQL code has been modified not to allow for 'set names' or returns something unexpected, I don't know what could happen.

BTW: Are you able to connect to other servers?

Thanks, Peter,

I do have command line access available and I can connect from the command line, using the sql statements that you have said that sqlyog uses.

I am able to connect to other servers (via tunneling).

how does sqlyog find mysql on my pc?

[Author]

Posts