[c64audio]

peterlaursen wrote on Aug 20 2007, 04:17 PM:

We have released 6.06 beta2. We believe this one fixes the issue with 'copy to other …' using two SSH connections. Please verify this.

The announcement:

http://www.webyog.com/forums//index.php?showtopic=3441

Your dump also tells us the position where the crash has occured with fast data entry as you dscribed it. It is clipboard related, as you suggested – that much we can confirm. But we still have not been able to reproduce a crash or find a bug in the code yet.

Thank you, I will test that build.

For the fast data entry thing, the impression I got was that it was a problem when a row is updated while the previous row is still updating (maybe a simultaneous connection problem, or a buffer overrun?). When I press “down arrow”, there's a non-zero (noticeable) period of time when the program is busy (presumably updating MySql). Test the data entry out on a system 120ms away by ping-time, accessed by SSH and you'll be replicating the circumstances of this bug.

Chris

[c64audio]

peterlaursen wrote on Aug 20 2007, 09:10 AM:

sorry .. I forgot this:

If you can reproduce a crash, please attach the DUMP file here

Dump file attached. You could probably recreate the problem by going to a cell, having a string in the clipboard: then press CTRL-V, down Arrow, CTRL-V, down arrow, quickly, as if you're trying to paste the same value into a whole column without using “update”.

As to your other comments:

My previous post was a complaint, it wasn't intended to be diagnostic, since I have already provided lots of information.

Specifically (and it's IRRITATING to have to repeat myself), I'll narrow myself to two showstoppers.

**** THE ACTUAL PROBLEMS *******

1) If you try and copy a table between two servers which are connected to using SSH tunnelling, you get an authentication error, DESPITE both connections still being live and the passwords being correct. I've attached a picture of the error, which is coming from the destination server: despite the fact that the open connection to the destination server is still live and functional, having been tested mere seconds before. (and is still live after the attempt to copy).

2) If you see “MySQL Has Gone Away” during an interactive session on an SSH tunnelled connection, the only way to recover is to disconnect and reconnect. And this applies to at last two completely different servers. It looks to me as if SQLYog is not monitoring the SSH input correctly for this message and so doesn't either reconnect within SSH, or destroy the SSH connection and start again.

My comments about earlier versions are designed to show that I'm not making this up, that I AM an experienced user (you just don't seem to get that), and that you really should be less offhand with your established clients: all I can describe are the symptoms I'm seeing, and the _diagnostic_ fact that it wasn't present in earlier versions: for instance, most of version 5 was fine, though I recall problems with 5.25 in this area. Demanding specific information about WHICH versions it used to work in is just unreasonable and looks like an attempt to make me give up complaining by bombarding me with ever more detailed requests for information (I'm well aware of that technique, having been in IT for nearly 30 years).

I've installed version 6 now: you want me to go back and find install builds for previous versions and test them painstakingly in each one? Perhaps I should packet sniff for you as well? If I do, are you going to pay my consulting rate if it's a bug in your software?

Chris

[c64audio]

OK, I can see I'm on my own. 😡

I've been using SQLYog for years, recommended it to lots of poeple, and it's never been this broken for me. I guess I'll have to think about looking for something else. Customer service was already rude and offhand to a friend of mine, and I guess tech support is now equally dismissive.

Chris

[c64audio]

c64audio wrote on Aug 12 2007, 08:43 PM:

The incident where I've got two SSH tunnelled accounts open in SqlYog at the same time and get an authentication error trying to copy tables between them is consistently reproduceable for me. It's also been working OK for most of the rest of the life of SqlYog, which I've had since, I think, version 3 or 4.

Also, interactive mode does not appear to try to reconnect when it gets the MySql Server has gone away message. What's so difficult about initialising the SSH connection again? It looks like it doesn't even try to do that, yet it's perfectly happy to reconnect when I disconnect and reconnect.

Chris

Another odd thing: I had a row which wouldn't update until I had removed () brackets from a text column: I got MySql generated syntax error messages.

And in addition, SqlYog has a nasty habit of occasionally crashing out when doing interactive data entry, especially entering data quite quickly into a column, pressing the down key each time.

Sorry, but I'm going to have to do a smiley to show how I feel…

[c64audio]

peterlaursen wrote on Aug 8 2007, 10:00 PM:

1) this is very strange! are you perfectly sure that this is consistently reproducable?

2) this is probably because connection is lost. The interactive session will reconnect but structure sync will not.

3) same reply as 3. As program reconnects automatically we have not implemented a manually reconnect option.

I believe your problems are issues with the server or with the connection. This does not mean we cannot improve on the 'tolerance' of the program. We will discuss if reconnect attempt can be implemented in Structure Sync. But there are limits to what you should expect from a client if problem is on the server or with the connection.

BTW (4) (mail notification not working): such error can happen on 3 different 'links of the chain':

1) failure on sender client side

2) failure on the server side

3) failure on recipient client side

.. and I think we should start to find out which is the case! We can arrange that you try our server and if we could try yours I think we would be able to find out. You can create a ticket where we can arrange details!

