# Filebeat not starting at startup

**URL:** https://discuss.elastic.co/t/filebeat-not-starting-at-startup/124679
**Category:** Beats
**Tags:** filebeat
**Created:** [March 20, 2018, 4:23am UTC](https://discuss.elastic.co/t/filebeat-not-starting-at-startup/124679 "2018-03-20T04:23:32Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![lfk](https://avatars.discourse-cdn.com/v4/letter/l/22d042/32.png) [@lfk](https://discuss.elastic.co/u/lfk)
#### Post date: [March 20, 2018, 4:23am UTC](https://discuss.elastic.co/t/filebeat-not-starting-at-startup/124679/1 "2018-03-20T04:23:32Z")

</div>

I've installed Filebeat on an Ubuntu 16.04 server (AWS EC2) according to the instructions [here](https://www.elastic.co/guide/en/beats/filebeat/current/setup-repositories.html), including running

```
sudo update-rc.d filebeat defaults 95 10

```

However, I still have to run

```
sudo service filebeat start

```

to start filebeat. Is that behaviour expected or am I doing something wrong?

---

<div class="post-metadata">

### Author: ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [March 20, 2018, 8:58am UTC](https://discuss.elastic.co/t/filebeat-not-starting-at-startup/124679/2 "2018-03-20T08:58:05Z")

</div>

On Ubuntu 16.04, which is using systemd, you need to do: `systemctl enable filebeat` instead of the `update-rc.d` command.

---

<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 17, 2018, 8:58am UTC](https://discuss.elastic.co/t/filebeat-not-starting-at-startup/124679/3 "2018-04-17T08:58:08Z")

</div>

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