# Help with LS stoping 30 seconds after start **URL:** \ **Category:** Logstash\ **Created:** [July 27, 2016, 12:17pm UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513 "2016-07-27T12:17:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![dustin.liddick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dustin.liddick/32/7390_2.png) [@dustin.liddick](https://discuss.elastic.co/u/dustin.liddick)\ **Post date:** [July 27, 2016, 12:17pm UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/1 "2016-07-27T12:17:26Z")
Hello: My LS instance starts up just fine, and ~30-120 seconds into the initialization, logstash then stops. I will paste the error below. The settings that I have for my LS indexing node is VM - Red Hat 6.5 x64 2xvCPU 12GB RAM Both resources can be adjusted if needed. Is it an issue with my settings for logstash? what should they be? I have 2 workers defined by '-w 2' in '/etc/sysconfig/logstash'. I have 1 input from redis defined with 8 threads and I have 1 output to ES defined with 4 workers, again, can be adjusted. I also have the 'LS\_HEAP\_SIZE' set to "1024m" Am I right with these settings? Thank to any and all insight, here is the error after the LS crash...its the same every time: [http://pastebin.com/zJWWWtXw](http://pastebin.com/zJWWWtXw) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 28, 2016, 2:59am UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/2 "2016-07-28T02:59:27Z")
What does your config look like? ---
**Author:** ![dustin.liddick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dustin.liddick/32/7390_2.png) [@dustin.liddick](https://discuss.elastic.co/u/dustin.liddick)\ **Post date:** [July 28, 2016, 3:28am UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/3 "2016-07-28T03:28:41Z")
what config are you speaking of. Ones that reside in '/etc/logstash/conf.d' or the one in '/etc/sysconfig/logstash' or '/etc/init.d/logstash'? I can paste bin anyone you want. Thank you for the reply ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [July 28, 2016, 10:44pm UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/4 "2016-07-28T22:44:54Z")
The the plugin config. ---
**Author:** ![dustin.liddick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dustin.liddick/32/7390_2.png) [@dustin.liddick](https://discuss.elastic.co/u/dustin.liddick)\ **Post date:** [July 29, 2016, 12:08am UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/5 "2016-07-29T00:08:42Z")
thank for the response. after literally staring at the error for about an hour I as able to make it out that the issue lied with the Ruby multi-line filter. since I had workers defined in my configuration, it was in contention for resources thus choking out. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:46am UTC](https://discuss.elastic.co/t/help-with-ls-stoping-30-seconds-after-start/56513/6 "2017-07-06T04:46:03Z")
Closed on July 6, 2017, 4:46am UTC