I am new in graylog and after installing the graylog, I have faced this isse:
While retrieving data for this widget, the following error(s) occurred:
Elasticsearch exception [type=cluster_block_exception, reason=blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];].
Could someonehelp on how to fix this? I have researched online and the troubleshooting was to run the command: ```
curl -X PUT “localhost:9200/_all/_settings” -H ‘Content-Type: application/json’ -d’{ “index.blocks.read_only” : false } }’
but still no joy.
The service is running (elasticsearch and graylog), I can log in in the admin panel but only facing that issue.
It would help if you posted more about your setup, any changes you might have made, why you thought the command you ran would solve the problem. At the bottom is a link to guide you to providing more information.
In the mean time, did you run out of space on your elasticsearch server? Have you checked the Graylog logs and the elasticsearch logs?
tail -f /var/log/graylog-server/server.log
(Elasticsearch is whatever you called your instance located in /var/log/elasticsearch… possibly graylog.log)
Don’t post the whole log, just parts that are relevant - and please use the forum tools such as </> to make your code/logs more readable. Also review below for help on giving good information when asking a question.
I have fixed that parted and believe because I have changed my data store paths.
Now in the nodes it gives the error mentioned above when clicking on the node and below the node name says system information is currently unavailable.
And in the log it says this
Error getting data
We had trouble fetching some data required to build this page, so here is a picture instead.
FetchError: There was an error fetching a resource: Internal Server Error. Additional information: Failed to connect to server/127.0.1.1:9000
Check your Graylog logs for more information.
The output… from what? It looks like the same lines repeated so we would be better served by just putting in one one and saying it repeats… Your follow up post doesn’t tell me much either - you fixed what part? you changes data store paths… for what mongoDB? Elaticsearch? If you did either of those did you adjust the Graylog configuration file to point to it? What was it that you were doing before the problem happened? What have you tried to do to fix it? Are your graylog logs different now that you fixed whatever part you fixed? Can you post your Graylog configuration … use this command for just the details:
Apologises for the confusion.
The 1st issue ( While retrieving data for this widget, the following error(s) occurred:
Elasticsearch exception [type=cluster_block_exception, reason=blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];].) was fixed due the changes in the paths in the elasticsearch.yml file. HAS BEEN SOLVED
The 2nd issue is the info that displayes in the node:
I don’t see anything in the graylog server.conf that tells Graylog where your elasticsearch_hosts are… that must be defined - look for this commented line.
If your using your local IP Address (192.168.1.10) for your URL and not your loop back ( 127.0.0.1.) without a DNS server make sure your /etc/host file is correct.
If you make this changes that @tmacgbay and I suggest, don’t forget to restart Graylog service.
We had trouble fetching some data required to build this page, so here is a picture instead.
FetchError: There was an error fetching a resource: Internal Server Error. Additional information: Failed to connect to myserver/127.0.1.1:9000
Check your Graylog logs for more information.
It should be set like this unless you secured your elasticsearch. If its a default configuration no need to use a username or password . The following setting in your Graylog config file should be good. Take note this is version 4.2 and I’m not sure what version you have.
elasticsearch_hosts = http://10.50.1.40:9200
Remember to restart your service after adjusting your config files.
