Issue #100: BIND won't start when KDC is unavailable - reconnect is missing - bind-dyndb-ldap

bind-dyndb-ldap

#100 BIND won't start when KDC is unavailable - reconnect is missing

Closed: Fixed None Opened 11 years ago by pspacek.

04-Dec-2012 12:40:29.122 Failed to init credentials (Cannot contact any KDC for realm 'E.TEST')
04-Dec-2012 12:40:29.122 [ldap_helper.c  : 2206: ldap_connect         ] check failed: failure
04-Dec-2012 12:40:29.122 couldn't establish connection in LDAP connection pool: failure
04-Dec-2012 12:40:29.122 [ldap_helper.c  :  498: new_ldap_instance    ] check failed: failure
04-Dec-2012 12:40:29.122 [zone_manager.c :  151: manager_create_db_instance] check failed: failure
04-Dec-2012 12:40:29.123 loading configuration: failure
04-Dec-2012 12:40:29.123 exiting (due to fatal error)

In case of connection timeout we try to reconnect after reconnect_interval.

pspacek commented 11 years ago

Patch is on review, but this change depends on IPA ticket #3429.

pspacek commented 11 years ago

Fixed by d4db1cb.

IPA part is not done at the moment.

pspacek commented 10 years ago

It was fixed in version 2.6 back in March 2013.

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 19

7 years ago

Metadata

Assignee

pspacek

Tags

None

Blocking

None

Depending on

None

Priority

major

Milestone

Fedora 19

rhbz

blockedby

None

blocking

None

fixedby

d4db1cbc35575595b3144adf3dd7f3a885b0f5a7

fixedin

2.6

proposedmilestone

None

type

defect

component

ldap driver

version

2.3

keywords

nihsyndrome

None

bind-dyndb-ldap

Source Code

Documentation

#100 BIND won't start when KDC is unavailable - reconnect is missing Closed: Fixed None Opened 11 years ago by pspacek.

Metadata

#100 BIND won't start when KDC is unavailable - reconnect is missing

Closed: Fixed None Opened 11 years ago by pspacek.