Greetings, nohup does the trick, as Mr. Bridge has shared. If you seem to want to run these and still have some "interactivity" with the services, consider using "screen" or "tmux" as these will enable you to run these programs in foreground, have added windows you can use to access shell, tail logs, and so on, and enable you to disconnect from the session, but still have these sessions available for re-attachment.
In addition, I using "runit" for service supervision may enable you to keep daemons running, but if your services are dying you may need to introspect more deeply on the root cause versus working around it by restarting them. *Terry Bates* *Email: *terryjba...@gmail.com *Phone: (*412) 215-0881 *Skype*: terryjbates *GitHub*: https://github.com/terryjbates *Linkedin*: http://www.linkedin.com/in/terryjbates/ On Tue, Jun 16, 2015 at 3:30 PM, Mike Bridge <m...@bridgecanada.com> wrote: > Have you tried using "nohup" > > nohup bin/zookeeper-server-start.sh config/zookeeper.properties & > nohup bin/kafka-server-start.sh config/server.properties & > > > On Tue, Jun 16, 2015 at 3:21 PM, Su She <suhsheka...@gmail.com> wrote: > > > Hello Everyone, > > > > I'm wondering how to keep Zookeeper and Kafka Server up even when my > > SSH (using putty) becomes inactive. I've tried running it in the > > background (using &), but it seems like it stops sometimes after a > > couple hours or so and I'll have to restart zookeeper and/or the kafka > > server. > > > > The only remediation i've found is to export TMOUT=[big number], but > > there must be another solution. > > > > Thank you! > > > > Best, > > > > Su > > >
