Generator-jhipster: detail : "None of the configured nodes are available: [{#transport#-1}{localhost}{127.0.0.1:9300}]"

Created on 10 Mar 2018 · 2Comments · Source: jhipster/generator-jhipster

Deployed my gateway on Heroku
Login succeed .
Trying to add some tag ..500 error in browser
full browser response
{"type":"http://www.jhipster.tech/problem/problem-with-message","title":"Internal Server Error","status":500,"detail":"None of the configured nodes are available: [{#transport#-1}{localhost}{127.0.0.1:9300}]","path":"/api/tags","message":"error.http.500"}
heroku logs gives me

2018-03-10T17:10:12.373678+00:00 heroku[web.1]: 2018-03-10T17:10:12.373865+00:00 heroku[web.1]: 2018-03-10T17:10:17.386406+00:00 app[web.1]: 2018-03-10T17:10:17.386419+00:00 app[web.1]:
Error R14 (Memory quota exceeded)
2018-03-10 17:10:17.386 WARN 4 --- [nfoReplicator-0] o.s.b.a.h.ElasticsearchHealthIndicator : Health check failed
/> org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{localhost}{127.0.0.1:9300}]
at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:326)
at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:223)
at org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:295)
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:359)
at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:348)
at org.elasticsearch.client.support.AbstractClient$ClusterAdmin.execute(AbstractClient.java:848)
at org.elasticsearch.client.support.AbstractClient$ClusterAdmin.health(AbstractClient.java:868)
at org.springframework.boot.actuate.health.ElasticsearchHealthIndicator.doHealthCheck(ElasticsearchHealthIndicator.java:50)
at org.springframework.boot.actuate.health.AbstractHealthIndicator.health(AbstractHealthIndicator.java:43)
at org.springframework.boot.actuate.health.CompositeHealthIndicator.health(CompositeHealthIndicator.java:68)
at org.springframework.cloud.netflix.eureka.EurekaHealthCheckHandler.getHealthStatus(EurekaHealthCheckHandler.java:103)
at org.springframework.cloud.netflix.eureka.EurekaHealthCheckHandler.getStatus(EurekaHealthCheckHandler.java:99)
at com.netflix.discovery.DiscoveryClient.refreshInstanceInfo(DiscoveryClient.java:1362)
at com.netflix.discovery.InstanceInfoReplicator.run(InstanceInfoReplicator.java:100)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
/> 2018-03-10 17:10:24.721 WARN 4 --- [ XNIO-2 task-15] o.s.c.n.zuul.web.ZuulHandlerMapping : No routes found from RouteLocator
2018-03-10 17:10:24.729 ERROR 4 --- [ XNIO-2 task-15] o.z.p.spring.web.advice.AdviceTrait : Internal Server Error
/> org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{localhost}{127.0.0.1:9300}]

Source

nutrimax1987

Most helpful comment

When deploying in production, you need to run your own instance of Elasticsearch somewhere. http://www.jhipster.tech/using-elasticsearch/

Starting in v5, the Heroku subgenerator will create a free elasticsearch addon for your app. https://github.com/jhipster/generator-jhipster/pull/7131

This ticket has been closed as the guidelines are not followed.

Tickets must follow our Guidelines, as mentioned in:

our Readme file on the front page of the project,
the "create a new ticket" page and
our Help page

We have also created a template on the "create a new ticket" page to help you follow those guidelines.

If this is indeed a JHipster bug, please open a new issue with proper details or update this issue with all details and request to reopen.
Issues opened without proper details will be closed without explanation.

If you have a question please use Stack Overflow, and tag the question with jhipster. This helps the project to keep the issue tracker clean. Also, Stack Overflow will give your question a larger audience:

This will increase your chances to get an answer
Answers will be of higher quality, as there is a voting system
This will also help other users who might have the same issue, as questions are tagged and easily searchable

ruddell on 10 Mar 2018

🎉2 👍2 😄1

All 2 comments

When deploying in production, you need to run your own instance of Elasticsearch somewhere. http://www.jhipster.tech/using-elasticsearch/

Starting in v5, the Heroku subgenerator will create a free elasticsearch addon for your app. https://github.com/jhipster/generator-jhipster/pull/7131

This ticket has been closed as the guidelines are not followed.

Tickets must follow our Guidelines, as mentioned in:

our Readme file on the front page of the project,
the "create a new ticket" page and
our Help page

We have also created a template on the "create a new ticket" page to help you follow those guidelines.

This will increase your chances to get an answer
Answers will be of higher quality, as there is a voting system
This will also help other users who might have the same issue, as questions are tagged and easily searchable

ruddell on 10 Mar 2018

🎉2 👍2 😄1

so quick response thank you very much , fantastic !

nutrimax1987 on 10 Mar 2018

Was this page helpful?

0 / 5 - 0 ratings