0003927: no failover in ldap hostname - SOGo

ID	Project	Category	View Status	Date Submitted	Last Update

0003927	SOGo	Backend General	public	2016-12-02 14:21	2016-12-30 20:12

Reporter	detrich	Assigned To	ludovic
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	no change required
Platform	[Server] Linux	OS	RHEL/CentOS	OS Version	7
Product Version	3.2.3

Summary	0003927: no failover in ldap hostname
Description	Hi, we have two LDAP servers for HA, in sogo.conf: SOGoUserSources = ( { / ... / hostname = "ldap://ldap1.example.com:389 ldap://ldap2.example.com:389"; / ... / } ) when ldap1.example.com is down sogo still trying to connect only first server.
Tags	No tags attached.

ludovic 2016-12-06 21:19 administrator ~0010955	That was tested before and it was working. SOGo doesn't handle this directly - it's the LDAP library that does it automatically for SOGo.

ludovic 2016-12-30 20:12 administrator ~0011149	Tested and it works correctly. I've added: hostname = "ldap://172.20.20.50:389 ldap://127.0.0.1:3389"; 172.20.20.50 being a bogus LDAP server and SOGo (well, openldap's client library) tried 172.20.20.50 and then, switched to 127.0.0.1. It sent two TCP SYNC packets to the 172.20.20.50 IP, and got two RST/ACK.

Date Modified	Username	Field	Change
2016-12-02 14:21	detrich	New Issue
2016-12-06 21:18	ludovic	Severity	major => minor
2016-12-06 21:19	ludovic	Note Added: 0010955
2016-12-30 20:12	ludovic	Note Added: 0011149
2016-12-30 20:12	ludovic	Status	new => closed
2016-12-30 20:12	ludovic	Assigned To	=> ludovic
2016-12-30 20:12	ludovic	Resolution	open => no change required