Thunderbird's address book cannot connect to LDAP server but doesn't show any error message. Reports "No contacts"
Categories
(MailNews Core :: LDAP Integration, defect)
Tracking
(thunderbird_esr115 affected)
Tracking | Status | |
---|---|---|
thunderbird_esr115 | --- | affected |
People
(Reporter: mozilla, Unassigned)
References
(Depends on 2 open bugs)
Details
Comment 2•11 years ago
|
||
Comment 7•11 years ago
|
||
Comment 9•11 years ago
|
||
Comment 10•10 years ago
|
||
Comment 12•10 years ago
|
||
Updated•9 years ago
|
Updated•6 years ago
|
Updated•2 years ago
|
Comment 13•2 years ago
|
||
Alain,
Does this still reproduce for you?
ldap has changed significantly in the past couple years
Reporter | ||
Comment 14•2 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #13)
Alain,
Does this still reproduce for you?ldap has changed significantly in the past couple years
Still an issue.
Searching in Adressbook says "No contacts" without any other explanation.
Updated•2 years ago
|
Updated•9 months ago
|
Comment 16•8 months ago
|
||
Sören, can you reproduce this?
How can I test this? I don't use LDAP.
Comment 17•8 months ago
|
||
You would need an ldap server, for example https://www.hostmyapple.com/blog/10-easy-steps-to-setup-openldap
But I think we really need an ldap log from the reporter, Alain. For version 102 and 115 the logging instructions are https://wiki.mozilla.org/MailNews:Logging#Thunderbird_Logging (different from earlier)
Updated•8 months ago
|
Reporter | ||
Comment 18•8 months ago
|
||
In 115, the behavior improved slightly. Connection refused errors to LDAP servers are now at least logged as such into the error console. However, there is still no obvious feedback to the user that something is amiss (no popup, no triangular warning sign), the UI just pretends that the address isn't there.
For an LDAP server which is unreachable, we no longer have a freeze, which is good.
Reporter | ||
Comment 19•8 months ago
|
||
In case you need the debug log:
mailnews.ldap: Connecting to ldap://localhost:1389 3 LDAPClient.jsm:49:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [1] BindResponse resultCode=0 message="" LDAPClient.jsm:209:20
mailnews.ldap: Searching dn="ou=people" filter="(|(cn=*paul.)(mail=paul.)(givenName=paul.)(sn=paul.))" LDAPClient.jsm:140:18
mailnews.ldap: C: [2] SearchRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [2] SearchResultEntry <empty string> 100 LDAPClient.jsm:209:20
mailnews.ldap: S: [2] SearchResultDone resultCode=4 message="" LDAPClient.jsm:209:20
mailnews.ldap: C: [3] UnbindRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [4] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [4] BindResponse resultCode=0 message="" LDAPClient.jsm:209:20
mailnews.ldap: Searching dn="ou=people" filter="(|(cn=*paul.)(mail=paul.)(givenName=paul.)(sn=paul.))" LDAPClient.jsm:140:18
mailnews.ldap: C: [5] SearchRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [6] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [6] BindResponse resultCode=0 message="" LDAPClient.jsm:209:20
mailnews.ldap: Searching dn="ou=people" filter="(|(cn=*paul.**)(mail=paul.)(givenName=paul.)(sn=paul.))" LDAPClient.jsm:140:18
mailnews.ldap: C: [7] SearchRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [5] SearchResultEntry <empty string> 100 LDAPClient.jsm:209:20
mailnews.ldap: S: [5] SearchResultDone resultCode=4 message="" LDAPClient.jsm:209:20
mailnews.ldap: C: [8] UnbindRequest LDAPClient.jsm:281:18
(When testing with iptables dropping packets to simulate a network outage, there was a long delay between the first line, and the rest, which only followed after I removed the drop rule again).
N.B. Without setting mailnews.ldap.loglevel to All, there is nothing at all in the error log for this failure case!
Reporter | ||
Comment 20•8 months ago
|
||
Didn't wait long enough. Here's another trace with the blocking iptables rule left in place
mailnews.ldap: Connecting to ldap://localhost:1389 5 LDAPClient.jsm:49:18
mailnews.ldap: Connection closed 2 LDAPClient.jsm:253:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: Connected LDAPClient.jsm:161:18
mailnews.ldap: Binding gouv.etat.lu\NQO344 LDAPClient.jsm:71:18
mailnews.ldap: C: [1] BindRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [1] BindResponse resultCode=0 message="" LDAPClient.jsm:209:20
mailnews.ldap: Searching dn="ou=people" filter="(|(cn=xavier.b*)(mail=xavier.b)(givenName=xavier.b)(sn=xavier.b))" LDAPClient.jsm:140:18
mailnews.ldap: C: [2] SearchRequest LDAPClient.jsm:281:18
mailnews.ldap: S: [2] SearchResultEntry <empty string> 5 LDAPClient.jsm:209:20
mailnews.ldap: S: [2] SearchResultDone resultCode=0 message="" LDAPClient.jsm:209:20
mailnews.ldap: C: [3] UnbindRequest LDAPClient.jsm:281:18
=> so, after the timeout, it just continues like nothing happened, and sends its LDAP search request onto a socket which is not actually connected!
Description
•