Sja For Linux — Http Tunneling

[rsurujbh]

Hi

Are there plans to allow SJA (Linux) synchronizations to utilize HTTP tunneling? I recently tried to perform a sync using SQLyogTunnel.php on the target server, and I received the following message:

Warning: Target server using tunneling.

Linux version of SJA does not support tunneling.

Thanks,

–Robert

[peterlaursen]

What would you be willing to pay for such feature?

Currently the option is to install SQLyog Enterprise in Wine/Linux.

[rsurujbh]

Hi Peter

Maybe — what kind of costing would we be looking at? I am a big fan of the stand-alone job agent for Linux. If it could utilize HTTP tunneling, it would prevent having mysql remote ports open.

Let me know and we can discuss further.

–Robert

[Rohit]

Workaround:

How about using ssh for port forwarding? You can create a shell script that makes the connection just before you start sja.

[rsurujbh]

Ok, I was able to successfully set up an SSH port forward tunnel between the two servers using this syntax on the source server:

ssh -L 4406:localhost:3306 root@[REMOTE_SERVER]

This should send all 4406 local mysql connections across the tunnel to 3306 on the remote server. Using the mysql command-line client on the source server, this works perfectly. I can connect to the remote server and access mysql just fine.

mysql -u [USER_NAME] -p -P 4406 –protocol=TCP

Now when using SJA, it does not seem to work. I am using a source and target host ID of “localhost” but with different ports for each (3306 and 4406). The job completes without error, but the report always says SrcRows and TgtRows counts are the same and no updates are made. It seems as if the agent is using the source mysql server as both source and target for the comparisons. No link to 4406 is being made by the agent.

Do you think this is a bug? Thanks for the help.

localhost

[USER_NAME]

[USER_PASS]A 3306

[DB_NAME]

localhost

[USER_NAME]

[USER_PASS] 4406

[DB_NAME]

`[TBL_NAME]`

[rsurujbh]

I found another post on the forum about a similar problem:

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

In that thread, 3310 was attempted and it worked. However, this does not work for me. Even with 3310, the job runs and the source server seems to update itself (completely ignoring the 3310 tag in the schema for the target).

Any ideas?

Thanks.

[rsurujbh]

I finally got this resolved by using 127.0.0.1 as the target (once the SSH tunnel was up). I am guessing it has something to do with the server's hosts file… but, it works.

Thanks.

[Author]

Posts