CRIT Exiting: Could not start registrar: Error loading state: Error decoding states: json: cannot unmarshal object into Go value of type []file

pierhugues · November 23, 2017, 8:38pm

Hello,

There is a few things I can see from this output.

2017-11-23T12:43:12Z CRIT Exiting: Could not start registrar: Error loading state: Error decoding states: json: cannot unmarshal object into Go value of type []file.State

I think there is either a problem with the content of the registrar or a permission issue and the error is hidden somehow. Can you add to this issue the output of the following command:

 cat /var/lib/filebeat/registry

Also, I haven't tried it. But I believe AWS Elasticsearch always requires signing request?, but Filebeat currently doesn't support that.

There is a few related discussion here:

Thanks

Topic		Replies	Views
Tried to parse field [log_json] as object Beats filebeat	1	449	February 14, 2019
Filebeat issue with json logs from ES audit Beats filebeat	1	439	March 16, 2022
Filebeat stops sending to es eventually, bulk index 400 Beats filebeat	10	4170	July 14, 2017
Failed to parse JSON response: json: cannot unmarshal string into Go struct field .Version of type struct { Number string }] Beats filebeat	17	5261	February 8, 2019
Sending filebeat data to AWS es Beats filebeat	2	1912	April 17, 2018

CRIT Exiting: Could not start registrar: Error loading state: Error decoding states: json: cannot unmarshal object into Go value of type []file

Related topics