tkohhh

I am also getting this error after updating Unraid to 6.10.3 from 6.9.2.

This problem is still persistent after updating to graylog 4.3.3 How can we get the developers to look at this issue?

I'm using docker compose as described here: https://whitematter.tech/posts/run-graylog-with-docker-compose-on-unraid/ Repositories are: mongo:5.0 docker.elastic.co/elasticsearch/elasticsearch-oss:7.10.2 graylog/graylog:4.3.3 Prior to updating to Unraid 6.9.2, there were no issues. Currently I'm running with logging set to...

If you need a second example of the data/journal directories, let me know!

I just want to report that this is still an issue after upgrading to Graylog 4.3.4

My journal does indeed reside on an Unraid "cache pool", but that particular share is set to "Cache:prefer". This means it permanently lives on the cache pool and is never...

Respectfully, I think you may be misunderstanding how Unraid cache works. The cache pool IS part of the file system... it's just another drive (usually an SSD for the speed...

Here are my findings: 1. Moving the journal to the array (instead of the cache pool) had no effect. I received the error after about 15 minutes. 2. Disabling all...

OK... that may be good news. I've been running for the last hour with the Unraid remote logging disabled, and no error. I'm going to turn it on with UDP...

UDP did generate the error after about 90 minutes. I'm going back to disabling the Unraid remote logging. I'll let it run for longer this time to see if I...