Skip to content

No alive nodes found in your cluster #805

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

Closed
FredrikLodon opened this issue Oct 5, 2018 · 6 comments
Closed

No alive nodes found in your cluster #805

FredrikLodon opened this issue Oct 5, 2018 · 6 comments

Comments

@FredrikLodon
Copy link

FredrikLodon commented Oct 5, 2018

Summary of problem or feature request

I have a strange scenario. I have two test environments which my configuration works flawless. But in my live environment I get the "No alive nodes found in your cluster" message.

So this is my two test environments which Elastic Cloud works great.

  1. VB-Ubuntu, setup:
  • Ubuntu 16.04
  • PHP 7.1.22-1+ubuntu16.04.1+deb.sury.org+1
  • PHP7.1-curl
  • Elasticsearch-php v6.0.1
    Note: Above works flawless - return desired result - both from the code itself and by "curl https://username:pass@myadress" from terminal.
  1. MAMP
  • MAMP under OSX
  • php7.2.1
  • curl7.52.1
  • Elasticsearch-php v6.0.1
    Note: Above works flawless - return desired result - both from the code itself and by "curl https://username:pass@myadress" from terminal.

This is the live-host, which the problem occurs
3. The-trouble-host

  • Debian 8.11
  • PHP 7.1.22-1+020181001133629.6+jessie1.gbp113f3b
  • PHP7.1-curl
  • Elasticsearch-php v6.0.1
    Note: This is my prod-server. Which returns the error below, Im using row breaks to get it a little bit more clear to look at:

[Fri Oct 05 16:39:28.787535 2018]
[proxy_fcgi:error]
[pid 17303:tid 139723339167488]
[client 85.225.129.215:50158]
AH01071:
Got error 'PHP message: PHP Fatal error:
Uncaught Elasticsearch\Common\Exceptions\NoNodesAvailableException:
No alive nodes found in your cluster in /srv/www.xxxx.xxxx/htdocs/wp-content/plugins/xxxxxxxx/vendor/elasticsearch/elasticsearch/src/Elasticsearch/ConnectionPool/StaticNoPingConnectionPool.php:51
\nStack trace:\n#0 /srv/www.xxxxx.xxx/htdocs/wp-content/plugins/xxxxx/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Transport.php(76):
Elasticsearch\ConnectionPool\StaticNoPingConnectionPool->nextConnection()\n#1 /srv/www.xxxx.xxx/htdocs/wp-content/plugins/xxxxx/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Transport.php(94):
Elasticsearch\Transport->getConnection()\n#2 /srv/www.xxxxx.xxxx/htdocs/wp-content/plugins/xxxxx/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php(246):
Elasticsearch\Transport->performRequest('GET', '/elasticxxxs...', Array, '{"query":{"matc...', Array)\n#3 /srv...\n', referer: https://www.xxxx.xxxx/search/?find=razor

How come I get this problem on this setup?

@FredrikLodon
Copy link
Author

FredrikLodon commented Oct 8, 2018

Im still troubleshooting this and have figured that if this error can come up if some sort of port is blocking the connection? Although this is a long-shot, I cant figure out why Im having this problem on the "3. The-trouble-host".

@nclavaud
Copy link

Did you try the curl command on the faulty host ?

@gamelife1314
Copy link

Did you set proxy environment (http_proxy, https_proxy) ?

@benanderton
Copy link

I came across a similar issue regarding the hostname, please see #509 (comment)

@PutziSan
Copy link

In my case it was a problem with SSL certificates (on windows). This SO response describes the solution:

  1. download an official cacert.pem from https://curl.haxx.se/docs/caextract.html and save it where you want
  2. add curl.cainfo = "C:\your\path\cacert.pem" to your php.ini

@ezimuel
Copy link
Contributor

ezimuel commented Aug 30, 2019

@FredrikLodon I'm closing this issue, I'll reopen if still relevant.

@ezimuel ezimuel closed this as completed Aug 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants