On 05/25/2013 01:34 PM, Graham Leggett wrote:
Just to recount an experience in the hope that it saves someone else some trouble.
I was trying to use the ./db2index.pl script to regenerate my indexes, and the script
point blank refused to work, telling me:
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
To debug this, hack the db2index.pl script to pass the "-d 1" parameter to
ldapsearch, which tells ldapsearch to give debug messages instead of the cryptic failure
In my case it revealed that db2index.pl was trying to contact the externally accessible
public IP of the box on port 389, instead of localhost as it should have in my case. To
fix the problem I had to manually hack the script.
Ideally this script shouldn't make blind assumptions as to the name of the LDAP
server, but leave it up to the caller.
Please file a ticket. But I don't understand - why was it a problem for
db2index.pl to use the publicly accessible IP address? That's the same
hostname/IP address you provided when you ran setup to create the
directory server instance?
389 users mailing list