Arch Linux

Description:
freeradius refuse to start when ldap server no available.

Additional info:
* package version: freeradius 3.0.16

* config
pool {
start = 0
...
}
From http://networkradius.com/doc/3.0.10/raddb/mods-available/pool.html

"It is sometimes useful to have the server start even when the back-end database is down or unreachable. Setting start = 0 will tell the server to initialize the pool with no connections. The pool and module initialization will then succeed, and the server will start."

-> When using 'rlm_sql' module with same 'pool' configuration, and no database
available, freeradius start correctly.

Steps to reproduce:
1. Configure freeradius to bind to one ldap server
2. Make ldap server not started
3. Start freeradius 3.0.16: it will fail to start

*logs(extract) of command 'radiusd -X':

rlm_ldap (ldap): Loading dynamic clients
rlm_ldap (ldap): 0 of 0 connections in use. You may need to increase "spare"
rlm_ldap (ldap): Opening additional connection (0), 1 of 32 pending slots used
rlm_ldap (ldap): Connecting to ldap://my-ldap-server:636
rlm_ldap (ldap): Bind with uid=radius,ou=users,dc=lan1 to ldap://my-ldap-server:636 failed: Can't contact LDAP server
rlm_ldap (ldap): Opening connection failed (0)
/etc/raddb/mods-enabled/ldap[312]: Error loading clients
/etc/raddb/mods-enabled/ldap[8]: Instantiation failed for module "ldap"

* Severity is set to 'high' because there is no work-around solution