Hi there,
I'm running a test installation to test Zimbra if it's suitable for deployment for us. It looks very promising; it has just about everything we need. However, I can't get the external GAL (global address list) to work. Whatever I enter as configuration, I get this notice:
service.FAILURE
system failure: unable to search gal
btpool0-37:https://192.168.1.106:7071/service/a...5a9d43387b042d
The LDAP server we're using is ruby-ldapserver. This parses the LDAP query and executes an SQL statement on our people database and gives the result back as an LDAP tree.
This setup works both in Thunderbird and the ldap tool ldapsearch. However, when I use the ldapsearch binary on my zimbra machine, it says this:
Google doesn't yield anything about that error.# extended LDIF
#
# LDAPv3
# basewith scope subtree
# filter: (cn=*halfgaar*)
# requesting: ALL
#
# extended result response
extended:
result: 2 Protocol error
text: header too long
# numResponses: 1
# numExtended: 1
What can I do to trace this? The log files aren't giving me a lot of information.
Thanks in advance.
Edit: almost solved. It was having problems with the gn= search query in the filter. However, now whenever I have query with a wildcard in it, it is extremely slow. CPU is idle when it's hanging on its test query.
Edit2: I added some debug notices to our ldap server and the filter query it contains, literally contains %s. So, zimbra doesn't seem to be replacing %s with what the user types. Further investigation is required.


LinkBack URL
About LinkBacks

