[AMBARI-24151] Kafka Broker doesn't produce stdout/stderr (e.g. Kerberos debug) when started via Ambari

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6.2
• Component/s: ambari-agent, ambari-server
• Assignee: Unassigned
• Reporter: Vipin Rathor
• Created: 20/Jun/18 08:37
• Updated: 20/Jun/18 08:37

Description

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:

1. Add Kerberos debug for Kafka (Ambari > Kafka > Advanced Kafka-env)

export KAFKA_KERBEROS_PARAMS="$KAFKA_KERBEROS_PARAMS -Dsun.security.krb5.debug=true"

1. Save & restart Kafka Broker via Ambari.
2. There won't be any file in /var/log/kafka location
3. Stop Kafka from Ambari and start manually via command line:

su - kafka
/usr/hdp/current/kafka-broker/bin/kafka-server-start.sh -daemon /etc/kafka/conf/server.properties

1. This time, you'll find a debug log in '/var/log/kafka/kafkaServer.out'.