Cause:This can happen if there is some other client process gained lock on the ambari DB. There was another ambari-server which was connecting to the same ambari database which seems to be causing the issue.
Solution:Make sure that no other client process or ambari server connecting to the same Ambari DB instance or gained lock when the main Ambari Server is trying to insert records inside the DB.
Stop the other ambari-server / client process then restart ambari server proceed to enable kerberos.

This website uses cookies for analytics, personalisation and advertising. To learn more or change your cookie settings, please read our Cookie Policy. By continuing to browse, you agree to our use of cookies.