View Issue Details

IDProjectCategoryView StatusLast Update
0003119SOGoBackend Mailpublic2015-03-18 14:56
Reporterkiju Assigned Toludovic  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionno change required 
Platform[Server] LinuxOSDebianOS Version7 (Wheezy)
Product Versionnightly v2 
Summary0003119: no failover in ldap hostname
Description

Hi,
we have two AD servers for HA, in sogo.conf:
<pre>
SOGoUserSources = (
{
/ ... /
hostname = "ldap://ad1.example.com:389 ldap://ad2.example.com:389";
/ ... /
}
)
</pre>

when ad1.example.com is down sogo still trying to connect only first server.

Mar 02 12:26:05 sogod [27471]: [ERROR] <0x0x7f5bcfdec7a0[LDAPSource]> Could not bind to the LDAP server ldap://ad1.example.com:389 (389) using the bind DN: cn=sogo,dc=example,dc=com

TagsNo tags attached.

Activities

Christian Mack

Christian Mack

2015-03-03 10:42

developer   ~0008245

Last edited: 2015-03-03 10:43

Try with:
<pre>
hostname = "ldap://ad1.example.com:389" "ldap://ad2.example.com:389";
</pre>

kiju

kiju

2015-03-04 09:26

reporter   ~0008246

this causing a configuration error

ludovic

ludovic

2015-03-18 14:40

administrator   ~0008300

The syntax is:

hostname = "foo.server.com bar.server.com"

This is passed straight to ldap_initialize.

The man page says:

"The uri parameter may be a comma- or whitespace-separated list of URIs containing only the schema, the host, and the port fields."

Issue History

Date Modified Username Field Change
2015-03-02 12:03 kiju New Issue
2015-03-03 10:42 Christian Mack Note Added: 0008245
2015-03-03 10:43 Christian Mack Note Edited: 0008245
2015-03-04 09:26 kiju Note Added: 0008246
2015-03-18 14:40 ludovic Note Added: 0008300
2015-03-18 14:40 ludovic Status new => resolved
2015-03-18 14:40 ludovic Resolution open => no change required
2015-03-18 14:40 ludovic Assigned To => ludovic
2015-03-18 14:56 francis Description Updated