This article describes what can happen if the incorrect libraries are loaded and the steps that can be taken to resolve the issue.
Problem: On AIX machines, adinfo may report that CentrifyDC mode is down. When trying to restart CentrifyDC or the Centrify-OpenSSH service, the following error may show:
root@hostname:/opt/freeware/lib:> Could not load program /usr/share/centrifydc/sbin/sshd: Dependent module /usr/lib/libgssapi_krb5.a( shr.o.2.2) could not be loaded. Member shr.o.2.2 is not found in archive
Cause: There may be another application installed on the machine that has implemented its own kerberos libraries. Centrify will try to use these libraries and will show errors.
Solution:
Use the ldd command to find the libraries that adclient needs. Example is below, and can also be used on linux:
Now that the required libraries are listed, the libraries can be exported to LIBPATH. It can be checked if there are any libraries already exported by running the following command:
$ echo $LIBPATH
Looking closely at the error message from above, the following line should indicate which library needs to be added to LIBPATH:
"Dependent module /usr/lib/libgssapi_krb5.a( shr.o.2.2) could not be loaded."
From the above output of the ldd command, it is seen that this path is what adclient is needing:
If this path is not showing when running the echo $ LIBPATH command, it can be exported using the following command. This will put the libraries that Centrify needs first in the LIBPATH. Currently another application's libraries are first.
Now try restarting CentrifyDC and adinfo should now show "centrifydc mode: connected." Also, restarting the Centrify-OpenSSH service should now also succeed.