[AMBARI-13172] Kafka Service check fails with umask 027 on secure cluster

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.1.2
• Component/s: ambari-server
• Assignee: Papirkovskyy Myroslav
• Reporter: Papirkovskyy Myroslav
• Created: 21/Sep/15 18:44
• Updated: 21/Sep/15 22:17
• Resolved: 21/Sep/15 18:51

Description

Kafka service check failed with exception:

[2015-09-21 18:16:34,906] WARN SASL configuration failed: javax.security.auth.login.LoginException: Zookeeper client cannot authenticate using the 'Client' section of the supplied JAAS configuration: '/usr/hdp/current/kafka-broker/config/kafka_jaas.conf' because of a RuntimeException: java.lang.SecurityException: Configuration Error:
	No such file or directory Will continue connection to Zookeeper server without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn)
Error while executing topic command null
java.lang.ExceptionInInitializerError
	at kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:231)
	at kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:92)
	at kafka.admin.TopicCommand$.main(TopicCommand.scala:54)
	at kafka.admin.TopicCommand.main(TopicCommand.scala)
Caused by: java.lang.RuntimeException: File /usr/hdp/current/kafka-broker/config/kafka_jaas.conf cannot be read.
	at kafka.utils.ZkUtils$.<init>(ZkUtils.scala:65)
	at kafka.utils.ZkUtils$.<clinit>(ZkUtils.scala)
	... 4 more

Issue Links

• links to: ReviewBoard