Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-2743: Manual restart is required for LDAP proxy after upgrade

Centrify DirectControl ,  

12 April,16 at 11:10 AM

Applies to : All version of Centrify-Enabled LDAP proxy

Problem:

The installer script (install.sh) was run to upgrade all Centrify components on the UNIX host. After the script completes - the LDAP server proxy process does not restart.


Cause:

This is expected behavior as there is no auto-start script for LDAP proxy.


Solution:

Manually start LDAP proxy process with the command:
  /usr/share/centrifydc/libexec/slapd

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-3925: How to add Centrify parameter to a group policy articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-5902: Ldapproxy is rejecting query with authentication request articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?