Logstash / kibana can't connect to instance

Hi Team,

I don't remember changing anything at all on my logstash server. As of just
yesterday it was working fine! And I used it to run some queries.

However.. today when I went to my logstash page, I see only thing message
come up:

Please find the details output below:

[root@ip-10-0-0-52 elasticsearch]# grep cors elasticsearch.yml -- I have
added below lines on elasticsearch.yml file

http.cors.allow-origin: "/.*/"

http.cors.enabled: true

[root@ip-10-0-0-52 elasticsearch]# netstat -tulpn | grep -i listen | grep
java

tcp 0 0 ::ffff:127.0.0.1:9300 :::*
LISTEN 973/java

tcp 0 0 ::ffff:127.0.0.1:9200 :::*
LISTEN 973/java

[root@ip-10-0-0-52 elasticsearch]# ps -ef | grep elasticsearch | grep -i -v
-e grep -e screen

496 973 1 3 13:18 ? 00:00:07 /usr/bin/java -Xms256m
-Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
-XX:+DisableExplicitGC -Delasticsearch
-Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
-Des.path.home=/usr/share/elasticsearch -cp
:/usr/share/elasticsearch/lib/elasticsearch-1.3.7.jar:/usr/share/elasticsearch/lib/:/usr/share/elasticsearch/lib/sigar/
-Des.default.path.home=/usr/share/elasticsearch
-Des.default.path.logs=/var/log/elasticsearch
-Des.default.path.data=/var/lib/elasticsearch
-Des.default.path.work=/tmp/elasticsearch
-Des.default.path.conf=/etc/elasticsearch
org.elasticsearch.bootstrap.Elasticsearch

[root@ip-10-0-0-52 elasticsearch]# curl -GET http://localhost:9200

{

"status" : 200,

"name" : "Blaze",

"version" : {

"number" : "1.3.7",

"build_hash" : "3042293e4b219dfb855a4e6c64241c530d1abeb0",

"build_timestamp" : "2014-12-16T13:59:32Z",

"build_snapshot" : false,

"lucene_version" : "4.9"

},

"tagline" : "You Know, for Search"

}

[root@ip-10-0-0-52 elasticsearch]# curl -XGET
'http://127.0.0.1:9200/_cluster/health?pretty=true'

{

"cluster_name" : "elasticsearch",

"status" : "green",

"timed_out" : false,

"number_of_nodes" : 1,

"number_of_data_nodes" : 1,

"active_primary_shards" : 0,

"active_shards" : 0,

"relocating_shards" : 0,

"initializing_shards" : 0,

"unassigned_shards" : 0

}

[root@ip-10-0-0-52 elasticsearch]#

When open Kibana web interface it give me below error
Connection Failed
Possibility #1: Your elasticsearch server is down or unreachable

This can be caused by a network outage, or a failure of the Elasticsearch
process. If you have recently run a query that required a terms facet to be
executed it is possible the process has run out of memory and stopped. Be
sure to check your Elasticsearch logs for any sign of memory pressure.
Possibility #2: You are running Elasticsearch 1.4 or higher

Elasticsearch 1.4 ships with a security setting that prevents Kibana from
connecting. You will need to set the following in your elasticsearch.yml:
http.cors.enabled: true
http.cors.allow-origin to the correct protocol, hostname, and port (if not
80) that your access Kibana from. Note that if you are running Kibana in a
sub-url, you should exclude the sub-url path and only include the protocol,
hostname and port. For example, http://mycompany.com:8080, not
http://mycompany.com:8080/kibana.
Click back, or the home button, when you have resolved the connection issue

Please suggest me what cloud be the problem -- Help me how to fix this issue

Many Thanks,
Madhu

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ee83c273-696f-4c74-9e62-7912117233bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi,

Can anyone please look into this.

Many Thanks,
Madhu

On Wednesday, January 28, 2015 at 5:43:23 AM UTC-8, ma...@venusgeo.com
wrote:

Hi Team,

I don't remember changing anything at all on my logstash server. As of
just yesterday it was working fine! And I used it to run some queries.

However.. today when I went to my logstash page, I see only thing message
come up:

Please find the details output below:

[root@ip-10-0-0-52 elasticsearch]# grep cors elasticsearch.yml -- I have
added below lines on elasticsearch.yml file

http.cors.allow-origin: "/.*/"

http.cors.enabled: true

[root@ip-10-0-0-52 elasticsearch]# netstat -tulpn | grep -i listen | grep
java

tcp 0 0 ::ffff:127.0.0.1:9300 :::*
LISTEN 973/java

