Watashi wrote:
May 17 14:48:06 paramana authdaemond: ldap operation returned error code: 1
...
Return 1 - LDAP_OPERATIONS_ERROR: Indicates an internal error. The server is
unable to respond with a more specific error and is also unable to properly
respond to a request. It does not indicate that the client has sent an
erroneous message.
Well, crap. It's returning the most general error it could. It tells
us almost nothing about the failure.
It's probably a bug, either in the directory server or the openldap
client libraries (and I'd guess the latter). You'll probably need to
follow up with the openldap developers. I presume that you're using the
openldap server?
I use Debian Etch AMD64 and here are my packages:
ii libldap-2.2-7 2.2.23-8 OpenLDAP
libraries
ii libldap-2.3-0 2.3.30-5 OpenLDAP
libraries
ii libldap2 2.1.30-13.3 OpenLDAP
libraries
ii libldap2-dev 2.1.30-13.3 OpenLDAP
development libraries
So, what can I do now? Thank again!
Did you build courier on this system? If so, it probably used the
rather old version of the openldap (libldap2-dev) client libraries. I'm
not sure what the package name would be, but consider trying to remove
libldap2-dev, and installing the dev package for libldap-2.3. Then
rebuild and reinstall courier-authlib.
If the latest client library exhibits the same problem, I'd recommend
detailing the platform and all ldap packages on both your production
ldap server, and the courier server. Then configure courier to use the
production server, and get another ethereal capture of the exchange.
Keep the complete capture, including the connection initiation, bind as
'cn=linuxbind,ou=Login_Anonimous,dc=test,dc=com', and both searches that
are being logged. You can present that to the openldap developers and
see what hints they can give you.
11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] RES: Limits with ...
.patch
