You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Vipin Rathor (JIRA)" <ji...@apache.org> on 2018/06/20 08:38:00 UTC
[jira] [Created] (AMBARI-24151) Kafka Broker doesn't produce
stdout/stderr (e.g. Kerberos debug) when started via Ambari
Vipin Rathor created AMBARI-24151:
-------------------------------------
Summary: Kafka Broker doesn't produce stdout/stderr (e.g. Kerberos debug) when started via Ambari
Key: AMBARI-24151
URL: https://issues.apache.org/jira/browse/AMBARI-24151
Project: Ambari
Issue Type: Bug
Components: ambari-agent, ambari-server
Affects Versions: 2.6.2
Reporter: Vipin Rathor
When Kerberos debugging is enabled in Kafka Broker via "-Dsun.security.krb5.debug=true" JVM argument and when Ambari is used to start Kafka Broker, the service doesn't print any Kerberos messages in any log file.
Whereas with the same configuration, when Kafka Broker is started via command line (command below), then Kafka Broker correctly creates a 'kafkaServer.out' file and writes Kerberos debug messages to it.
Steps to recreate:
# Add Kerberos debug for Kafka (Ambari > Kafka > Advanced Kafka-env)
{code:java}
export KAFKA_KERBEROS_PARAMS="$KAFKA_KERBEROS_PARAMS -Dsun.security.krb5.debug=true"{code}
# Save & restart Kafka Broker via Ambari.
# There won't be any file in /var/log/kafka location
# Stop Kafka from Ambari and start manually via command line:
{code:java}
su - kafka
/usr/hdp/current/kafka-broker/bin/kafka-server-start.sh -daemon /etc/kafka/conf/server.properties{code}
# This time, you'll find a debug log in '/var/log/kafka/kafkaServer.out'.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)