Storm and Kafka are always there for no reason session close

Recently engaged in kafak+storm+flume real-time processing, but Kafka and Storm will always be inexplicable to die, view the log is the following content:

2015-07-22t03:15:31.808+0800 b.s.event [INFO] Event Manager interrupted
2015-07-22t03:15:31.808+0800 b.s.event [INFO] Event Manager interrupted
2015-07-22t03:15:31.928+0800 O.a.s.z.zookeeper [INFO] SESSION:0X34E629EB72B00DE closed

2015-07-22t03:15:31.928+0800 o.a.s.z.clientcnxn [INFO] Eventthread shut down

Also do not see what, just beginning thought is zookeeper problem, later Google to a post, said is the implementation process, no use nohup reason.

Because I am a beginner to Linux, I simply find a bit of information to see the introduction of Nohup.

1. The nohup command runs commands specified by the command parameter and any related arg parameters, ignoring all hang-up (SIGHUP) signals . Use the Nohup command to run a program in the background after logging off. To run the Nohup command in the background, add & (the symbol representing "and") to the end of the command.

2, SIGHUP-This signal is issued at the end of the user terminal connection (normal or abnormal), usually at the end of the control process of the terminal , notify the same session of the various jobs, then they are no longer associated with the control terminal

OK, it's not hard to see the problem through these two.

Storm and Kafka are always there for no reason session close