Filebeat service failing after upgrading to 7.3.0

Elastic Stack Beats
1

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.
2

Never mind, it worked!!!

filebeat.prospectors has been removed from newer version.

3

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