Hello @Chase
I see there has been some issues in the past with the journal.
Ill try to explain those messages above.
You may find that answer here for that log message.
Seams like you having issues with Elasticsearch, I would check you status/health of your Elasticsearch.
curl -XGET http://localhost:9200/_cluster/health?pretty=true
Knowing what your Graylog and elasticsearch configurations look like, I might be able to help further.
When your journal get to full this will happen, hence something is wrong with Elasticsearch. Since Elasticsearch grabs the messages from the journal and indices them. that would be the first place I would look, especially the logs. You maybe having a problem all this time but it takes a few days to notice. No need to reboot all your doing is restarting the services and perhaps cleaning out the journal.
To be honest I would go over all you logs /var/log
to find if anything could pertain to this issue. If you running a load balancer ( i.e. nginx/apache) I would also check those logs.
What version are you running?
- Elasticsearch
- Graylog
- MongoDb
This also could be a direct results with resources and distributions of resources.
It possible Graylog HDD is getting full and Elasticsearch stops index message in the journal, hence filling up until you reboot.
root # df -h
If you can try restarting Graylog service and tail its log file
systemctl restart graylog-server
and
tail -f /avr/log/graylog/server.log
Watch how Graylog starts up and check for issues, just a thought you may find something.