Hey there, My graylog was working perfect until I ran a search and then it failed. I have checked the following: Service status for graylog and ElasticSerach: both running, I reloaded both. Logs for GrayLog : Could not connect to http://10.111.111.224/9200 Logs for ES: Just Info no errors It t…

In this case you’ll have to tune the JVM settings of Graylog and Elasticsearch accordingly. I’d recommend using 1 GB heap for Elasticsearch and 1 GB heap for Graylog. MongoDB should be happy with 64 MB of memory. Make sure that there is some memory left for the operating system to use as a disk buf…

Ah, my bad then, sorry I’m newbie. I assumed if the health check is fine then the elasticsearch_hosts URI is working. But how I can check it?

@jochen Here are my config files: Graylog-server.conf: elasticsearch_hosts = http://10.111.111.224:9200/ elasticsearch.yml: cluster.name: graylog network.host: 10.111.111.224 http.port: 9200

Update: I have tried to reinstall the elasticsearch using: wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add - echo “deb https://artifacts.elastic.co/packages/5.x/apt stable main” | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list $ sudo apt update && sudo apt …

[image] shayz: but no success What’s the complete output of these commands? What’s in the logs of your Elasticsearch node(s)?

@jochen Here is the last page from graylog.log in ES logs [2018-04-05T14:08:59,258][INFO ][o.e.n.Node ] [] initializing ... [2018-04-05T14:08:59,554][INFO ][o.e.e.NodeEnvironment ] [Z2kVnoJ] using [1] data paths, mounts [[/ (rootfs)]], net usable_space [93gb], net total_space …

[image] shayz: [2018-04-05T14:09:12,108][INFO ][o.e.h.n.Netty4HttpServerTransport] [Z2kVnoJ] publish_address {127.0.0.1:9200}, bound_addresses {[::1]:9200}, {127.0.0.1:9200} 127.0.0.1 is the local loopback interface and only accessible from the same machine. Loopback | Virtual loop…

@jochen It was the default setting and it was working before until I made a wrong query string in search on web interface. What should I change now?

[image] shayz: What should I change now? Make sure that your Graylog nodes (elasticsearch_hosts in the configuration file) are able to communicate with the HTTP API of your Elasticsearch nodes (network.host and related settings in the configuration file).

Hey @jochen , Appreciate your help but still no chance.Here are my config files: #elasticsearch.yml: cluster.name: graylog network.host: 10.1.11.224 #graylog.conf is_master = true node_id_file = /etc/graylog/server/node-id password_secret = xxxx root_password_sha2 = xxxxx plugin_d…

[image] shayz: after some seconds the whole system dies and the the elasticsearch service stops. What does that mean exactly?

Error : Could not connect to ElasticSearch

Graylog Central (peer support)

jochen (Jochen) April 5, 2018, 6:23pm 10

127.0.0.1 is the local loopback interface and only accessible from the same machine.

Elasticsearch not getting messages

Topic		Replies	Views
Can't Connect to ElasticSearch? Graylog Central (peer support)	17	5035	August 15, 2017
Graylog not able to connect to Elasticsearch cluster Graylog Central (peer support)	9	12255	May 17, 2017
Unable to perform search query error Graylog Central (peer support)	14	7204	October 14, 2019
Elasticsearch stops running on reboot Graylog Central (peer support)	15	2654	September 25, 2022
Graylog and Elasticsearch work but I can't reach web interface Graylog Central (peer support)	3	3928	September 13, 2017

Error : Could not connect to ElasticSearch

Related topics