I want to create a new virtual organisation with the gridware application AliEn and when I try to configure the LDAP server I get the following error. I can't figure out the problem.
Here is the error :


Proceed with creation [Y]:Y
Creating /home/alienmaster/.alien/var/lib/alien-ldap... ok
Crypting password... ok
Reading old /opt/alien/etc//openldap/slapd.conf... ok
Writing the new configuration...
Changing /opt/alien/ for /opt/alien/
Changing directory\s+/var/lib/alien-ldap for directory /home/alienmaster/.alien/var/lib/alien-ldap
all changes done!!...
Changing DIRECTORY=/opt/alien.* for DIRECTORY=/opt/alien
Changing /opt/alien/ for /opt/alien/
all changes done!!...ok
Starting the daemon...
Starting ldap as user alienmaster
LOOKING FOR slapd
LOOKING FOR slurpd
Starting ldap: [ OK ]
Enter PEM pass phrase:Connecting to the ldap server testbed02.grid.spacescience.ro:8389... failed
Error conecting to the ldap server
0 and Connection refused and IO::Socket::INET: connect: Connection refused

8389 is an odd port for LDAP. Try 389 instead, or 636 for that matter,
since you seem to be using encryption.


Cheers,
Tink

I don't think it's a problem with port I'm using. Acctualy, the inintial port number that the script is asking for, has the implicit 8080 value. But when it's trying to connect to the LDAP server, he uses the 8389 port.

Is it possible that I need another LDAP server on my machine? I don't really think so, because this script is tring to create a LDAP server.
Or could it be a conflict with another LDAP server, like openldap? (though I don't find any other in my services list)

As I said: the "official" ports for ldap according to services (and
in environments where I've used ldap) are 389 and 636. You could
run netstat to see which ports what is listening on. I may be off
on a tangent, though, since I have no clue what AliEn is or how it
works internally. It could well be that you missed a step and didn't
create a proper Cert for its authentication.


Cheers,
Tink