Linux Target Could Not Connect

[xristy]

I'm running on RH ES Linux 2.4.21-32.0.1.ELsmp. SJA is version 501.

I was running MySql 3.x and got SJA to work without any problems; however, it turned out that the version of MySql was too old to support some other features that I needed so I upgraded to MySql 4.1.

On MySql 4.1 I had a bit of a problem getting “Could not connect to TARGET MySQL server” which I solved by changing the host from “localhost” to the external name (even though it had worked with the older MySql install and the only change was to uninstall 3.x and install 4.1 ?!)

Unfortunately I then got:

“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.”

The Source server is 4.0.12. So I uninstalled 4.1 and installed 4.0.12 as the Target and now I can't connect at all with SJA. I tried 'localhost', the external host name and the IP address in the all to no avail. mysql, mysqladmin and navicat on a remote system are all able to connect to the 4.0.12 install, so it seems to me that I'm staring at a brickwall.

I really need to get this working as part of a migration chain so I really appreciate any help.

Thanks

[peterlaursen]

This message:

Quote:

“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.”

is exlained here: http://www.webyog.com/faq/10_68_en.html

Quote:

This means that the concatenation of colums is performed on the server side, and the checksum's generation and further calculation is done on the client side. Unfortunately the implementation of the concat_ws() function has changed with various MySQL versions. If you try to sync across versions where this is the case, SJA reports an error stating that concat_ws is used and this might not work with different versions of MySQL – and aborts. We have no plans to implement the concatenation on the client side (because that would completely destroy the efficiency of the tool) and thus the sync tool cannot be used if the MySQL versions are “too much different” in this respect. Version 3.23.x cannot be sync'ed with 4.0.x and higher and 4.x cannot be synced with 5.x.

It is NOT a connection issue. It connects! But the DATA SYNC TOOL can't sync across these versions.

You can export your 4.0 database and import to a higher version.

I think your are using the SJA for LINUX. Right? You may install SQLyog on WINE:

http://www.webyog.com/faq/5_71_en.html if you are not able to connect from a Windows client.

And this issue

Quote:

On MySql 4.1 I had a bit of a problem getting “Could not connect to TARGET MySQL server” which I solved by changing the host from “localhost”

probably is a problem with locating the socket file. The MySQL versions uses different sockets (depending on whether it is a dynamically or statically linked version and if you compiled it yourself there are sources available with different compile options). And it is not a SQLyog issue. You would experience the same thing with 'Administrator' and 'Query Browser' as well. You may try!

[peterlaursen]

However …

You can also install 4.1 on the source (remember to run the fix_privilege script) and then sync the data.

[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

[peterlaursen]

What is a 'headless' Linux system ?? Sorry but I never heard that before!

I am sorry if I did not get you right.

Your writings must have been too complcated for my brains :huh:

But you are running 4.0 on both systems now I understand. And you can't connect with SJA for LINUX to TARGET MySQL server on local machine. How can you tell ? Error messages in the sja.log?

Are other clients able to connect from local machine? Can SQLyog connect when installed on WINE for instance. 'MySQL Administrator' ? Local MySQL command line client?

Can the SJA connect from another machine (Windows or Linux) ?

Well, I also don't understand the reason for this either!

But you will have to provide more information.

[peterlaursen]

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?

[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 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]

[peterlaursen]

I am confused now

Quote:

I'm just syncing the Linux hosted MySql from the BSD hosted MySql

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

[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]

[peterlaursen]

Also I believe there are different .RPMs to test with.

Binary RPM's built with a specific Linux version and generic binaries.

. Also source RPM's if you have gnucc-compiler etc installed with the RH Linux.

On my SuSE 10, sometimes the binary versions compiled with SuSE 9.3 will work. Sometimes not. Sometimes the generic will do. Once (Query Browser) I have had to use the source RPMs – neither the SuSE 9.3 version or the generic RPM would work properly. They compile with a single mouse-click on SuSE YaST installer. Probably it is not difficult with YOU either.

A broad variety of builds from here:

ftp://sunsite.dk/mirrors/mysql/Downloads/MySQL-4.0/

This is source: ftp://sunsite.dk/mirrors/mysql/Downloads/&#8230;.0.26-0.src.rpm

This is generic: ftp://sunsite.dk/mirrors/mysql/Downloads/…0.26-0.i386.rpm

Don't forget to tell what you did when you got it working!

[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]

[peterlaursen]

SHIT!

But it connects then!

Link to arhcives here: http://downloads.mysql.com/archives.php?p=mysql-4.0

changelogs here: http://dev.mysql.com/doc/refman/4.1/en/news.html

see if you can find that implementation in the changelogs and find the latest release before that! I'll research a little too!

[peterlaursen]

http://dev.mysql.com/doc/refman/4.1/en/news-4-0-14.html

“The CONCAT_WS() function no longer skips empty strings.”

Try this http://downloads.mysql.com/archives/mysql-…0.13-0.i386.rpm

a generic 4.0.13

[peterlaursen]

And if it works you should install the coresponding client package as well. And the MAX server binary if you need it (must be installed over the standard server – adds BDB support among other pretty rare things – as far as I remember InnoDB is included with the standard server in 4.0.x)).

[peterlaursen]

sweet silence <_<

Code:

Label1:
If NO_NEWS == GOOD_NEWS then
{ please tell
}
else GOTO Label1

😀

[Author]

Posts