Unable to revive connection
See original GitHub issueHello,
I keep getting this error, and it never recovers. I’m using Elasticsearch 1.3.2 and elasticsearch-js 2.4.0 (node client)
Elasticsearch WARNING: 2014-09-09T08:09:05Z
Unable to revive connection: https://elasticsearch.****.net/
Elasticsearch WARNING: 2014-09-09T08:09:05Z
No living connections
Here is my configuration
{
apiVersion:'1.3',
sniffOnConnectionFault:true,
maxRetries:5,
keepAlive:true,
connectionClass:'http'
}
Issue Analytics
- State:
- Created 9 years ago
- Reactions:6
- Comments:62 (5 by maintainers)
Top Results From Across the Web
How to resolve 'Unable to revive connection'? - Kibana
I have a Elasticsearch instance in dev mode. My Elasticsearch config is following, cluster.name: "logparser" node.master: true node.data: ...
Read more >How to resolve the error "No living connection" while starting ...
status: working. I am using a docker-compose.yml file to run elasticsearch and kibana on localhost. port 9200 is being used by another service ......
Read more >1781492 – Kibana is not updated after secrets regenerated.
Description of problem: Deploy logging stack via operator, make sure the logging stack works well. Then scale down CLO to 0, delete mater-certs...
Read more >Kibana Unable to revive connection to ElasticSearch-docker
[Solved]-Kibana Unable to revive connection to ElasticSearch-docker. Search. score:2. Accepted answer. The reason why it isn't working is because you are ...
Read more >Elasticsearch has been working for months, but now I have an ...
So it all started when I wanted to restart all ELK service ... ,"pid":18595,"message":"Unable to revive connection: http://localhost:9200/"} ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My problem has been solved.
code
version
I was facing the same problem. For me issue was with setting auth configuration. Following configuration is worked for me.