New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TASK [logstash : Load filebeat JSON index template] #73

gitmkc opened this Issue Nov 29, 2018 · 1 comment


None yet
2 participants

gitmkc commented Nov 29, 2018

I am getting below error in logstash.
fatal: [elkserver]: FAILED! => {"attempts": 30, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://localhost:9200/_template/filebeat?pretty"}


This comment has been minimized.


sadsfae commented Dec 7, 2018

Hey @gitmkc I'm not able to reproduce this, the specific Playbook line that runs this is:

It works fine for me:

TASK [logstash : Load filebeat JSON index template] ***********************************************************************************************
ok: [host-01]

Typically this will fail if Elasticsearch isn't up and running yet, this can take some time on slower systems which is why we have 30 attempts. What kind of resources does your ELK host have? I have only seen this when it's not powerful enough (memory, cpu) to instantiate all the Elastic Java processes beforehand.

We try to stagger out dependent service deployment in this playbook to accommodate as well as build in sensible timeouts (which is why you see a lot of non-Kibana stuff happen in the Kibana role).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment