I am very sorry for the trouble that has brought you, this is the case. The current openldap version used in the production environment is 2.4.44. The service configuration is active and standby, running in the Linux environment. New users and groups will be delivered to the client very quickly. When I update the user properties, some clients will not be updated (the update is completed after 20 minutes). Clock synchronization is complete, ntpserver is the same, ldap client and ldapserver are on the same network segment.
发送自 Windows 10 版邮件应用
--On Monday, July 15, 2019 3:24 PM +0800 王峰 <email@example.com>
> Hello, wish you happiness!
> Sorry, take up your precious time. I encountered a problem. In
> the openldap HA environment, the update user group found that it was not
> synchronized to the client in time (8 hosts, 5 stations, 3 syncs, not
> synchronized, waiting for half an hour to complete synchronization). Has
> anyone encountered such a problem? And would like to know how to
You should provide significantly more information than this:
a) What version of OpenLDAP are you using?
b) What type of replication do you have configured? What are the
configuration parameters for each server (serverIDs, syncrepl stanzas,
syncprov overlay configs, accesslog overlay configs, etc)?
c) Are the clocks on the servers tightly sync'd (mandatory for syncrepl
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: