LDAP profile refresh may store the incorrect IP-address in "NS_LDAP_SERVERS= 0.0.0.0" in the /var/ldap/ldap_client_file (Doc ID 1592843.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 11 11/11 to 11.2 [Release 11.0]
Information in this document applies to any platform.

Symptoms

 

The issue described in this document does only apply to LDAP clients using Solaris 11 and newer, but not to any older versions of Solaris.

 

 
If the LDAP client on a Solaris 11 system had become configured to use a LDAP client profile that does contain of an attribute/value pair for preferredServerList, but no attribute/value pair for defaultServerList, then the LDAP client recreate the /var/ldap/ldap_client_file configuration file with the incorrect IP-address "0.0.0.0" in the parameter NS_LDAP_SERVERS, and also import that incorrect IP-address into the properties of the SMF service svc:/network/ldap/client:default.

This configuration change, that does automatically happen every time when the LDAP client performs a profile refresh (which by default is on every 12 hours) may cause other SMF services that do depend on LDAP, such as the SMF service svc:/network/nfs/client:default, to get restarted.

Example for such a profile:

 

After having become configured and enabled with that once, the LDAP client will refresh this configuration on every time when the profileTTL expires.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms