omldapsync does not modify user accounts (any more)

[stephan.klein]

Hi,

I have set up a scalix server which gets its user information from openldap.

omldapsync copies the user entries from openldap to scalix ldap as it should. Since a few days (weeks), changes on exisiting ldap-accounts, i.e. the addition of email-addresses, are no longer reflected to scalix ldap while new ldap accounts from openldap are correctly created in scalix ldap.

I tried so far:
* manual omldapsync (update, accept errors, complete reload, ...)
* manual deletion of the new but not synchronised ldap attributes in the according files in the import directory (i.e. add.curr etc.).

In former days, omldapsync stated that there where items to modify which worked perfectly, these message is gone. omldapsync now only says that there are 43 items to add.

Any help welcome!

Regards
stephan

[dirk]

are these 43 entries the ones you already have in Scalix? In this case you might want to compare the UUIDs. Some dumb LDAP administrationtools do funny things when moving items to another container.

Running omldapsync in debug mode (-d <numvalue>) will show you more about whats happening.

[kramer.markus]

good evening,

info: I'm cooporating with stephan in the case of solving this problem...

according to your advise we checked de UUIDs. the are identical.

here a short excerpt of the log:

Code: Select all

2009-03-27 00:00:03 INFO: work dir is /var/opt/scalix/m7/s/ldapsync/XXXXXXXX_sync/import
2009-03-27 00:00:03 STATUS: skip reprocess error from 127.0.0.1 ...
2009-03-27 00:00:03 STATUS: search source directory on 127.0.0.1 ...
2009-03-27 00:00:03 INFO: search base is ou=People,dc=XXXXXXXX,dc=de
2009-03-27 00:00:04 INFO: ... 42 entries to check
2009-03-27 00:00:04 STATUS: find delta and perform mapping ...
2009-03-27 00:00:04 INFO: ... 0 entries to delete
2009-03-27 00:00:04 INFO: ... 42 entries to add
2009-03-27 00:00:04 INFO: ... 0 entries to modify
2009-03-27 00:00:04 WARNING: this sync agreement has no delete limit configured
2009-03-27 00:00:04 STATUS: apply membdelete data against Scalix ...
2009-03-27 00:00:04 INFO: ... 0 entries passed for member.curr
2009-03-27 00:00:04 INFO: ... 0 entries failed for member.curr
2009-03-27 00:00:04 INFO: ... 0 entries warned for member.curr
2009-03-27 00:00:04 STATUS: apply delete data against Scalix ...
2009-03-27 00:00:04 INFO: ... 0 entries passed for delete.curr
2009-03-27 00:00:04 INFO: ... 0 entries failed for delete.curr
2009-03-27 00:00:04 INFO: ... 0 entries warned for delete.curr
2009-03-27 00:00:04 STATUS: apply add data against Scalix ...


no entry matched the "modify-criteria"....why?
and what are these criteria?


regards
markus

[dirk]

Your sync agreement may have forgotten its former results. One reason for this could be that someone has run omldapsync with the "-L" switch by mistake.
Please have a look at the /var/opt/scalix/m7/s/ldapsync/XXXXXXXX_sync/import directory.
The search.* files are used to build the differences. (Basically its putting the LDIF to search.curr, process it and if everything is fine copying it to search.last).
If you have a backup of this directory you can compare to the search.* files from the time before.

[kramer.markus]

Thanks a lot for your advice.

In our case the search.last file only contains one entry. For this user the sync runs fine, for all other users changes aren’t synced into scalix.

I'm not sure if my concept would work, but as far as I'm concerned Ihave to put all the data of the current scalix directory to this file (LDIF) and the sync would work fine again….

How can I get an LDIF output of the scalix directory?
Or would you prefer another way?

Regards
Markus

[dirk]

First make sure that the user-base, read: the mailboxes and groups in Scalix and in your leading directory are in sync.

Then you can simply copy search.curr to search.last. (Other readers of this thread: This is dangerous! Think twice before you modify these files if you think that this is the solution)

After that, use the "-M" option to resyncronise. A first test with "-n" before the full modify is highly recommended as well as setting "IM_DELETE_MAILBOX=FALSE" in sync.cfg.
Read the omldapsync man-page carefully before running the mod.

Finally you should try to find the reason for the isuue by reviewing the the sync.log.