Hi Sandro, Thanks for your reply, Here is detail output from graylog2 server when i update the configuraiton you recommended. grep -v ^# /etc/elasticsearch/elasticsearch.yml /etc/graylog2.conf | grep cluster /etc/elasticsearch/elasticsearch.yml:cluster.name: naisu07-lab02prod /etc/graylog2.conf:elasticsearch_cluster_name = "naisu07-lab02prod" grep 127.0.0.1 /etc/graylog2.conf rest_listen_uri = http://127.0.0.1:12900/ rest_transport_uri = http://127.0.0.1:12900/ Error out curl 'http://127.0.0.1:9200/_status?pretty=true' curl: (7) couldn't connect to host But when i ran this comamnd no error. curl 'http://127.0.0.1:12900/_status?pretty=true' Still seeing errors with graylog2-servers. 2014-01-06 19:35:47,748 INFO : org.elasticsearch.plugins - ["graylog2"] loaded [], sites [] 2014-01-06 19:35:49,158 ERROR: org.elasticsearch.gateway.local.state.meta - ["graylog2"] failed to read local state, exiting... org.elasticsearch.ElasticSearchIllegalStateException: node is not configured to store local location BR. ~Sonu.
On Monday, January 6, 2014 11:47:15 PM UTC-8, Sandro Roth wrote: > Hi Sunu > > You should not need to link your elasticsearch config file > to /etc/graylog2-elasticsearch.yml. > All you need is to set up elasticsearch and point graylog to it. > > So install elasticsearch (preferably with the rpm, tarball works too) and > change 'cluster.name' in it's configuration to some name of your choice. > After that start it and make sure it works! You can check that by > connecting to the api: > > # curl 'http://127.0.0.1:9200/_status?pretty=true' > > Now change 'elasticsearch_cluster_name' in your graylog config to the same > name and try to start it again. > Make your you don't have any typos in there... > > # grep -v ^# /etc/elasticsearch/elasticsearch.yml /etc/graylog2.conf | > grep cluster > /etc/elasticsearch/elasticsearch.yml:cluster.name: graylog_new > /etc/graylog2.conf:elasticsearch_cluster_name = graylog_new > > > Hope that helps. > Sandro > > > On Tuesday, January 7, 2014 3:06:16 AM UTC+1, Sunu wrote: >> >> Found rpm version for redhat and installed and make the two changes as >> cluster.name and node.name, seems same issues. >> >> -Sunil. >> >> On Monday, January 6, 2014 1:35:51 PM UTC-8, Sunu wrote: >> >>> Hi Jane, >>> >>> I am running Redhat 6.3 kernel ver - 2.6.32-279.el6.x86_64, I did not >>> found rpm for elasticsearch. I downloded tar.ball and extracted. The >>> version is - /usr/local/gray/elasticsearch-0.90.7. >>> >>> Yml PATH is - >>> /usr/local/gray/elasticsearch-0.90.7/config/elasticsearch.yml link to >>> /etc/graylog2-elasticsearch.yml >>> >>> Regrards, >>> -Sunil. >>> >>> On Sunday, January 5, 2014 1:00:50 AM UTC-8, jane white wrote: >>> >>>> Have you install the elasticsearch.rpm version? >>>> >>>> Why don't you check your configure file( elasticsearch.yml path)? >>>> >>>> >>>> >>>> 2014년 1월 4일 토요일 오전 6시 31분 49초 UTC+9, Sunu 님의 말: >>>>> >>>>> I am seeing errros with graylog2-server-0.20.0-preive.8 >>>>> >>>>> I am running - java -jar graylog2-server.jar --debug and I am >>>>> getting this errors, please help. >>>>> >>>>> 2014-01-03 10:58:45,424 DEBUG: org.elasticsearch.transport.netty - >>>>> [graylog2-production] disconnected from >>>>> [[#zen_unicast_1#][inet[/172.24.1.55:9300]]] >>>>> 2014-01-03 10:58:45,424 DEBUG: org.elasticsearch.discovery.zen - >>>>> [graylog2-production] filtered ping responses: (filter_client[true], >>>>> filter_data[false]) {none} >>>>> 2014-01-03 10:58:45,426 DEBUG: org.elasticsearch.transport.netty - >>>>> [graylog2-production] connected to node >>>>> [[#zen_unicast_1#][inet[/172.24.1.55:9300]]] >>>>> 2014-01-03 10:58:45,428 DEBUG: >>>>> org.elasticsearch.discovery.zen.ping.unicast - [graylog2-production] [3] >>>>> filtering out response from >>>>> [graylog2-production][RePqKcpDTq-BunBF9TSNaw][inet[/172.24.1.55:9300]], >>>>> not >>>>> same cluster_name [elasticsearch] >>>>> 2014-01-03 10:58:46,926 DEBUG: >>>>> org.elasticsearch.discovery.zen.ping.unicast - [graylog2-production] [3] >>>>> filtering out response from >>>>> [graylog2-production][RePqKcpDTq-BunBF9TSNaw][inet[/172.24.1.55:9300]], >>>>> not >>>>> same cluster_name [elasticsearch] >>>>> 2014-01-03 10:58:47,420 ERROR: org.graylog2.Main - >>>>> >>>>> ################################################################################ >>>>> ERROR: No ElasticSearch master was found. >>>>> Need help? >>>>> * Official documentation: http://support.torch.sh/help/kb >>>>> * Mailing list: >>>>> http://support.torch.sh/help/kb/general/forums-mailing-list >>>>> * Issue tracker: >>>>> http://support.torch.sh/help/kb/general/issue-trackers >>>>> * Commercial support: http://www.torch.sh/ >>>>> But we also got some specific help pages that might help you in this >>>>> case: >>>>> * >>>>> http://support.torch.sh/help/kb/graylog2-server/connecting-to-an-elasticsearch-cluster >>>>> Terminating. :( >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
