[damonp]

This is not our server. We are doing an install for a client. I can PM you the link to the http tunnel.

[damonp]

When connecting via http tunnel.

Its a new connection created yesterday and still have not been able to connect to this server. IE. its not a working connection that stopped working or a sporadic problem. Happens everytime on this server whether attempting a connect or test connection.

[damonp]

I did finally notice in the help doc the direction to use different local ports if using different ssh tunnels in the same session. That appears to have cleared up this problem.

The thing that was driving me nuts was it worked depending on the order. I ran many queries and copies while connected to both over the same port and it worked so long as I connected to them in the right order. Too strange.

sorry to jump the gun

damonp

[damonp]

Yes there is a MySQL daemon running on my local machine, but I'm not connecting to it. It has different db names so its easy to tell I'm not mucking that up.

My understanding of SSH tunnel, the only place requiring the _remote_ FQDN is in the SSH connection. Once on the box via SSH, that becomes my new frame of reference so I am technically conecting to user@localhost. Depending on your settings the FQDN or 127.0.0.1 might also work once you are on that box via SSH.

If I am wrong in this, please correct me, but thats the way I've understood SSH tunneling with other apps.

I did finally RTFM to find out if you were doing multiple SSH tunnels in a single session, specify a different local port number to keep them separate. That helped with my other problem (in a separate post).

I checked my old copy of the competition's app and they do host/db to host/db transactions by referencing the name of the connection in the connection dialog instead of the connection settings (user@host). That way if you name the connections something similar to the hostname, its a no brainer to keep them straight.

Using your pulldown screen cap above as an example, mine only shows half of the entries because all show root@localhost for the connection setting even though one is connection is root@localhost and one connectoin is [email protected]. The duplicates get dropped. I am 99% sure I am connected to two different boxes, because one has all 40 db's and the other only has the 8 I have successfully copied over at the moment.

Note: The only reason one was set to be root@FQDN (ie. [email protected]) was to try to get the pulldown to differientiate the hosts.

I hope I'm making more sense now.

What version are you using?

thanks

damonp

[damonp]

peterlaursen wrote on Oct 22 2004, 10:28 PM:

You can copy a DB anywhere you want and to any webserver. But that DB won't work with MySQL on that server (it will just be a set of files! and there a not even beautiful to lo at like pictures 🙂 )

Now I'm confused. 🙂

So the copy command I am using is working at the file level and not through MySQL?

Thanks for the comments

damonp

[damonp]

I'm tunnelling to two different _remote_ servers.

When using ssh tunnel, I set _my_ ssh user/pass in the ssh portion of the tunnelling.

I set one mysql connection to root@localhost and the other to root@FQDN. (two _different_ remote hosts but I have root permissions setup to work both ways for this test)

My pulldown shows _all_ connections to be root@localhost.

1. Why?

2. Shouldn't the pulldown be able to show some distinctions between connections. If you ssh tunnel 2 hosts with root@localhost MySQL login _and_ they have the same db names, how do you tell the databases apart.

[damonp]

I'm not using the sync wizard. Right click on db name in the explorer pane, say copy db to different host/db. The pulldown in the middle of that box is what I am referring to.

Yes most times it should techincally be localhost to localhost (if using ssh tunnel), but in that pulldown, that doesn't give you enough info pick the correct host and db if db names are the same on different hosts.

Changing one ssh tunnel setting to use the FQDN doesn't get updated in the pulldown, still shows localhost. That itself should be a bug shouldn't it? The other is a feature change that would make the system more usable.

damonp

[damonp]

Copying a table (w & wo data) in the same db with and without data works.

Copying anything in a different db doesn't work.

[damonp]

I'm using SSH tunnel to copy tables to different dbs on the same host.

It appears to be data independant as it happens every time no matter if it is a two column text table or a complicated table.

It does let me create a copy of a table in the same db.

[damonp]

This is the output of the page on the server:

Quote:

This PHP page exposes the MySQL API as a set of webservices.

This page allows SQLyog to manage a MySQL server even if the MySQL port is blocked or remote access to MySQL is not allowed.

Visit Webyog to get more details about SQLyog.

Still can't get a connection or an error message using test or connect.

[damonp]

Yes this is beta 4.

Clicking on 'test connection' and 'connect' provide the same results, no error message and no connection. It appears that it does nothing.

thanks

[Author]

Posts