[xristy]

I just tried 4.0.26 on the Linux system and the result was:

“The implementation of concat_ws() in source and target MySQL servers are different. SJA uses the concat_ws() MySQL function to generate checksums. Please make sure that the source and target MySQL servers are similar.

Exiting SQLyog Job Agent.”

so apparently they changed the implementation between 4.0.12 and 4.,0.26

Oh well 🙁

peterlaursen wrote on Jan 14 2006, 09:47 PM:

I am confused now

does that mean that it is working now ??

That would be too good to be true, so I don't think that is what you mean!

With SSH-access only there are not so many clients to try .. unless you are allowed to login with a graphical shell (KDE, GNOME) using SSH (don't know RH in this respect, but on SuSE you can)

A few things that you can try if time a saturday night is no issue:

1:

Install 4.0.26 instead of 4.0.12.  4.0.12 is an old boy! – there has been quite a lot of fixes since then, and I would not recommend it.  It can be sync'ed with 4.0.12 on BSD as well (same concat_ws() implementation).  There should not be but nevertheless there could be an issue with the client library that SJA is compiled with.  hmmmm .. but still it connects to SOURCE that is also a 4.0.12  🙁

2:

Do you have a Windows machine available?  You can try the SQLyog Enterprise Trial.  It won't let you do the sync but it will let you connect with SSH.  Just as a test to see if additional info of some kind shows up

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

[xristy]

I don't have it working. I meant that I'm trying to get 4.0.12 on both systems working.

I'll give 4.0.26 a try.

peterlaursen wrote on Jan 14 2006, 09:47 PM:

I am confused now

does that mean that it is working now ??

That would be too good to be true, so I don't think that is what you mean!

With SSH-access only there are not so many clients to try .. unless you are allowed to login with a graphical shell (KDE, GNOME) using SSH (don't know RH in this respect, but on SuSE you can)

A few things that you can try if time a saturday night is no issue:

1:

Install 4.0.26 instead of 4.0.12.  4.0.12 is an old boy! – there has been quite a lot of fixes since then, and I would not recommend it.  It can be sync'ed with 4.0.12 on BSD as well (same concat_ws() implementation).  There should not be but nevertheless there could be an issue with the client library that SJA is compiled with.  hmmmm .. but still it connects to SOURCE that is also a 4.0.12  🙁

2:

Do you have a Windows machine available?  You can try the SQLyog Enterprise Trial.  It won't let you do the sync but it will let you connect with SSH.  Just as a test to see if additional info of some kind shows up

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

[xristy]

I unistalled 4.1 and installed 4.0.12 fresh. I'm just syncing the Linux hosted MySql from the BSD hosted MySql so it's no big deal to blow away the installs until I get it all working.

peterlaursen wrote on Jan 14 2006, 09:06 PM:

Downgrading from 4.1 to 4.0

The MySQL docs has this to say when downgrading from 4.1 to 4.0:

http://dev.mysql.com/doc/refman/4.1/en/dow…ing-to-4-0.html

Anything here that is relevant to your situation?

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

[xristy]

I get the message:

“Could not connect to TARGET MySQL server”

when trying to connect to 4.0.12 on the local Linux server where SJA is running.

I can connect to the 4.0.12 server locally with mysql and mysqladmin. I can connect to the 4.0.12 server remotely with Navicat.

A “headless” system is one that has no keyboard, mouse or display. In my case, it is a server that can only be accessed via ssh.

I've tested 4.0.12 and it is able to perform the functions that I need for the daily migration.

So, all I need is to get the sync working and all will be most excellent.

Thanks

[xristy]

I have a production 4.0.12 server running on a BSD system. This is the SOURCE. I cannot change this system.

I have a headless Linux system on which I can install whatever MySql I like. As I mentioned in the previous note, I currently have 4.0.12 installed on the TARGET so they certainly should be compatible.

Since the TARGET is headless (and so is the SOURCE) and since the intent is to run an unattended cron job to sync the TARGET to the SOURCE I don't see Wine as a win.

I'd really like to understand why I can't connect to the TARGET 4.0.12 system.

Thanks

[Author]

Posts