Couldnt start filebeat-Please HELP!

Elastic Stack Beats
1

systemctl status filebeat
â 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 Tue 2019-10-15 16:18:06 IST; 1min 13s ago
Docs: https://www.elastic.co/products/beats/filebeat
Process: 11446 ExecStart=/usr/share/filebeat/bin/filebeat $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=1/FAILURE)
Main PID: 11446 (code=exited, status=1/FAILURE)

Oct 15 16:18:06 localhost.localdomain systemd[1]: Unit filebeat.service entered failed state.
Oct 15 16:18:06 localhost.localdomain systemd[1]: filebeat.service failed.
Oct 15 16:18:06 localhost.localdomain systemd[1]: filebeat.service holdoff time over, scheduling restart.
Oct 15 16:18:06 localhost.localdomain systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticsearch..
Oct 15 16:18:06 localhost.localdomain systemd[1]: start request repeated too quickly for filebeat.service
Oct 15 16:18:06 localhost.localdomain systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..
Oct 15 16:18:06 localhost.localdomain systemd[1]: Unit filebeat.service entered failed state.
Oct 15 16:18:06 localhost.localdomain systemd[1]: filebeat.service failed.

This is the error while i am trying to start the server

2

Hello,

Have you tried a :

filebeat check config

if it didn't display anything, have a look on /var/log/filebeat/filebeat.log or on /var/log/message to get an accurate error message.

3

Resolved.Thank you

4

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