# Managing Logstash - restating on fail

**URL:** <https://discuss.elastic.co/t/managing-logstash-restating-on-fail/80471>\
**Category:** Logstash\
**Created:** [March 29, 2017, 11:39am UTC](https://discuss.elastic.co/t/managing-logstash-restating-on-fail/80471 "2017-03-29T11:39:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsps](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsps/32/5411_2.png) [@jsps](https://discuss.elastic.co/u/jsps)\
**Post date:** [March 29, 2017, 11:39am UTC](https://discuss.elastic.co/t/managing-logstash-restating-on-fail/80471/1 "2017-03-29T11:39:37Z")

</div>

Hi All, first time we are starting to use logstash.  
What is the best practice for restarting the process when it dies from lack of memory or network issue for example ? We are consuming from databases using the JDBC plugin and the process occasionally dies, for instance if the network to the database is temporarily unavailable. What I'd like to happen is the process to run much like a cron job ( I have the schedule set in JDBC plugin ) thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 26, 2017, 11:39am UTC](https://discuss.elastic.co/t/managing-logstash-restating-on-fail/80471/2 "2017-04-26T11:39:38Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.