Master/Slave sync error

[Marcus]

Hello,

I'm having problems setting up the Master/Slave replication on fresh, fully up-to-date v3.0 installs.

Up to now, this is what I've done:
1) setup master (very basic - I only choosed "Users&Groups" and removed the "cloud" freemium)
2) setup slave (same local network - very basic - only Users&Groups and removed the "cloud" freemium)

On the master: 
1) picked up the "Slave connection password"

On the slave:
1) Clicked on the drop down menu (Sync users from:) and choosed "Other Zentyal Server"
2) I typed the local IP in the "Master host:" field
3) Changed the "Master port:" to something else (SSL is needed)
4) Entered the "slave password"
5) Hit Change followed by updating the configuration (top right)

On the master;
1) created a group
2) created a user

Logs are giving:
DEBUG> SOAPClient.pm:115 EBox::SOAPClient::__ANON__ - 500 Status read failed: 
ERROR> Slave.pm:149 EBox::UsersAndGroups::Slave::__ANON__ - Error notifying sl1 for _addUser: 500 Status read failed: 
DEBUG> SOAPClient.pm:115 EBox::SOAPClient::__ANON__ - 500 Status read failed: 
ERROR> Slave.pm:149 EBox::UsersAndGroups::Slave::__ANON__ - Error notifying sl1 for _modifyGroup: 500 Status read failed: 

I've redone the sync configuration by switching the slave configuration to "none", saved the new configuration, switching it back to remote zentyal and saved again.  Still same error...

** Apparmor got removed from both servers and that didn't seem to help.

Any help would be much appreciated.

Best,

Marcus

[nontrivial]

I am having the same problem. The only think I can add is that a bunch of files are created in /var/lib/zentyal/syncjournal/sl3/ that seem to have something to do with the process. Until the issue is resolved, is there some way I can copy over these files to the slave machine and have it process them?

Which log were you looking at, BTW?

James

[nontrivial]

Hmm, I was looking at the Zentyal bug list, and it looks like there are multiple bug reports about the issue. See 5270 (http://trac.zentyal.org/ticket/5270) and 5615 (http://trac.zentyal.org/ticket/5616). Hopefully the issues will be resolved soon.

James