@iamabug  I think I have seen the problem, can you share your Ambari UI screenshot of your configured listeners? Or where have you declared these parameters SASL_PLAINTEXT://192.168.1.1:9092,EXTERNAL://88.88.88.88:19092 listener.security.protocol.map=SASL_PLAINTEXT:SASL_PLAINTEXT,EXTERNAL:SASL_PLAINTEXT security.inter.broker.protocol=SASL_PLAINTEXT Only one broker? I am sorry I can only help in the evenings I have a full time job that consumes my time 🙂         ... View more

@svasi  For the logs I can see that the UDP port 88 used by the KDC is already in use by some application. Nov 07 12:40:19 master-1 krb5kdc[31877](info): listening on fd 10: udp ::.88 (pktinfo) Nov 07 12:40:19 master-1 krb5kdc[31877](info): listening on fd 10: udp ::.88 (pktinfo) krb5kdc: setsockopt(11,IPV6_V6ONLY,1) worked krb5kdc: setsockopt(11,IPV6_V6ONLY,1) worked krb5kdc: Address already in use - Cannot bind server socket on ::.88 krb5kdc: Address already in use - Cannot bind server socket on ::.88 Nov 07 12:40:19 master-1 krb5kdc[31877](info): set up 2 sockets Nov 07 12:40:19 master-1 krb5kdc[31877](info): set up 2 sockets   The default ports used by Kerberos are port 88 for the KDC1 and port 749 for the admin server. You can, however, choose to run on other ports, as long as they are specified in each host's /etc/services and krb5.conf files, and the kdc.conf file on each KDC Solution one Check for the PID of port 88 # netstat -tupln kill PID # kill -9 <PID> Retry your kerberiszation Solution 2 Change the port to something like 8888 in /etc/services and krb5.conf files, and the kdc.conf Restart the kdc and kadmin and retry the kerberization     ... View more

@svasi  Sorry also these 2 logs the files attached look okay, /var/log/krb5/krb5kdc.log /var/log/krb5/kadmind.log Did you create the re-create the principal? Share the output of   # kadmin.local listprincs         ... View more

@svasi  Can you share the files mentioned in my previous post? Redact site specific sensitive information and I will have a look at it.     ... View more

@Harpreet_Singh  Okay sorry for that please keep me posted  ... View more

@svasi  I saw a couple of potential issues and I would like you to make a few changes.     Recreate an admin for Kerberos Using the below syntax # kadmin.local -q "addprinc admin/admin" ----------start of output--------- Authenticating as principal root/admin@EDHDEV.COM with a password. WARNING: no policy specified for admin/admin@EDHDEV.COM; defaulting to no policy Enter the password for principal "admin/admin@EDHDEV.COM": welcome1 Re-enter password for principal "admin/admin@EDHDEV.COM": welcome1 Principal "admin/admin@EDHDEV.COM" created. ----------end of output---------   Validate the principal works # kadmin -p admin/admin@EDHDEV.COM   It will ask for the password once successfully authenticated then type q to quit Can you leave the default encryption types? and you should select Manage krb5.conf through Cloudera Manager Don't change the kadm5.acl file it's okay the way it is !!   I saw something missing in your krb5.conf between [realms] and [logging] the domain_realm add that to all the hosts if it's a multinode [realms] EDHDEV.COM = { kdc = master-1.dev.edl.gcp.domain.it admin_server = master-1.dev.edl.gcp.domain.it }   [domain_realm] .edhdev.com = EDHDEV.COM edhdev.com = EDHDEV.COM   [logging] kdc = FILE:/var/log/krb5/krb5kdc.log admin_server = FILE:/var/log/krb5/kadmind.log default = SYSLOG:NOTICE:DAEMON   Go to the CM and launch the kerberization using  this below the principal   admin/admin@EDHDEV.COM   Please make the above changes restart the kdc and retry kerberization it should go smoothly Happy hadooping  ... View more