# ERROR instance/beat.go:1027 Exiting: 1 error: error loading config file: invalid config: yaml: line 85: did not find expected key Exiting: 1 error: error loading config file: invalid config: yaml: line 85: did not find expected key
**URL:** https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171
**Category:** Beats
**Tags:** filebeat
**Created:** [June 4, 2023, 7:39pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171 "2023-06-04T19:39:46Z")
**Posts on this page:** 9
**Page:** 2
### Author:  [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [June 11, 2023, 7:27am UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/21 "2023-06-11T07:27:09Z")
So, at the end, did logs send and arrived to ES?
---
### Author:  [@yash2](https://discuss.elastic.co/u/yash2)
#### Post date: [June 12, 2023, 3:59am UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/22 "2023-06-12T03:59:00Z")
No it did not sir.
---
### Author:  [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [June 19, 2023, 1:25pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/23 "2023-06-19T13:25:55Z")
Completely miss this topic. Sorry.
Do next:
1. Stop your Filebeat service if is running: `systemctl status filebeat`
2. All Filebeat processes should be stopped, use `ps aux` to check
3. Download [https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.17.10-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/beats/filebeat/filebeat-7.17.10-linux-x86_64.tar.gz) or the latest, and extact somewhere, home or opt directory
4. Copy [Stephen config] + add logger, or just copy this as filebeat.yml (rename old) in the directory where is filebeat extracted, and pay attention on spaces at the begging of line
```auto
filebeat.inputs:
- type: filestream
id: my-filestream-id
enabled: true
paths:
- /var/log/*.log
filebeat.config.modules:
path: ${path.config}/modules.d/*.yml
reload.enabled: false
setup.template.settings:
index.number_of_shards: 1
setup.kibana:
host: "localhost:5601"
#output.elasticsearch:
# hosts: ["localhost:9200"]
output.console:
pretty: true
logging.level: debug
logging.to_files: true
logging.files:
path: ./logs
name: filebeat.log
keepfiles: 10
permissions: 0644
```
1. Test config filebeat.yml in the extracted directory: `./filebeat.exe test config`
2. Run it: `./filebeat.exe -e`
3. You should see what's happening on the screen. You can delete the data/registry/filebeat/log.json file which keeps tracking and run it again without -e (Log to stderr and disable syslog/file output) to see only result
4. If everything is working, change output in filebeat.yml to elasticsearch.
---
### Author:  [@yash2](https://discuss.elastic.co/u/yash2)
#### Post date: [June 19, 2023, 2:25pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/24 "2023-06-19T14:25:33Z")
Hey, I have already tried all of this, filebeat, the configuration test, specifically, ./filebeat.exe -e, went through successfully, but filebeat is never outputting any logs to the dashboard, and instead been using logstash to send the logs to Elasticsearch, still, nothing works on that end, while enabling the Elasticsearch module from filebeat.
---
### Author:  [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [June 19, 2023, 2:29pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/25 "2023-06-19T14:29:54Z")
To see data in the dashboard, you have to import Kibana dashboard (filebeat setup -e) and configure module i.e. path to logs, port,...
Again it depend which FB module are you using and is that device/log/stream supported.
---
### Author:  [@yash2](https://discuss.elastic.co/u/yash2)
#### Post date: [June 19, 2023, 4:37pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/26 "2023-06-19T16:37:18Z")
I have done all of that
---
### Author:  [@yash2](https://discuss.elastic.co/u/yash2)
#### Post date: [June 26, 2023, 7:54pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/27 "2023-06-26T19:54:56Z")
We can close this.
---
### Author:  [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [June 26, 2023, 8:02pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/28 "2023-06-26T20:02:08Z")
@yash2 Did you find the solution?
If so can you please post so that anyone else that has the same issues might benefit?
Even if it is minor it help, or help us that answer so we might ask better questions next time.
Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 24, 2023, 10:02pm UTC](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171/29 "2023-07-24T22:02:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
[Previous page](https://discuss.elastic.co/t/error-instance-beat-go-1027-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key-exiting-1-error-error-loading-config-file-invalid-config-yaml-line-85-did-not-find-expected-key/335171.md?page=1)