Description Sönke Schwardt-Krummrich 2013-12-11 16:39:26 CET

On a DC backup and a DC slave an inconsistency between ldap content and listener cache occurred. After calling univention-replicate-one the listener checked the upstream object against the listener cache and jumped to the next transaction because according to the cache the system was up-to-date:

11.12.13 15:29:05.335  LISTENER    ( ALL     ) : handler: replication considered
11.12.13 15:29:05.335  LISTENER    ( INFO    ) : handler: replication (up-to-date)

The listener should always pass the retrieved object to the replication module - no matter if the listener cache has already seen this object.