Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Could Not Connect To Source (ssh)

forums forums SQLyog Sync tools, Migration, Scheduled Backup and Notifications Could Not Connect To Source (ssh)

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #10017
      savery
      Member

      I wish to run some data synchronisations and maintenance scripts from an internal server to a remotely hosted (internet) database.

      I am using sja and when the jobs run successfully the product seems to meet my needs.

      Sadly, the connection seems to be very flaky, and I often get the “Could Not Connect to SOURCE”

      but not all the time.

      The script (site address/password etc have been changed) are as follows

      mysshuser

      mysshpwd

      myssh.mywebsite.com

      22

      3310

      database.mywebsite.com

      myuser

      mypwd 3306

      mydatabase

      truncate table zw_RemoteFileCount;

      insert into zw_RemoteFileCount

      select 't1', count(*) from t1

      union

      select 't2', count(*) from t2

      I created the xml through sqlyog enterprise and have run it successfully. Running it from a scheduled job seems to fail, but again not consistently.

      I am running sqlyog enterprise v4.1, mysql Ver 14.7 Distrib 4.1.21, for Win32 (ia32)

      The remote database is 4.1.21 and so I think I need to stay at the same version.

    • #22914
      peterlaursen
      Participant
      Quote:
      sqlyog enterprise v4.1

      We do not support such old porgram versions! Please upgrade!

      You can still upgrade for free if you hurry up!

      Upgrade policy: http://webyog.com/faq/30_129_en.html

      Of course I cannot guarantee that an upgrade will sove this. But there has been a lot of improvements – also with connectivity. So testing with a recent version would be 'first shot'.

      for clarity: I am talking about upgrading SQLyog – not MySQL!

    • #22915
      savery
      Member

      Seems to be fixed in 5.19 in trial version. I am sorting out full version. Thanks

Viewing 2 reply threads
  • You must be logged in to reply to this topic.