bind-dyndb-ldap

#133 Handle "Failed to init credentials (Resource temporarily unavailable)" in a better way

Opened 10 years ago by pspacek. Modified 7 years ago

Enhancement proposal

Named should not fail to start because of temporary GSSAPI problem:

named: Failed to init credentials (Resource temporarily unavailable)
named: loading configuration: failure
named: exiting (due to fatal error)

It should be more resilient.

Proposed implementation

Re-try after configured timeout.

pspacek commented 10 years ago

Nice to have, it will be handled after DNSSEC support. Maybe it can be solved by GSSProxy...

mkosek commented 9 years ago

As per discussion with Petr - no cloning for now.

pspacek commented 8 years ago

These tickets are not directly related to upcomming FreeIPA 4.4 features.

pspacek commented 8 years ago

Moving tickets as triaged on 2016-02-11 with mkosek. These tickets are not going to be implemented without strong need/good justification.

I'm setting priority to 'critical' so these tickets stay on top of The Backlog bucket.

Metadata Update from @pspacek:
- Issue assigned to someone
- Issue set to the milestone: The Backlog

7 years ago

Metadata

Assignee

someone

Tags

None

Blocking

None

Depending on

None

Priority

critical

Milestone

The Backlog

rhbz

blockedby

None

blocking

None

fixedby

None

fixedin

None

proposedmilestone

The Backlog

type

enhancement

component

ldap driver

version

None

keywords

nihsyndrome

None

bind-dyndb-ldap

Source Code

Documentation

#133 Handle "Failed to init credentials (Resource temporarily unavailable)" in a better way Opened 10 years ago by pspacek. Modified 7 years ago

Close issue as:

Enhancement proposal

Proposed implementation

Metadata

#133 Handle "Failed to init credentials (Resource temporarily unavailable)" in a better way

Opened 10 years ago by pspacek. Modified 7 years ago