This problem started when someone deleted my /etc/krb5.keytab file.  I am 
trying to get the named service working again.  I am following the docs: What 
to do when named with bind-dyndb-ldap cannot start   
https://docs.pagure.org/bind-dyndb-ldap/BIND9/NamedCannotStart.html

1 Gather logs-
A. my system is Rocky 8.7 and does not contain /var/log/messages.  Really!  I 
was surprised too and wondering why not.  I thought that was a standard log 
that all EL systems had.
B /var/named/data/named.run is a file with zero size.  Yes, it's unfortunately 
empty.
>>>What did you change before it started to fail? :-)   /etc/krb5.keytab was 
>>>deleted.  See post - 
>>>https://lists.fedoraproject.org/archives/list/[email protected]/thread/7AXKGNWWNLHIGOIRVLH7QCN26W76ZVT4/

2. >>>Server ldap/[email protected] not found in Kerberos database
This is not an issue.  hostname displays FQDN and  /etc/hosts is correctly 
formatted as shown in the correct line example

3>>>Failed to init credentials or Failed to get initial credentials
This is not an issue for /etc/named.keytab, the version of klist and kvno match

HOWEVER, /etc/krb5.keytab does not match when running klist and kvno  
Could this have the same effect?  To cause named not to start?

Should I continue down the list and also get some more info from setting up the 
trace export KRB5_TRACE=/tmp/named_krb5.log or fix the issue with 
/etc/krb5.keytab first?

At this point I think I will stop investigating until I get a more clear 
understanding of my questions.  I hope someone can assist.  Many thanks in 
advance!
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to