System information is currently unavailable - Timeout Issues

I am getting the below issue in my nodes page. I currently run 1 node with everything on it. I do not go through a proxy.
image
Looking through the log shows a lot of:

2021-05-11T16:54:26.287-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:54:36.348-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:54:40.230-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:54:52.243-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:54:52.258-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:55:02.328-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:55:04.323-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:55:14.334-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:55:16.247-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout
2021-05-11T16:55:24.408-04:00 WARN  [ProxiedResource] Unable to call https://172.16.8.214:9000/api/system/metrics/multiple on node <21ece229-31c0-4f6b-b1ec-d764c59a6488>: timeout

Below are what I believe are the relevant conf settings. I have tried with and with out specifying HTTPS.

http_bind_address = 172.16.8.214:9000
http_publish_uri = https://172.16.8.214:9000/
#http_external_uri =

From other troubleshooting I have found I ran the command :

$ curl -i ‘https://172.16.8.214:9000/api/?pretty=true

and get the output:

HTTP/1.1 307 Temporary Redirect
Location: https://172.16.8.214:9000/
X-Graylog-Node-ID: 21ece229-31c0-4f6b-b1ec-d764c59a6488
X-Runtime-Microseconds: 223
Content-Length: 0

Any ideas on what else to try or check?

Hello,

What does your service status look like.

systemctl status elasticsearch

Does you elasticsearch.yaml configuration network.host: match your graylog confguration file configuration elasticsearch_hosts = ?

Any firewalls enabled on your server?

EDIT: Try this and see what you get.

curl -i ‘http://172.16.8.214:9000/api/?pretty=true’

Since you stated your using HTTPS it may be your certificates. Try setting it back to HTTP and restart graylog service. In the past I have missed a configuration and my HTTP connection still didnt work.

Thank you @gsmith after testing it seems to be my certificates. It was working but it is around time to replace them anyway. Thank you!

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.