Hi Claus and Roy,
Thanks for the reply.
In fact nothing to do with sendmail, I pasted the wrong lines from /var/adm/messages, sorry for that
LDAP Server: OpenLdap Linux LDAP Clients: Linux, Solaris 10, Solaris 9 and Solaris 8
Following command works fine for Solaris 10 but it doesn't work for 8 and 9. Please help me I really need to sort out this.
ldapclient -v manual -a defaultServerList=10.10.10.10 -a defaultSearchBase=dc=test,dc=com -a authenticationMethod=tls:simple -a serviceAuthenticationMethod=pam_ldap:tls:simple -a credentialLevel=proxy -a serviceAuthenticationMethod=passwd-cmd:tls:simple -a proxyDN=cn=proxyagent,ou=Profile,dc=test,dc=com -a proxyPassword=test
When I ran ldaplist I get following in /var/adm/messages on Solaris 9
Mar 21 23:35:38 web04 ldaplist[1932]: [ID 293258 user.warning] libsldap: Status: 81 Mesg: openConnection: simple bind failed - Can't contact LDAP serverMar 21 23:35:38 web04 ldaplist[1932]: [ID 292100 user.warning] libsldap: could not remove 203.221.221.83 from servers listMar 21 23:35:38 web04 ldaplist[1932]: [ID 293258 user.warning] libsldap: Status: 7 Mesg: Session error no available conn.
While on server I get following in debugs
Mar 21 23:29:50 rhapp04-t1 slapd[15119]: connection_read(10): checking for input on id=0Mar 21 23:29:50 rhapp04-t1 slapd[15119]: connection_read(10): TLS accept error error=-1 id=0, closingMar 21 23:29:51 rhapp04-t1 slapd[15119]: connection_closing: readying conn=0 sd=10 for close
Really appreciate if someone shows me the right way to solve this issue.
Cheers,
Farhan
Hello Farhan,
I experienced a similar issue with the ldap tools via Solaris 8, it appears as if this is somewhat broken. To make sure: Are your nsswitch.conf[.ldap!] settings correct, especially the hosts line that the server can even be found? I am not sure about Solaris 8 and 9, but for Solaris 10, when starting ldapclient, the nsswitch.ldap is copied to nsswitch.conf, so perhaps a necessary setting gets lost during startup (that is what happened here during the reboot to get into production - almost had a heart attack)?
The message
"Can't contact LDAP server" sounds a bit as if something like that might be the case.
Claus
Kick, Claus wrote:
Hello Farhan,
I experienced a similar issue with the ldap tools via Solaris 8, it appears as if this is somewhat broken.
Solaris 8's native client had no TLS support, but that supposedly was fixed in Solaris 10. All in all it's easier to just use PADL's client instead, and have known/consistent behavior all the time.
To make sure: Are your nsswitch.conf[.ldap!] settings correct, especially the hosts line that the server can even be found? I am not sure about Solaris 8 and 9, but for Solaris 10, when starting ldapclient, the nsswitch.ldap is copied to nsswitch.conf, so perhaps a necessary setting gets lost during startup (that is what happened here during the reboot to get into production - almost had a heart attack)?
The message
"Can't contact LDAP server" sounds a bit as if something like that might be the case.
Claus
openldap-technical@openldap.org
-
farhan ahmed -
Howard Chu -
Kick, Claus