#1994 Complain loudly if backend doesn't start due to missing or invalid keytab
Closed: Fixed None Opened 5 years ago by jhrozek.

The sssd_be loads the keytab on start and checks for the expected principal. In case the keytab is wrong or the principal is missing, there is no explanation with the default logging, just:

(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [load_backend_module] (0x0010): Error (2) in module (ipa) initialization (sssm_ipa_id_init)!
(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [be_process_init] (0x0010): fatal error initializing data providers
(Thu Jun 20 17:50:54 2013) [sssd[be[ipa.example.com]]] [main] (0x0010): Could not initialize backend [2]

We should make it clear that the back end didn't start due to wrong keytab.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => todo

Fields changed

keywords: => easyfix

Fields changed

mark: => 0

Fields changed

owner: somebody => preichl

(Fri Jun 19 15:25:26 2015) [sssd[be[ipa.work]]] [select_principal_from_keytab] (0x0010): Failed to read keytab [default]: No such file or directory
(Fri Jun 19 15:25:26 2015) [sssd[be[ipa.work]]] [load_backend_module] (0x0010): Error (2) in module (ipa) initialization (sssm_ipa_id_init)!
(Fri Jun 19 15:25:26 2015) [sssd[be[ipa.work]]] [be_process_init] (0x0010): fatal error initializing data providers
(Fri Jun 19 15:25:26 2015) [sssd[be[ipa.work]]] [main] (0x0010): Could not initialize backend [2]

Output from 'select_principal_from_keytab' seems enough for me - what else should we be hiniting?

sensitive: => 0

After discussing this ticket with Jakub we decided that current logging message is sufficient, so we can close the ticket.

[select_principal_from_keytab] (0x0010): Failed to read keytab [default]: No such file or directory

_comment0: => 1434967298239355
resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.1

2 years ago

Login to comment on this ticket.

Metadata