[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: OpenLDAP configured for TLS not listenting on port 636

Dieter,

The quotes are for the shell so that "ldap:/// ldaps:///" are not broken into two hunks by shell. They won't show up in a "ps" command because they're not passed (and aren't supposed to be passed) to slapd. Thanks to some help from Geert Van Muylen, I found the source of the problem in the startup script and fixed it. It will take me a while to actually understand the failure mechanism, but since I could pinpoint it, I was able to successfully work around it.

-- Rob

On 10/30/2006 11:47 PM, Dieter Kluenter wrote: 
Rob Tanner <rtanner@linfield.edu> writes:


  
A ps command confirms that the start-up script did the right thing:

/usr/local/libexec/slapd -u ldap -h ldap:/// ldaps:///

But ssl connections fail and a netstat command only shows the server
listening on port 389.

Is there something I'm missing at this point merely to get the server
listening on port 636?
    

The examples in man slapd(8) show the URLlist quoted 

    -h "ldap:/// ldaps:///"


-Dieter

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature