Hi list,
Sorry if I'm posting to the wrong list. Please point me to the right one
if I'm wrong. Thanks.
If I configure ldapclient with only one server in the defaultServerList
it works if I reboot.
If I put multiple servers afterwards (eg: ldapclient mod -a
"defaultServerList=172.23.4.2 172.23.4.3 172.23.5.2 172.23.14.12" )
ldapclient is transitioned to maintenance on reboot and I can't clear it.
Here is the message I get in /var/svc/log/network-ldap-client:default.log :
[ f?vr. 19 14:13:24 Executing start method ("/lib/svc/method/ldap-client
start"). ]
/usr/lib/ldap/ldap_cachemgr: terminated by signal 6.
[ f?vr. 19 14:13:27 Method "start" exited with status 1. ]
Sometimes it says terminated by signal 11.
To make it work, I have to reconfigure it with only one server (
ldapclient manual etc...) and then use the ldapclient mod command to
readd my servers.
It doesn't matter which server I use for the "manual" command (as long
as it's a valid server).
As a side note, the "ldapclient manual" command fails if I use multiple
servers from the beginning, but not once ldapclient has been succesfully
configured with single server and the ldapclient mod-ed.
I'm struggling with this problem since about 5 dev builds, read sun docs
and double checked that the NS_LDAP_SERVERS in my
/var/ldap/ldap_client_file has the same format as sun docs's examples.
I'm using kerberos/gss authentication to the ldap server and suspected a
problem there, but the problem doesn't show with any of the ldap server
as long as I only use one at a time.
I can post full command lines (I always use the same copy-pasted one to
avoid typos), full ldap_client_file, klist output,... if needed.
If anyone has even the slightest clue about this issue, please share.
Thanks in advance,
Arnaud
