# Service restart/stop won't work after upgrade

**URL:** https://discuss.elastic.co/t/service-restart-stop-wont-work-after-upgrade/90446
**Category:** Beats
**Tags:** filebeat
**Created:** [June 22, 2017, 11:49am UTC](https://discuss.elastic.co/t/service-restart-stop-wont-work-after-upgrade/90446 "2017-06-22T11:49:10Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![jknaack](https://avatars.discourse-cdn.com/v4/letter/j/cab0a1/32.png) [@jknaack](https://discuss.elastic.co/u/jknaack)
#### Post date: [June 22, 2017, 11:49am UTC](https://discuss.elastic.co/t/service-restart-stop-wont-work-after-upgrade/90446/1 "2017-06-22T11:49:10Z")

</div>

After installing filebeat updates on Ubuntu 14.04 servers, "service filebeat stop" isn't working immediately after upgrading. The processes filebeat-god and filebeat stay running although pid-file is correct.

A service restart end up in duplicate processes.

This at least happened when updating from 5.4.0 to 5.4.1 and 5.4.2.

It looks like the god-wrapper can't find the sub-processes being started with a prior (pre-upgrade) filebeat version and therefore won't stop them.

---

<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: [July 20, 2017, 11:49am UTC](https://discuss.elastic.co/t/service-restart-stop-wont-work-after-upgrade/90446/2 "2017-07-20T11:49:30Z")

</div>

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