tcp 0 0 ::ffff:127.0.0.1:9200 :::*
LISTEN 973/java

[root@ip-10-0-0-52 elasticsearch]# ps -ef | grep elasticsearch | grep -i
-v -e grep -e screen

496 973 1 3 13:18 ? 00:00:07 /usr/bin/java -Xms256m
-Xmx1g -Xss256k -Djava.awt.headless=true -XX:+UseParNewGC
-XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError
-XX:+DisableExplicitGC -Delasticsearch
-Des.pidfile=/var/run/elasticsearch/elasticsearch.pid
-Des.path.home=/usr/share/elasticsearch -cp
:/usr/share/elasticsearch/lib/elasticsearch-1.3.7.jar:/usr/share/elasticsearch/lib/:/usr/share/elasticsearch/lib/sigar/
-Des.default.path.home=/usr/share/elasticsearch
-Des.default.path.logs=/var/log/elasticsearch
-Des.default.path.data=/var/lib/elasticsearch
-Des.default.path.work=/tmp/elasticsearch
-Des.default.path.conf=/etc/elasticsearch
org.elasticsearch.bootstrap.Elasticsearch

[root@ip-10-0-0-52 elasticsearch]# curl -GET http://localhost:9200

{

"status" : 200,

"name" : "Blaze",

"version" : {

"number" : "1.3.7",

"build_hash" : "3042293e4b219dfb855a4e6c64241c530d1abeb0",

"build_timestamp" : "2014-12-16T13:59:32Z",

"build_snapshot" : false,

"lucene_version" : "4.9"

},

"tagline" : "You Know, for Search"

}

[root@ip-10-0-0-52 elasticsearch]# curl -XGET '
http://127.0.0.1:9200/_cluster/health?pretty=true'

{

"cluster_name" : "elasticsearch",

"status" : "green",

"timed_out" : false,

"number_of_nodes" : 1,

"number_of_data_nodes" : 1,

"active_primary_shards" : 0,

"active_shards" : 0,

"relocating_shards" : 0,

"initializing_shards" : 0,

"unassigned_shards" : 0

}

[root@ip-10-0-0-52 elasticsearch]#

When open Kibana web interface it give me below error
Connection Failed
Possibility #1: Your elasticsearch server is down or unreachable

This can be caused by a network outage, or a failure of the Elasticsearch
process. If you have recently run a query that required a terms facet to be
executed it is possible the process has run out of memory and stopped. Be
sure to check your Elasticsearch logs for any sign of memory pressure.
Possibility #2: You are running Elasticsearch 1.4 or higher

Elasticsearch 1.4 ships with a security setting that prevents Kibana from
connecting. You will need to set the following in your elasticsearch.yml:
http.cors.enabled: true
http.cors.allow-origin to the correct protocol, hostname, and port (if not
80) that your access Kibana from. Note that if you are running Kibana in a
sub-url, you should exclude the sub-url path and only include the protocol,
hostname and port. For example, http://mycompany.com:8080, not
http://mycompany.com:8080/kibana.
Click back, or the home button, when you have resolved the connection issue

Please suggest me what cloud be the problem -- Help me how to fix this
issue

Many Thanks,
Madhu

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/94418261-a179-489a-8dc8-37aa3356b74b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

On Thursday, January 29, 2015 at 06:51 CET, madhu@venusgeo.com wrote:

Can anyone please look into this.

This is a volunteer-based mailing list. If want a 24-hour SLA there are
paid options for that.

On Wednesday, January 28, 2015 at 5:43:23 AM UTC-8, ma...@venusgeo.com
wrote:

I don't remember changing anything at all on my logstash server.
As of just yesterday it was working fine! And I used it to run
some queries.

However.. today when I went to my logstash page, I see only thing
message come up:

[...]

Connection Failed
Possibility #1: Your elasticsearch server is down or unreachable
This can be caused by a network outage, or a failure of the
Elasticsearch process. If you have recently run a query that required
a terms facet to be executed it is possible the process has run out of
memory and stopped. Be sure to check your Elasticsearch logs for any
sign of memory pressure.

Your browser's developer console (naming varies) probably contains clues
about the problem. In Chrome you can access it with e.g. Ctrl+Shift+I.

[...]

--
Magnus Bäck | Software Engineer, Development Tools
magnus.back@sonymobile.com | Sony Mobile Communications

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/20150129121307.GD30366%40seldlx20533.corpusers.net.
For more options, visit https://groups.google.com/d/optout.