129107 - unknown error returned when LDAP tools fail to connect

Status: RESOLVED DUPLICATE of bug 206018

(Directory :: LDAP Tools, defect, P3)

Description

[Mark Smith [:mcs]]

ldapsearch and friends fail this way if they fail to connect due to a TCP
timeout:

ldap_simple_bind: Can't connect to the LDAP server - unknown error


I suspect the problem is that the tools use NSPR (via the prldap layer) but do
not retrieve the NSPR error code. But that is just a theory.  Reproduce by
issuing a command with an IP address that can't be found, e.g.,

ldapsearch -h 0.0.0.1 -s base -b '' ''

Comment 1

[Frankie]

Spam for bug 129472

Comment 2

[Wayne Mery (:wsmwk)]

is the jist of this, that the user should be told "TCP timeout" instead of unknown error?

Comment 3

[Nikolay Shopik]

I think we had same problem in TB in past, but can't find bug about that. Because if i remember correctly this was fixed since 3.0 released in ldap code.

Comment 4

[Wayne Mery (:wsmwk)]

are you thinking of Bug 206018?  ldap connections not close properly, LDAP/SSL triggers internal failure error message

all ldap bugs fixed since mid 2007 http://bit.ly/bCcrKB

Comment 5

[Nikolay Shopik]

(In reply to comment #4)
> are you thinking of Bug 206018? 
yep

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to comment #5)
> (In reply to comment #4)
> > are you thinking of Bug 206018? 
> yep