# Pipeline/output.go:154 Failed to connect to backoff
**URL:** https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767
**Category:** Beats
**Tags:** filebeat
**Created:** [December 2, 2021, 12:50pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767 "2021-12-02T12:50:07Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 2, 2021, 12:50pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/1 "2021-12-02T12:50:07Z")
Hello,
I'm getting this error, does anyone knows how to solve this?
```auto
ERROR [publisher_pipeline_output] pipeline/output.go:154 Failed to connect to backoff(elasticsearch(https://xxxxxx:9200)): Connection marked as failed because the onConnect callback failed: resource 'filebeat-7.14.0' exists, but it is not an alias
```
---
### Author:  [@AquaX](https://discuss.elastic.co/u/AquaX)
#### Post date: [December 2, 2021, 2:11pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/2 "2021-12-02T14:11:06Z")
> [@abhi.logs](#):
>
> `Connection marked as failed because the onConnect callback failed: resource 'filebeat-7.14.0' exists, but it is not an alias`
I think this means that the index you are trying to write to exists but is not an alias as you likely defined some sort of ILM rules to be followed.
If you can paste your beats output config then that will help to figure out the problem.
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 2, 2021, 2:14pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/3 "2021-12-02T14:14:09Z")
Thanks for reply
```auto
# ================================== Outputs ===================================
# Configure what output to use when sending the data collected by the beat.
# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
# Array of hosts to connect to.
hosts: ["xxxxxx:9200"]
indices:
- index: "logindex-%{[fields.server]}-%{[fields.log_type]}-%{+yyyy.MM.dd}"
when.contains:
fields.log_group: "paltform"
# Protocol - either `http` (default) or `https`.
protocol: "https"
# Authentication credentials - either API key or username/password.
username: "username"
password: "password"
```
---
### Author:  [@AquaX](https://discuss.elastic.co/u/AquaX)
#### Post date: [December 2, 2021, 2:19pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/4 "2021-12-02T14:19:37Z")
Have you recently upgraded your agents or Elasticsearch?
Try setting this in filebeat:
```auto
setup.template.settings:
setup.template.overwrite: true
setup.template.enabled: true
```
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 2, 2021, 2:29pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/5 "2021-12-02T14:29:31Z")
> [@AquaX](#):
>
> `setup.template.enabled: true`
No, we didn't upgrade anything, We shut down ES for a month. When we started ES it stopped working and getting this error @AquaX template setting not working
---
### Author:  [@AquaX](https://discuss.elastic.co/u/AquaX)
#### Post date: [December 2, 2021, 2:36pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/6 "2021-12-02T14:36:56Z")
Put
```auto
setup.template.enabled: true
setup.template.overwrite: true
```
before `setup.template.settings:`
ideally `above setup.template.name`
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 2, 2021, 2:43pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/7 "2021-12-02T14:43:33Z")
Getting the same error for both conditions.
---
### Author:  [@AquaX](https://discuss.elastic.co/u/AquaX)
#### Post date: [December 2, 2021, 3:00pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/8 "2021-12-02T15:00:54Z")
Hmm... strange. I'm honestly not sure what the problem could be.
Does your template on Elasticsearch include an alias?
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 2, 2021, 3:08pm UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/9 "2021-12-02T15:08:45Z")
How to check alias?
I hope this is correct cmd.
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 3, 2021, 11:53am UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/10 "2021-12-03T11:53:37Z")
While checking the ES logs, I received this error.
```auto
> [ERROR][o.e.x.i.IndexLifecycleRunner] [ip] current step [{"phase":"hot","action":"rollover","name":"check-rollover-ready"}] for index [logindex-qa-xx-log-2021.10.03] with policy [10-day_delete_policy] is not recognized
```
---
### Author:  [@abhi.logs](https://discuss.elastic.co/u/abhi.logs)
#### Post date: [December 7, 2021, 5:03am UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/11 "2021-12-07T05:03:31Z")
Deleted the filebeat-7.14.0 index.
This one help me to resolved this issue
------\>\>
> [@Exiting: resource 'metricbeat-7.4.2' exists, but it is not an alias](https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685/3):
>
> I managed to find a way around this in case anyone else is interested. Here's what I had to do: Stop new index auto-creation Added action.auto\_create\_index: false to the user override settings for the node Deleted the metricbeat-7.4.0 index (I can afford to lose this data) Created a new metricbeat-7.4.0-2019-11-06 index and assign it the alias PUT /metricbeat-7.4.0-2019-11-06 { "actions" : [ { "add" : { "index" : "metricbeat-7.4.0-2019.11.06-000001", "alias" : "metric…
\<\<------
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 4, 2022, 7:03am UTC](https://discuss.elastic.co/t/pipeline-output-go-154-failed-to-connect-to-backoff/290767/12 "2022-01-04T07:03:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.