Hello && welcome @aqxea
I went over all your configurtion and logs, what I was noticing was these errors through our you log file.
ERROR [VersionProbe] Unable to retrieve version from Elasticsearch node: Failed to connect to /127.0.0.1:9200. - Connection refused.
INFO [VersionProbe] Elasticsearch is not available. Retry #2
ERROR [MongoDBProcessingStatusRecorderService] Couldn't persist processing status
ERROR [InMemoryRolePermissionResolver] Could not find roles collection, no user roles updated
ConnectException: Connection refused
Looking over your OS config I dont see the port 9200 open
Example of mine
[root@graylog opensearch]# cat /etc/opensearch/opensearch.yml | egrep -v "^\s*(#|$)"
cluster.name: graylog
path.data: /var/lib/opensearch
path.logs: /var/log/opensearch
network.host: 127.0.0.1
http.port: 9200
action.auto_create_index: false
discovery.type: single-node
bootstrap.memory_lock: true
plugins.security.disabled: true
plugins.security.system_indices.enabled: false
[root@graylog opensearch]#
What I have noticed in the forum and depending on users environment, localhost may not work, but using the loop back address does. What I have done in my GL configuration file is set it like this
elasticsearch_hosts = http://127.0.0.1:9200
This matches my opensearch.yml file above.
TBH having 0.0.0.0
states “connect to anything”, not good for security reseasons.
As for MongoDb logs.
caused by: java.net.ConnectException: Connection refused
Check MongoDb config file
#Network interfaces
net:
port: 27017
bindIp: 127.0.0.1 # Listen to local interface only, comment to listen on all interfaces.
# bindIp: 0.0.0.0
With Graylog you can login the Web UI without opensearch running BUT you cannot without MongoDb.
EDIT: I just realize you stated that this VM was rebooted, this maybe the reason why the logs shown " Elasticsearch is not available. Retry #1", Sidenote, ensure the address are reachable over you network.