Don't put the Slapd on the same machine than the Sogo server, but slapd and
LDAP database should be on the same server.
Louis
2010/10/12 Dennis Petschull d.petsch...@two4.it
Hi Louis,
I just tried it out. As I expected, this does not work, as the slapd is
looking for the socket on the ldap server, whereas the actual socket is of
course on the sogo server.
Here is the error message from the syslog on the ldap server:
slapd[2631]: socket connect(/var/run/sogo/sogo-sockd.sock) failed
So, is there anybody who did this already with ldap and sogo being on
different
hosts??
Cheers,
Dennis
On Monday 11 October 2010 11:16:15 ketzal devims wrote:
Hi Dennis,
For my configuration, I did it in a Co-localized server, but I'm pretty
sure you can do it with two different servers. (If you're not sure, try
it
:))
Regs
Louis
2010/10/11 Dennis Petschull d.petsch...@two4.it
Hi Valentin,
In general you're right. But are you sure that this also holds true
for
this special use-case of the sogo-slapd-sockd?
As I understand, the users ldap query triggers the ldap server to ask
the
socket, specified in the ldap-directory.
But the socket address is only present on the sogo server (where the
sogo-slapd-sockd command was executed), not on the ldap server itself.
Or am I missing something here??
Cheers,
Dennis
On Monday 11 October 2010 09:20:43 Valentin Bud wrote:
Hello Dennis,
On Sun, Oct 10, 2010 at 10:15 PM, Dennis Petschull
d.petsch...@two4.it
wrote:
Hi Louis,
thanks for your help. I think I can manage it now...
But now that I'm setting it all up, a question came to my mind:
For all of this to work out, the LDAP server and the SOGo server
need
reside
on the same host, right? Or is it also possible when LDAP and SOGo
servers are
on different hosts??
Doesn't matter if SOGo and LDAP are on the same server or not. You
must
point SOGo
to the LDAP server either using DNS name or IP address.
a great day,
v
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists
