Closed riverar closed 4 years ago
dear @riverar
the solution might be simple - please check this FAQ entry: https://docs.graylog.org/en/3.1/pages/faq.html#dedicated-partition-for-the-journal
This is the result from my research in: https://github.com/Graylog2/graylog2-server/issues/2348
We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our discussion forum or join the #graylog channel on freenode IRC.
Thank you!
Hi @jalogisch, this is a new volume, the equivalent of a brand new dedicated partition. Am I missing something? Thanks!
check if the user is able to write to this directory and if that directory does contain other files.
@jalogisch It's writable. And I'm using a new volume each time.
can the userid 1100 what is used by the user graylog write to that folder?
@jalogisch It's writable. And I'm using a new volume each time. The graylog user is able to write to the folder during startup.
what filesystem is that volumen on @riverar ?
Did you have the same system if you create a docker-volumen and use that?
I tried deploying Graylog 3.1 as-is, vanilla, with its own exclusive volumes, and it fails to start up.
Exception snippet:
Repro steps:
graylog
folder to work withindocker-compose.yml
with the contents of the file belowconfig
folderconfig
folder, download the following files (from docs):graylog
folder, issue command:docker-compose up
docker-compose.yml:
docker version