Filebeat won't start the service. Data path already locked by another beat

Elastic Stack Beats
1

Hello, This is my first time to setup logging stack.

My problem is the Filebeat service wont start.

 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 2021-10-06 07:41:10 UTC; 3s ago
     Docs: https://www.elastic.co/beats/filebeat
  Process: 19354 ExecStart=/usr/share/filebeat/bin/filebeat --environment systemd $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BEAT_PATH_OPTS (code=exited, status=1/FAILURE
 Main PID: 19354 (code=exited, status=1/FAILURE)

Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Failed with result 'exit-code'.
Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Service RestartSec=100ms expired, scheduling restart.
Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Scheduled restart job, restart counter is at 5.
Oct 06 07:41:10 delete-soon systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticsearch..
Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Start request repeated too quickly.
Oct 06 07:41:10 delete-soon systemd[1]: filebeat.service: Failed with result 'exit-code'.
Oct 06 07:41:10 delete-soon systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to Elasticsearch..

Filebeat log produces

Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).

I'm looking around for answer but seems didn't worked. What I have to do to solve this?

2

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