[Ken Weise]

peterlaursen wrote on Jun 18 2009, 10:03 AM:

Is it errors occurring with SJA itself of MySQL errors or both you are interested in and how detailed?

Do you want us to print all errors (and warnings?) that MySQL sends and if any of the kind occurs you want an error code that you can use for a condition in the script?

Of course, the more detailed the better. But an exit code of 0 for no errors, then an exit code of non-zero for an error is ok. Then you could possibly have a list of error codes and related text, depending on how far you're willing to take it. At a minimum, I think 0 for no error, 1 for warning(s), 2 for error(s). Then like I said, if you're willing to put the effort, other exit codes could exist for specific errors. That would be more work, as reporting 2 errors would be difficult.

Just knowing that an error occurred, would allow me to include the log file in a follow up email, which notifies of the error. Knowing that it's a warning or hard error would let us know how urgent it is to look into.

Thanks!

[Ken Weise]

nithin wrote on Jun 18 2009, 02:11 AM:

Linux SJA logs error to a file 'sja.log' that creates where the SJA.EXE runs. This is similar with Windows when SJA.EXE runs through command line.

If run through SQLyog wizard you can specify the path of sja.log where GUI provides an option for that(please see the screen shot attached)

Thanks

Yes, I know about the log file. But is there a list of possible errors reported in the log file? My intention, as stated, is to make an automated script to sync, and notify on errors. However, I don't know what to have the script look for in the log file in order to automatically report all error conditions.

[Ken Weise]

peterlaursen wrote on Jun 15 2009, 09:47 AM:

However I think that support 32 for bit executables is optional in 64 bit Linux (but undoubtedly it will be default with the installer in every distribution). Only if you build from source or make a very selective 'packet-picking' you have to think about it.

Thanks! We'll be going with a default install, we don't need anything special to need a complete kernel rebuild.

[Ken Weise]

peterlaursen wrote on Aug 28 2008, 04:24 PM:

7.x Data SYNC is not compatible with MySQL 4.0 and 3.x. The functions we use for achieving the speed improvements do not exist in 4.0 and 3.x. Currently you will need to use 6.56 for Data Sync if a 3.x or 4.x server is involved. You can have 6.x and 7.x installed in parallel. I hope (but cannot guarantee) that we will find a better solution soon.

The destination server is 5.0.22-community-nt, and the source server is (linux) 5.0.27. It transfers a bunch of other files successfully.

[Author]

Posts