After nsswitch2/sparks project integration, libsldap seems to be keeping connections open
(for later use) for processes other than nscd. Before nsswitch2 integration only nscd
was keeping the connections open for later use. This new behaviour introduced by nsswitch2
seems to be causing issues with automound, svc.startd and ldap_cachemgr. The following error messages are logged by these processes that seem to indicate issues with using an already open connection to server.
Sep 20 12:06:19 dnvpars01 ldap_cachemgr[1436]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Er
ror occurred during receiving results. This may be due to a stalled connection.
Sep 20 12:06:19 dnvpars01 ldap_cachemgr[1436]: [ID 186574 daemon.error] Error: Unable to refresh profile:apc.srv_expl: LD
AP ERROR (81): Error occurred during receiving results. This may be due to a stalled connection.
Sep 20 12:34:53 dnvpars01 automountd[1617]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Error
occurred during receiving results. This may be due to a stalled connection.
Sep 20 13:17:50 dnvpars01 automountd[307]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Error
occurred during receiving results. This may be due to a stalled connection.
:
:
:
Sep 21 10:31:37 dnvpars01 automountd[307]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Error
occurred during receiving results. This may be due to a stalled connection.
Sep 21 10:53:34 dnvpars01 automountd[307]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Error
occurred during receiving results. This may be due to a stalled connection.
:
:
Sep 20 13:20:46 dnvpars01 svc.startd[7]: [ID 293258 daemon.warning] libsldap: Status: 81 Mesg: LDAP ERROR (81): Error occurred during receiving results. This may be due to a stalled connection.
Sep 20 13:25:57 dnvpars01 svc.startd[7]: [ID 293258 daemon.warning] libsldap: Status: 2 Mesg: Unable to load configuration '/var/ldap/ldap_client_file' ('').