We keep getting the issue of the journal filling with unprocessed messages. I have found the solutions of: Removing and recreating the internal ‘server.log’ text file or fully deleting the ‘journal’ file.
What I would like to know is why does this issue keep occurring? It is not viable for us to have to go into the back-end of our Graylog each day to resolve this issue and I would like the be able to stop it all together, has anyone got any ideas as to why this occurs?
Checked the logs and all I could find was the disk usage was over 85% and then the disk went 100% full. I believe that this was the cause of the issue, I will give it a few hours to ensure we don’t run into this problem again.