You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Myroslav Papirkovskyy (JIRA)" <ji...@apache.org> on 2015/09/21 20:45:04 UTC
[jira] [Created] (AMBARI-13172) Kafka Service check fails with
umask 027 on secure cluster
Myroslav Papirkovskyy created AMBARI-13172:
----------------------------------------------
Summary: Kafka Service check fails with umask 027 on secure cluster
Key: AMBARI-13172
URL: https://issues.apache.org/jira/browse/AMBARI-13172
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.1.2
Reporter: Myroslav Papirkovskyy
Assignee: Myroslav Papirkovskyy
Priority: Blocker
Fix For: 2.1.2
Kafka service check failed with exception:
{noformat}
[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
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)