sync/namechange issue

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

HansR100
Posts: 35
Joined: Fri May 21, 2010 2:28 am

sync/namechange issue

Postby HansR100 » Fri Aug 26, 2011 5:29 am

Hello Com,

weve got a multiserver setup where server A syncs with all others( B, C, D).
The issue is if you change a name on server A in sac, restart the dirsync also on the other servers on C and D the changes work, but on the server B they won´t appear.
So you cannot mail via the adressbook to the user because there is an old adress.

The dirsync works just fine, i last addes users on the servers and it worked well and fast also to sync.
Maybo someone got an idea whats the problem and how to solve it?

If i manuelly delete the entry with omdelent -e 'UL-AUTHID=<authid>' and add the entry from server A to B with omaddent it works...

Thanks
HansR
Last edited by HansR100 on Thu Sep 15, 2011 9:30 am, edited 2 times in total.

ls-al
Scalix Star
Scalix Star
Posts: 510
Joined: Tue Jun 29, 2004 8:28 am
Location: Leipzig, Germany
Contact:

Re: sync/namechange issue

Postby ls-al » Mon Aug 29, 2011 11:26 am

Given that there is a valid import agreement on server B for the central host A, you will have to run "omresyncds" on server B. Look at the man-page for this command.

HansR100
Posts: 35
Joined: Fri May 21, 2010 2:28 am

Re: sync/namechange issue

Postby HansR100 » Tue Aug 30, 2011 10:18 am

Thanks hope this will do it.
The output of the command was not that much.

regards

HansR100
Posts: 35
Joined: Fri May 21, 2010 2:28 am

Re: [solved, hopefully] sync/namechange issue

Postby HansR100 » Thu Sep 15, 2011 9:29 am

got the same problem with a +BB entry, which got deleted on server A, but still exists on B not on C and D...
omresyncds did nothing.

some other ideas?

going to delete it manually

Thanks
Hans R.

ls-al
Scalix Star
Scalix Star
Posts: 510
Joined: Tue Jun 29, 2004 8:28 am
Location: Leipzig, Germany
Contact:

Re: sync/namechange issue

Postby ls-al » Thu Sep 15, 2011 9:53 am

Manual deletion is still possible, but I would also compare the "PROPAGATED-BY" attribute to confirm that the entry in question was created through dirsync.

It should also be noted that omresyncds only creates a full-sync request which will be sent out during the next sync-cycle. You can force it by restarting the dirsync-service when having "DS_CUST_SEND_REQ_NOW=true" in general.cfg.


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 6 guests