# Filebeat broken
**URL:** https://discuss.elastic.co/t/filebeat-broken/148280
**Category:** Beats
**Tags:** filebeat
**Created:** [September 12, 2018, 8:44am UTC](https://discuss.elastic.co/t/filebeat-broken/148280 "2018-09-12T08:44:42Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mouli\_v](https://discuss.elastic.co/u/mouli_v)
#### Post date: [September 12, 2018, 8:44am UTC](https://discuss.elastic.co/t/filebeat-broken/148280/1 "2018-09-12T08:44:42Z")
Our elastic search instance is with 6.2.4 version
```auto
"version" : {
"number" : "6.2.4",
"build_hash" : "ccec39f",
"build_date" : "2018-04-12T20:37:28.497551Z",
"build_snapshot" : false,
"lucene_version" : "7.2.1",
"minimum_wire_compatibility_version" : "5.6.0",
"minimum_index_compatibility_version" : "5.0.0"
}
```
We have other instances, which loads the filebeat data to the elastic search instances.
Here is my question: We manage few instances in our environment few are installed with filebeat 6.2.4 and few are with 6.3.2.
Filebeat with 6.3.2 is doing as expected, but 6.2.4 is behaving weirdly; It is failing frequently. Is there any issue, We should not use different versions on different nodes?, which reports to one elasticsearch node?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 10, 2018, 8:44am UTC](https://discuss.elastic.co/t/filebeat-broken/148280/2 "2018-10-10T08:44:49Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.