[
https://issues.apache.org/jira/browse/KAFKA-7154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551062#comment-16551062
]
Ray Chiang commented on KAFKA-7154:
-----------------------------------
A lot could depend on how you intend to make Kafka available. The standard way
on CentOS to handle startup scripts is documented in this file:
{code}
/usr/share/doc/initscripts-<version>/sysvinitfiles
{code}
Beyond that, you can use the standard practice of directing stdout/stderr to
/dev/null for your shell. This would look something like:
{code}
nohup bin/kafka-server-start.sh config/server.properties > /dev/null 2>&1
{code}
In the future, I suggest asking these questions in the [email protected]
mailing list rather than creating a JIRA.
> Apache kafka getting shut down everytime it is started
> ------------------------------------------------------
>
> Key: KAFKA-7154
> URL: https://issues.apache.org/jira/browse/KAFKA-7154
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Pushkar Kumar
> Priority: Major
> Attachments: server.txt
>
>
> Hi Team,
> We performed below steps to setup Apache Kafka on a Linux CentOS box:-
> 1.Setup jdk-8u172-linux-x64
> 2.Setup zookeeper-3.5.4-beta and its running fine.
> 3.Setup kafka_2.12-1.1.0(Binary file download from Apache Kafka platform)
> Whenever I am trying to start the Kafka Service, it shows below behavior:-
> INFO Terminating process due to signal SIGHUP (kafka.Kafka$)
> INFO [KafkaServer id=0] shutting down (kafka.server.KafkaServer)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
