Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch

× filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch.
Loaded: loaded (/lib/systemd/system/filebeat.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2022-11-02 11:02:52 -05; 13min ago
Docs: Filebeat: Lightweight Log Analysis & Elasticsearch | Elastic
Process: 4934 ExecStart=/usr/share/filebeat/bin/filebeat --environment systemd $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=2)
Main PID: 4934 (code=exited, status=2)
CPU: 45ms

nov 02 11:02:52 wazuhserver01 filebeat[4934]: rip 0x7f6c15120a7c
nov 02 11:02:52 wazuhserver01 filebeat[4934]: rflags 0x246
nov 02 11:02:52 wazuhserver01 filebeat[4934]: cs 0x33
nov 02 11:02:52 wazuhserver01 filebeat[4934]: fs 0x0
nov 02 11:02:52 wazuhserver01 filebeat[4934]: gs 0x0
nov 02 11:02:52 wazuhserver01 systemd[1]: filebeat.service: Scheduled restart job, restart counter is at 5.
nov 02 11:02:52 wazuhserver01 systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticsearch..
nov 02 11:02:52 wazuhserver01 systemd[1]: filebeat.service: Start request repeated too quickly.
nov 02 11:02:52 wazuhserver01 systemd[1]: filebeat.service: Failed with result 'exit-code'.
nov 02 11:02:52 wazuhserver01 systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..

Welcome to our community! :smiley:

Please don't just post a log without adding more context, you are unlikely to get much help as your post currently is.

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