Failed to connect to backoff, data path already locked by another beat

Elastic Stack Elasticsearch
1

Elasticsearch and filebeats, auditbeats, packetbeats, metricbeats and Logstash are running on the following:

Ubuntu 18.04
2 core , 64 bit, 4GB RAM

All the aformentioned beats and Logstash have been systemctl stopped

(A) Then executing packetbeats -e produces this error

[publisher_pipeline_outline] pipeline/output.go:155 Failed to connect to backoff(elasticsearch(http://XX.X.X.XX:5044)): Get http://XX.X.X.XX:5044: dial tcp XX.X.X.XX connect: connection refused

(B) systemctl restarting packetbeat and executing the command packetbeat -e produces the following error:

INFO instance/beat.go: 404 packetbeat stopped.
ERROR instance/beat.go:958 Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).

Why is elasticsearch not being connected to and when only packetbeat is running the error is the data path is locked by another beat.

Thanks in advance!

2

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