The incident where I've got two SSH tunnelled accounts open in SqlYog at the same time and get an authentication error trying to copy tables between them is consistently reproduceable for me. It's also been working OK for most of the rest of the life of SqlYog, which I've had since, I think, version 3 or 4.

Also, interactive mode does not appear to try to reconnect when it gets the MySql Server has gone away message. What's so difficult about initialising the SSH connection again? It looks like it doesn't even try to do that, yet it's perfectly happy to reconnect when I disconnect and reconnect.

Chris

[c64audio]

peterlaursen wrote on Aug 8 2007, 11:36 AM:

There is no attempt to reconnect in Structure Sync. But with the copy options there is!

Well, that partially answers one of the questions, but everything else is still current

1) Copying between two accounts open with SSH port forwarding tends to result in authentication/access denied errors (even if the account is correct): all the time when copying a table without data, and intermittently when copying a table with data

2) Structure synchronisation just plain doesn't work between two accounts open with SSH port forwarding: it complains about the MySql server having gone away, even though it's still live in both boxes

3) Occasionally MySql has gone away during an interactive session: why is there no menu option to reestablish the SSH link?

BTW: Email notification doesn't appear to work, and I've checked my spam filter: it wasn't in there.

Chris

[c64audio]

peterlaursen wrote on Oct 2 2006, 10:41 AM:

@Chris ..

Can you tell what program version does like this?

There have been quite a lot changes with SSH since 5.15, so program version is important!

Did you try the same with 5.2 beta5 ?

Bug was present in 5.18, but I've just installed 5.19 and it seems you nailed the bug in that. Cool!

Chris

[c64audio]

vygi wrote on Sep 29 2006, 05:12 PM:

Oh yes, I see!

Sorry for posting it again as separate thread; somehow I did not see this another topic!

It seems to be exactly same issue: SQLyog disappears when it runs for a long time and then the users switches to another Windows application.

Now I can recall it happened always some time in the morning, probably when SQLyog was in front of other programs “running” (or actually sleeping) over the night.

Now you must be a little happier as you are at least not alone!! 😉

And I will install Beta 5 to see if it helps (have beta 3 until now).

Sorry I haven't checked the changelogs, but I've found that SQLYog crashes out without warning consistently if you stop a long running query over a MySql link that's using SSH. Has that been dealt with?

Chris

[c64audio]

peterlaursen wrote on Feb 20 2006, 10:58 AM:

You did not experience that with 5.01 either?  That is pretty strange then!

But you have a PM!

[post=”8802″]<{POST_SNAPBACK}>[/post]

Actually, I went straight from 4.something -> 5.02. Took me a while to remember to upgrade. Thanks for the PM. No problems so far on the crashing out front.

[c64audio]

peterlaursen wrote on Feb 19 2006, 11:58 PM:

Not my experience! I don't think 5.02 has crashed a single time here since it was released.  This is true for two Windows XP-SP2 installations and one WINE installation.  I use it probably around 3-4 hours per day in average.

Looks like the SQLyog process is being killed suddenly on your system since even the Windows standard popup *SQLyog(Ent).exe has caused an error and will be shut down* (or whatever it is exactly in English) does not occur. Any idea how this could happen?

Do you have a chance to test on other systems?

[post=”8800″]<{POST_SNAPBACK}>[/post]

Nothing else is being killed (or has been, and it's a mature system), and it's the first SQLYog to do this (I've been using it since v3), but I am running a lot of SSH tunnels on different ports at once. Maybe a timeout on one of them isn't being handled properly?

Chris

[c64audio]

Well, that would be nice. But all I'm suggesting is the following:

(user submits query)

If connection down THEN reconnect

display results

instead of

(user submits query)

If connection down THEN complain

(user resubmits same query)

reconnect

display results

Chris

[c64audio]

Idle timeout perhaps? It happens on three pretty vanilla Dedicated Server Mysql setups running on completely different ISPs under Linux w/cpanel, but there's nothing obviously I can see to fix the problem. I still think that if the connection has broken it would be helpful if SqlYog re-established it (perhaps this could be an option).

I'd like to hear about things I can tweak, of course, but I think there's an opportunity here to just tweak Sqlyog for added friendliness too.

Chris

[c64audio]

Enterprise = SQLYog Enterprise

PLink.exe = small process started by SQLYog Enterprise

<<< Undoubtedly thereis something wrong with your local MySQL-installation or maybe another MySQL-client running locally. Has your current MySQL been upgraded from a previous version ? And what version(s) are we talking about ? >>>

Doubtedly. There is nothing wrong with the local MySQL installation, and there is no other MySQL Client running locally. Anyway, it's not complaining about another client, it's complaining about another server already open on port 3306 when the service tries to restart. The current version is 4.1.6. Gamma NT, but the same problem was exhibited when I installed 4.0, and then completely uninstalled that version (even Registry entries). Logging into the local server works all the time EXCEPT when SQLYog is logged into another server through SSH tunnelling. Does SQLYog open anything servery on Port 3306? That could conceivably cause a problem if the local server was listening on port 3306. Hey, that gives me an idea…

Chris

[Author]

Posts