Forum Replies Created
-
AuthorPosts
-
Big DaneMember
With help from a more (than me) decent Linux admin, we managed to debug the problem (used gdb to debug) and it seems that SJA is looking for the MySQL socket in the wrong location.
This is how my MySQL is configured (/etc/mysql/my.cnf):
Code:socket = /var/run/mysqld/mysqld.sockBut this is where SJA looks for the socket:
Code:socket = /var/lib/mysql/mysql.sockSo, the short term solution is, to make a softlink, like described here: http://www.webyog.com/forums//index.php?showtopic=1367
Big DaneMemberHi Peter, I have gathered the following information:
TARGET server info: YES, 64bit Ubuntu
Code:Linux ServerName 2.6.20-16-server #2 SMP Thu Aug 30 23:21:48 UTC 2007 x86_64 GNU/LinuxMySQL SOURCE info:
Code:Welcome to the MySQL monitor. Commands end with; or g.
Your MySQL connection id is 127344
Server version: 5.0.27-standard-log MySQL Community Edition – Standard (GPL)MySQL TARGET info:
Code:Welcome to the MySQL monitor. Commands end with; or g.
Your MySQL connection id is 37889
Server version: 5.0.38-Ubuntu_0ubuntu1-log Ubuntu 7.04 distributionSJA job describtion:
Code:
host
user pass 3306 dbname
localhost
user pass 3306 dbname
TEST case:
As a test I've tried to do a SJA job, at my localhost (source=target) and nothing happens:
– the SJA.LOG is empty: “Sync started at Tue Oct 9 15:06:23 2007” – nothing more than that.
– the SJASESSION.XML has this info: “
“Can I call SJA in debug or some kind of verbose log mode?
-
AuthorPosts