Problem: no change of listener transaction id for last 0 checks

[Gohmann]

Problem: no change of listener transaction id for last 0 checks

The LDAP replication does not work and the log file /var/log/univention/listener.log shows a similar error message:

25.07.19 16:24:41.359  LISTENER    ( INFO    ) : notifier returned = id:83853	dn:<LDAP>	cmd:*
25.07.19 16:24:41.359  LISTENER    ( ERROR   ) : notifier.c:129:notifier_wait_id_result LDAP failed No such object (32): id:83853

Solution

The given ID is not available in the replication backend. To solve do (please adjust the ID):

/usr/share/univention-directory-notifier/univention-translog check --fix
/usr/share/univention-directory-notifier/univention-translog load 83853

Recreation of the listener cache could also be a soultion:

Recreate listener cache

Problem: The univention directory listener fails with I/O errors in the /var/log/univention/listener.log - no further replication is done (see also SDB article 1303). The reason is corrupt listener cache - this can happen if the filesystem ran out of free space for example. Example snip from listener.log: 17.01.15 13:45:18.851 LISTENER ( ERROR ) : database error: unable to create/retrieve page 3462 17.01.15 13:45:18.851 LISTENER ( ERROR ) : database error: PANIC: Input/output err…