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

Could Not Connect To Source Mysql Server

forums forums Could Not Connect To Source Mysql Server

  • This topic is empty.
Viewing 24 reply threads
  • Author
    Posts
    • #9358
      raja1979
      Member

      When i run sja i get the following error.

      [root@matrix sja5]# ./sja test_back.xml

      SQLyog Job Agent Version 5.0

      Copyright © Webyog Softworks Pvt. Ltd.. All Rights Reserved.

      Sync started at Thu Nov 17 13:26:50 2005

      Could not connect to SOURCE MySQL server

      Check sja.log for complete error details.

      i have installed mysql on this pc , OS is Red Hat 7.1 and Mysql 3.23.

      the contents of xml file is ;

      localhost

      root

      passw 3306

      balaginew

      localhost

      root

      passw 3306

      balagiold

      i also checked the port its working and also tried ip address in place of localhost.

      but it does not work.

    • #19777
      peterlaursen
      Participant

      1) And you are PERFECTLY sure that the MySQL server is running?

      2) Can you connect from command line client 'mysql' (probably in /usr/bin) -or anything else such as a php script – with the same credentials? You could also install SQLyog (for windows) with WINE on Linux.

      I am not quite sure what you mean here

      QUOTE
      i also checked the port its working

      How did you check?

      You could also try the ip '127.0.0.1' instead of 'localhost'

    • #19778
      raja1979
      Member

      1. Mysql Server is running , iam able to connect using command line & i also telneted to

      Port 3306 and it show the mysql prompt.

      2. I Also have tryed using 127.0.0.1 but same error is displayed.

      3. I have used the windows versions it works properly.

      4. But i want the linux version.

    • #19779
      peterlaursen
      Participant

      well .. I can only say that it works for me on SUSE 10.

      I don't know if there could be an issue with Read Hat 7.

    • #19780
      Ritesh
      Member

      And what does sja.log say?

    • #19781
      raja1979
      Member

      It also contains the same message

      Sync started at Thu Nov 17 13:26:50 2005

      Could not connect to SOURCE MySQL server

      Is there any version problem of Mysql or Linux

    • #19782
      gberz3
      Member

      QUOTE(raja1979 @ Nov 17 2005, 10:03 AM)
      It also contains the same message

      Sync started at Thu Nov 17 13:26:50 2005

      Could not connect to SOURCE MySQL server

      Is there any version problem of Mysql or Linux

      [snapback]7912[/snapback]

      I'm having a similar (if not the same) issue, running Ubuntu 5.10. I can connect to remote servers all day (if I set *them* up as the SOURCE, for instance), but then I, of course, receive “Could not connect to TARGET. . .” Some documentation on what exactly SJA is doing (or more verbose logging) would be soooooo helpful.

    • #19783
      kyjamil
      Member

      A-O-A

      by default root dont have any pass

      you can check it by

      $ mysql -u root -h localhost

      if this command connected then this means no password req in XML file.

      Cheers

      Yasar

    • #19784
      gberz3
      Member

      QUOTE(peterlaursen @ Nov 17 2005, 06:17 AM)
      well .. I can only say that it works for me on SUSE 10.

      I don't know if there could be an issue with Read Hat 7.

      [snapback]7910[/snapback]

      Could you provide a list of the Linux versions on which you have built/verified the SJA tool? I have still not overcome the problem in Ubuntu 5.10.

      Thanks.

    • #19785
      peterlaursen
      Participant

      I really doubt this is related to on which 'nix' dialect it was built. since it has no dependencies and is statically linked. Rather I think it is related to the way MySQL is configured with the actual build (ubuntu in this case).

      Can you connect with some other client using the C-API, such as *MySQL Administrator* ?

      I don't know ubuntu (and what type of install packages it uses) but is a big deal to uninstall the distro-version of MySQL and install/compile a standard build from mysql.com? If you can do this I suggest you try it.

      But I agree that a list of distro's in which it has been tested (with any sort of tricks and configuration issues) could/should be maintained. As the maintaneer of the Webyog FAQ that must be my job! But I will need then that users are more responsive. People don't seem to realise the importance of reporting ´not-problems' – only problems! And BTW: this applies to SQLyog running on WINE as well.

    • #19786
      gberz3
      Member

      QUOTE(peterlaursen @ Feb 17 2006, 05:29 PM)
      . . .

      Can you connect with some other client using the C-API, such as *MySQL Administrator* ?

      I don't know ubuntu (and what type of install packages it uses) but is a big deal to uninstall the distro-version of MySQL and install/compile a standard build from mysql.com?  If you can do this I suggest you try it.

      . . .

      Yes, using “localhost” I can connect to the 'mysql' program directly. I also created a quickie program in python using the MySQLdb module, and it worked as well. SJA seems to be the only thing that will *not* work. I realize the program is free, and we can't necessarily rightfully expect top-of-the-line support, but would your people mind givng debian and/or ubuntu a quick runthrough and see what the problem might be?

    • #19787
      peterlaursen
      Participant

      You don't answer my questio, I believe!

      QUOTE
      Can you connect with some other client using the C-API, such as *MySQL Administrator* ?

      I am not talking about commandline! Clients that connect through socket are irrelevant here! It must be a client using TCP for connection!

      In your my.cnf does it read like

      skip_networking

      or

      #skip_networking

      …if it is 1st then TCP connections are disabled.

      Also: do you have any firewall application running?

    • #19788
      gberz3
      Member

      QUOTE(peterlaursen @ Feb 18 2006, 09:53 AM)
      You don't answer my questio, I believe!

      I am not talking about commandline!  Clients that connect through socket are irrelevant here!  It must be a client using TCP for connection!

      In your my.cnf does it read like

      skip_networking

      or

      #skip_networking

      …if it is 1st then TCP connections are disabled.

      Also: do you have any firewall application running?

      [snapback]8780[/snapback]

      First of all, I included the fact that I used the MySQLdb module which is the Python API for accessing mysql. I certainly believe that is relevant. As far as my my.cnf file goes, it says, and I quote:

      # Instead of skip-networking the default is now to listen only on

      # localhost which is more compatible and is not less secure.

      bind-address = 127.0.0.1

    • #19789
      peterlaursen
      Participant

      QUOTE
      I used the MySQLdb module which is the Python API for accessing mysql

      Well I don't know if it uses socket or TCP. But you seem to know.

      QUOTE
      # Instead of skip-networking the default is now to listen only on

      # localhost which is more compatible and is not less secure.

      bind-address = 127.0.0.1

      Could I suggest that you try comment out like

      QUOTE
      #bind-address = 127.0.0.1

      That would implement MySQL standards which are 'not skip_networking'

      127.0.01 may be routed over socket with that system.

      QUOTE
      which is more compatible

      Compatible with what? Not MySQL standards!

    • #19790
      peterlaursen
      Participant

      and use the local ip (ie. 10.0.0.1 or whatever and not 127.0.0.1) I would add. Or some name server alias for that.

    • #19791
      gberz3
      Member

      QUOTE(peterlaursen @ Feb 18 2006, 11:55 AM)
      and use the local ip (ie. 10.0.0.1 or whatever and not 127.0.0.1) I would add.  Or some name server alias for that.

      [snapback]8783[/snapback]

      After much anguish it appears that the “solution” is as follows:

      1) make sure your '/etc/hosts' file reads as follows:

      CODE

      127.0.0.1 localhost                //localhost *MUST* be first (notice separate entries)

      127.0.0.1 localhost.localdomain

      127.0.0.1 . . .

      2) make sure you reference the local server in the SJA.XML file as:

      CODE

      127.0.0.1

      or

      localhost.localdomain

      This will then allow the sync to occur. I am now having a problem, however, with the actual sync. I Intentinally set up a database with no data (but full of tables). I then tried to sync it with another completely empty database (no tables present). The output lists all the tables from the database with tables, however, it doesn't propagate those tables to the 'empty' database. What could possibly be the problem?

      The following is my XML file:

      CODE

      127.0.0.1

      root

      3310

      fulldb

      127.0.0.1

      root

      3306

      emptydb

      I have port 3310 SSH forwarded to the remote machine. Everything works and it sees it (as I said), and even the output misleads you to think that a sync occurred, but no tables get copied. 😕

    • #19792
      peterlaursen
      Participant

      hmmm ..

      1) localhost.localdomain. Now again!

      actually we wrote about it here:

      http://webyog.com/faq/23_36_en.html

      But you are welcome to propose an improvement of this FAQ. Actually I am not satisfied with it!

      2) SJA data sync is a tool for DATA SYNC, not STRUCTURE SYNC. However I think this could be fixed, as long it is only dublicating a structure to an empty DB! Let Ritesh comment on it. Can you put a single row on 'dummy' row of data in each table on the source? Fixing this will not be high priority right now. We are busy with this:

      http://webyog.com/faq/33_20_en.html . And a little bit late actually!

      SQLyog Enterprise runs on Wine. http://webyog.com/faq/31_71_en.html . It has a true STRUCTURE SYNC tool, that will be TOTALLY COMPLETE with ver. 5.1 /BETA1 probably next week).

    • #19793
      gberz3
      Member

      Ok, actually got past all that. Now, I'm having a different issue. After using SJA to sync the tables, I get the following when I repeat it in EXACTLY the same fashion:

      CODE

      Check sja.log for complete error details.

      NULL definition mismatch for 'Product_ID' column in '`My_products`' table

      Check sja.log for complete error details.

      NULL definition mismatch for 'Product_ID' column in '`Other_rates`' table

      . . .

      What could possibly be occurring?

    • #19794
      peterlaursen
      Participant

      QUOTE
      and even the output misleads you to think that a sync occurred

      Wrong! All data were sync'ed. SJA did not even have to create tables to do it! 😀

    • #19795
      peterlaursen
      Participant

      Are MySQL versions identical?

      http://webyog.com/faq/11_68_en.html.

      Is the SJA recent? It should display an error essage.

      Unless there is a simple 'NULL definition mismatch'.

      Read in detail about data sync:

      http://webyog.com/articles/Using_SQLyog_En…L_Databases.pdf

    • #19796
      peterlaursen
      Participant

      BTW: is this

      QUOTE
      1) make sure your '/etc/hosts' file reads as follows:

      CODE

      127.0.0.1 localhost                //localhost *MUST* be first (notice separate entries)

      127.0.0.1 localhost.localdomain

      127.0.0.1 . . .

      2) make sure you reference the local server in the SJA.XML file as:

      CODE

      127.0.0.1

      or

      localhost.localdomain

      This will then allow the sync to occur.

      your own discovery? Quite valuable actually if it is true and complete!

    • #19797
      gberz3
      Member

      QUOTE(peterlaursen @ Feb 18 2006, 01:04 PM)
      Are MySQL versions identical?

      http://webyog.com/faq/11_68_en.html.

      Is the SJA recent?  It should display an error essage.

      Unless there is a simple 'NULL definition mismatch'.

      Read in detail about data sync:

      http://webyog.com/articles/Using_SQLyog_En…L_Databases.pdf

      [snapback]8789[/snapback]

      Good call. I was trying it with different machines (with, of course, various versions of MySQL :eek:) and it was only occuring with syncs between different versions. Everything works with the same version. Thank you!

    • #19798
      gberz3
      Member

      QUOTE(peterlaursen @ Feb 18 2006, 01:09 PM)
      BTW: is this

      your own discovery? Quite valuable actually if it is true and complete!

      [snapback]8790[/snapback]

      Yes, after reviewing my own cryptic documentation from months past I retraced some steps and narrowed it down. I can't promise it's not published elsewhere (or that it's the only method), but those findings came from my own discoveries. 😉

    • #19799
      peterlaursen
      Participant

      Well thanks then.

      I think I will be able to improve the FAQ.

    • #19800
      peterlaursen
      Participant

      Added your solution (and a previous one too) to the FAQ:

      http://webyog.com/faq/23_36_en.html

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