@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
