# Systemd kills drip daemon and standby vm

**URL:** <https://discuss.elastic.co/t/systemd-kills-drip-daemon-and-standby-vm/131503>\
**Category:** Logstash\
**Created:** [May 11, 2018, 3:21pm UTC](https://discuss.elastic.co/t/systemd-kills-drip-daemon-and-standby-vm/131503 "2018-05-11T15:21:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robertr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robertr/32/31128_2.png) [@robertr](https://discuss.elastic.co/u/robertr)\
**Post date:** [May 11, 2018, 3:21pm UTC](https://discuss.elastic.co/t/systemd-kills-drip-daemon-and-standby-vm/131503/1 "2018-05-11T15:21:37Z")

</div>

Hi,

Just noticed in my development setup that setting USEDRIP doesn't improve the logstash start time when running logstash as a systemd service.

Looking more closely what I notice is that 3 PIDs are completely different between service restarts. What I see is the PIDs for the active JVM, the drip daemon and the standby JVM.

Even if I just kill the active JVM directly with the kill command, systemd kicks in and kills the other two and starts drip again from scratch!

I think this may be an exotic, and unsupported usecase but I would be curious to see if you have any suggestions as to how I might address this?

Thanks!  
Rob

---

<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:** [June 8, 2018, 3:21pm UTC](https://discuss.elastic.co/t/systemd-kills-drip-daemon-and-standby-vm/131503/2 "2018-06-08T15:21:38Z")

</div>

Closed on June 8, 2018, 3:21pm UTC

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