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

Why? Writing to log to AWS Es as a service. ES..whats the deal? What does that mean? How do I ship to ES using file beat on 16.04?

filebeat:
prospectors:
-
paths:
- "/tmp/upload.log"
- "/var/log/nginx/access.log"
- "/var/log/nginx/error.log"
- "/tmp/upload_server_bottle.log"
fields:
type: log
exclude_lines: ["^.ELB-HealthChecker.$"]
output.elasticsearch:
hosts: ["https://vpc-es.eu-central-1.es.amazonaws.com:443"]
protocol: "https"

12Z INFO Home path: [/usr/share/filebeat] Config path: [/etc/filebeat] Data path: [/var/lib/filebeat] Logs path: [/var/log/filebeat]
2017-11-23T12:43:12Z INFO Beat UUID: 3b490c5b-a242-4431-bf12-390b11ced166
2017-11-23T12:43:12Z INFO Metrics logging every 30s
2017-11-23T12:43:12Z INFO Setup Beat: filebeat; Version: 6.0.0
2017-11-23T12:43:12Z INFO Elasticsearch url: https://vpc-es-zen-aws-prod-fmm-logs-xpugakhxsixbsvbsq4hzqrca3q.eu-central-1.es.amazonaws.com:443
2017-11-23T12:43:12Z INFO Beat name: upload-fmm-10mvvdn
2017-11-23T12:43:12Z INFO filebeat start running.
2017-11-23T12:43:12Z INFO Registry file set to: /var/lib/filebeat/registry
2017-11-23T12:43:12Z INFO Loading registrar data from /var/lib/filebeat/registry
2017-11-23T12:43:12Z INFO Total non-zero values: beat.memstats.gc_next=4473924 beat.memstats.memory_alloc=3334312 beat.memstats.memory_total=3334312 filebeat.harvester.open_files=0 filebeat.harvester.running=0 libbeat.config.module.running=0 libbeat.output.type$
2017-11-23T12:43:12Z INFO Uptime: 7.810057ms
2017-11-23T12:43:12Z INFO filebeat stopped.
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

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

This topic was automatically closed after 21 days. New replies are no longer allowed.