# Filebeat service failing after upgrading to 7.3.0

**URL:** <https://discuss.elastic.co/t/filebeat-service-failing-after-upgrading-to-7-3-0/195778>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [August 19, 2019, 4:22pm UTC](https://discuss.elastic.co/t/filebeat-service-failing-after-upgrading-to-7-3-0/195778 "2019-08-19T16:22:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijayakrishna.rg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakrishna.rg/32/36798_2.png) [@vijayakrishna.rg](https://discuss.elastic.co/u/vijayakrishna.rg)\
**Post date:** [August 19, 2019, 4:22pm UTC](https://discuss.elastic.co/t/filebeat-service-failing-after-upgrading-to-7-3-0/195778/1 "2019-08-19T16:22:02Z")

</div>

Elasticsearch version: 7.3.0  
Filebeat version: 7.3.0  
Logstash version: 7.3.0

Filebeat configuration:

```
filebeat.prospectors:
- input_type: log
  paths:
    - /var/log/nginx/*.log
  exclude_files: ['\.gz$']

output.logstash:
  hosts: ["10.10.10.10:5400"]

```

Filebeat status:

```
systemctl status filebeat -l
● filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch.
   Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Mon 2019-08-19 16:09:25 UTC; 11min ago
     Docs: https://www.elastic.co/products/beats/filebeat
  Process: 28996 ExecStart=/usr/share/filebeat/bin/filebeat $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=1/FAILURE)
 Main PID: 28996 (code=exited, status=1/FAILURE)

Aug 19 16:09:25 nginxnprod systemd[1]: Unit filebeat.service entered failed state.
Aug 19 16:09:25 nginxnprod systemd[1]: filebeat.service failed.
Aug 19 16:09:25 nginxnprod systemd[1]: filebeat.service holdoff time over, scheduling restart.
Aug 19 16:09:25 nginxnprod systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticsearch..
Aug 19 16:09:25 nginxnprod systemd[1]: start request repeated too quickly for filebeat.service
Aug 19 16:09:25 nginxnprod systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..
Aug 19 16:09:25 nginxnprod systemd[1]: Unit filebeat.service entered failed state.
Aug 19 16:09:25 nginxnprod systemd[1]: filebeat.service failed.
```

---

<div class="post-metadata">

**Author:** ![vijayakrishna.rg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakrishna.rg/32/36798_2.png) [@vijayakrishna.rg](https://discuss.elastic.co/u/vijayakrishna.rg)\
**Post date:** [August 19, 2019, 4:55pm UTC](https://discuss.elastic.co/t/filebeat-service-failing-after-upgrading-to-7-3-0/195778/2 "2019-08-19T16:55:17Z")

</div>

Never mind, it worked!!!

filebeat.prospectors has been removed from newer version.

---

<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:** [September 16, 2019, 4:55pm UTC](https://discuss.elastic.co/t/filebeat-service-failing-after-upgrading-to-7-3-0/195778/3 "2019-09-16T16:55:20Z")

</div>

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