ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12828) Kafka Service check fails after adding it to secure cluster
Date Thu, 20 Aug 2015 14:58:46 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-12828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705064#comment-14705064
] 

Hudson commented on AMBARI-12828:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #3301 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3301/])
AMBARI-12828 Kafka Service check fails after adding it to secure cluster (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=78d04fe4579e30c5bc9eaa7db34a610b897bd2d1)
* ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/kerberos.json


> Kafka Service check fails after adding it to secure cluster
> -----------------------------------------------------------
>
>                 Key: AMBARI-12828
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12828
>             Project: Ambari
>          Issue Type: Bug
>          Components: stacks
>    Affects Versions: 2.1.1
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-12828.patch
>
>
> Kafka check fails with:
> {code}
> [2015-08-17 05:27:54,331] 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:\n\tNo such file or directory Will continue connection to Zookeeper server
without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn)\nError
while executing topic command null\njava.lang.ExceptionInInitializerError\n\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:231)\n\tat
kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:92)\n\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:54)\n\tat
kafka.admin.TopicCommand.main(TopicCommand.scala)\nCaused by: java.lang.RuntimeException:
File /usr/hdp/current/kafka-broker/config/kafka_jaas.conf cannot be read.\n\tat kafka.utils.ZkUtils$.<init>(ZkUtils.scala:65)\n\tat
kafka.utils.ZkUtils$.<clinit>(ZkUtils.scala)\n\t... 4 more\n\n2015-08-17 05:27:54,710
- call returned (0, \"[2015-08-17 05:27:54,331] 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:\\n\\tNo such file or directory Will continue connection to Zookeeper
server without SASL authentication, if Zookeeper server allows it. (org.apache.zookeeper.ClientCnxn)\\nError
while executing topic command null\\njava.lang.ExceptionInInitializerError\\n\\tat kafka.admin.AdminUtils$.createTopic(AdminUtils.scala:231)\\n\\tat
kafka.admin.TopicCommand$.createTopic(TopicCommand.scala:92)\\n\\tat kafka.admin.TopicCommand$.main(TopicCommand.scala:54)\\n\\tat
kafka.admin.TopicCommand.main(TopicCommand.scala)\\nCaused by: java.lang.RuntimeException:
File /usr/hdp/current/kafka-broker/config/kafka_jaas.conf cannot be read.\\n\\tat kafka.utils.ZkUtils$.<init>(ZkUtils.scala:65)\\n\\tat
kafka.utils.ZkUtils$.<clinit>(ZkUtils.scala)\\n\\t... 4 more\
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message