Hey,
thanks for the information. The output of the first two commands show that the S4 connector seems to be running and processing data properly. That’s good.
However, the output of the last two commands show that the univention-directory-listener
program doesn’t seem to be running. It has to for the domain to work properly, though. It is responsible for acting on changes to the LDAP contents.
Please verify this by running ps uw -u listener
. It should output one process called /usr/sbin/univention-directory-listener
.
If it isn’t running, as I think it isn’t, you should start it by running service univention-directory-listener start
. Afterwards make sure that it is actually running with the ps
command mentioned above.
Now observe the content of the file /var/lib/univention-directory-listener/notifier_id
. The number should start rising again, slowly approach and finally match the number in /var/lib/univention-ldap/last_id
. Explanation: the last_id
is incremented each time any change is made in the LDAP, and the notifier_id
is incremented each time the univention-directory-listener
component has processed the corresponding change. In a regular system both numbers should match (or the notifier_id
be at least a few steps behind the last_id
if the listener is currently processing data).
You can and should also check the content of the corresponding log file, /var/log/univention/listener.log
.
Kind regards,
mosu