@ Ruslan Fialkovsky Are you doing some lab, this looks familiar can you share the link, I want to see if I can reproduce it on my cluster? ... View more

@ Ruslan Fialkovsky Is your nifi part of the kerberized cluster or is a separate HDF cluster? What are versions of the components NIF,HDP etc ? ... View more

@Ruslan Fialkovsky Can you open a new thread and share the problems you are encountering so you can get help, I am afraid this thread is not active. HTH ... View more

@Gaurang Shah Could this be what you are looking for? Status of HDP components using Ambari API HTH ... View more

@Lindsay Gaff If you found this answer addressed your question, please take a moment to log in and click the "accept" link on the answer. That would be a great help to Community users to find the solution quickly for these kinds of errors. ... View more

@Javert Kirilov Glad to know your case was resolved.......No everything was generated automatically by running the Kerberos Wizard. ... View more

@Javert Kirilov Resend the linkedin invitation deleted by error ... View more

@Javert Kirilov I have just completed the kerberization of a Single node Centos 7 HDP3.1.0.0 running Ambari 2.7.3.0 everything went as planned no hiccups. See attached screenshots krb5.conf [libdefaults] renew_lifetime = 7d forwardable = true default_realm = UGANDA.UG ticket_lifetime = 24h dns_lookup_realm = false dns_lookup_kdc = false default_ccache_name = /tmp/krb5cc_%{uid} #default_tgs_enctypes = aes des3-cbc-sha1 rc4 des-cbc-md5 #default_tkt_enctypes = aes des3-cbc-sha1 rc4 des-cbc-md5 [domain_realm] .uganda.ug = UGANDA.UG uganda.ug = UGANDA.UG [logging] default = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log kdc = FILE:/var/log/krb5kdc.log [realms] UGANDA.UG = { admin_server = pawor.uganda.ug kdc = pawor.uganda.ug } kadm5.acl */admin@UGANDA.UG * kdc.conf [kdcdefaults] kdc_ports = 88 kdc_tcp_ports = 88 [realms] UGANDA.UG = { #master_key_type = aes256-cts acl_file = /var/kerberos/krb5kdc/kadm5.acl dict_file = /usr/share/dict/words admin_keytab = /var/kerberos/krb5kdc/kadm5.keytab supported_enctypes = aes256-cts:normal aes128-cts:normal des3-hmac-sha1:normal arcfour-hmac:normal camellia256-cts:normal camellia128-cts:normal des-hmac-sha1:normal des-cbc-md5:normal des-cbc-crc:normal } To help in the diagnostics can you align your configuration to mine mapping your REALM and Server values and retest! Can you try start the services manually, run the start date nodes command on all the data nodes su -l hdfs -c "/usr/hdp/current/hadoop-hdfs-namenode/../hadoop/sbin/hadoop-daemon.sh start secondarynamenode" su -l hdfs -c "/usr/hdp/current/hadoop-hdfs-datanode/../hadoop/sbin/hadoop-daemon.sh start datanode" Take a keen interest in the supported_enctypes and compare with your cluster I don't think adding all the encryption types will help:-) ... View more