ZCS Administrator's Guide 8.0.3
ZCS Administrator's Guide 8.0.3
Open Source Edition


Zimbra LDAP Service > Flushing LDAP Cache

Flushing LDAP Cache
When you modify the following type of entries in the Zimbra LDAP server, you might need to flush the LDAP cache to make the change available on the server.
*
*
*
*
*
*
*
*
*
Flush the Cache for Themes and Locales
When you add or change theme (skin) property files and locale resource files for ZCS on a server, you must flush the cache to make the new content available.
*
To flush skins, type zmprov flushCache skin.
*
To flush locales, type zmprov flushCache locale.
Flush Accounts, Groups, COS, Domains, and Servers
When you modify the account, COS, groups, domain, and server attributes, the change is effective immediately on the server to which the modification is done. On the other servers, the LDAP entries are automatically updated after a period of time if the attributes are cached.
The default ZCS setting to update the server is 15 minutes. The caching period is configured on local config key.
*
To change the setting, type
zmlocalconfig ldap_cache_<object>_maxage.
*
To make changes available immediately, type
zmprov flushCache [account|cos|domain|group|server] [name|id].
If you do not specify a name or ID along with the type, all entries in cache for that type are flushed and the cache is reloaded.
Note:
Flush Global Attributes
When you modify global config attributes, the changes are effective immediately on the server to which the modification is done. On other mailbox servers, you must flush the cache to make the changes available or restart the server. LDAP entries for global config attributes do not expire.
Some global config attributes are computed into internal representations only once per server restart. For efficiency reasons, changes to those attributes are not effective until after a server restart, even after the cache is flushed. Also, some global configuration settings and server settings that are inherited from global config are only read once at server startup, for example port or number of processing threads. Modifying these types of attributes requires a server restart.
To flush the cache for global config changes on all servers:
1.
zmprov mcf zimbraImapClearTextLoginEnabled TRUE
The change is only effective on the server zimbra_zmprov_default_soap_server, port zimbra_admin-service_port.
2.
Flush the global config cache on all other servers, zmprov flushCache must be issued on all servers, one at a time. For example:
zmprov –s server-2 flushcache config
zmprov –s server-3 flushcache config
3.
zmprov desc -a <attributename>.
The requiresRestart value is added to the output if a restart is required.
 
Copyright © 2013 VMware Inc.