Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

volume mount point for graylog_data to /usr/share/graylog/data/data ? #27

Open
bpauly opened this issue Apr 11, 2023 · 3 comments
Open
Assignees
Labels

Comments

@bpauly
Copy link

bpauly commented Apr 11, 2023

The current /open-core/docker-compose.yml and /enterprise/docker-compose.yml have the following configuration to mount the graylog_data volume:

volumes:
  - "graylog_data:/usr/share/graylog/data/data"
  - "graylog_journal:/usr/share/graylog/data/journal"

Is the /usr/share/graylog/data/data correct or should this actually go to /usr/share/graylog/data ?
There doesn't seem to be anything saved under /usr/share/graylog/data/data and it would seem desirable to save the content under /usr/share/graylog/data to a persistent volume.

@bernd bernd added the triaged label Apr 19, 2023
@bernd bernd self-assigned this Apr 19, 2023
@hertell
Copy link

hertell commented Oct 29, 2023

This has to be wrong. That directory contains nothing. Also the journal-location seems to be wrong, if the intention is to split these into two different volumes. it should be something like this:

The journal should be configured into an other location in gralog.conf
message_journal_dir=journal

And the volume should then be something like this

volumes:
  - "graylog_data:/usr/share/graylog/data"
  - "graylog_journal:/usr/share/graylog/journal"

@BenAigan
Copy link

I have been fighting this issue for a while now, every time I docker compose down and back up I just get errors:

11:37:24.723 [main] ERROR org.graylog2.storage.versionprobe.VersionProbe - Unable to retrieve version from Elasticsearch node: Hostname a84xxxxxx5c3 not verified:
certificate: sha256/plUJdntgAxxxxxxxNsH5q2yXsuPU+YVEIXRM=
DN: CN=b22xxxxxde5e
subjectAltNames: [127.0.0.1, 0:0:0:0:0:0:0:1, 172.28.0.2, localhost, b225613ede5e, 0:0:0:0:0:0:0:1]. - Hostname a84xxxxxx5c3 not verified:
certificate: sha256/plUJdntgAxxxxxxxNsH5q2yXsuPU+YVEIXRM=
DN: CN=b22xxxxxde5e
subjectAltNames: [127.0.0.1, 0:0:0:0:0:0:0:1, 172.28.0.2, localhost, b225613ede5e, 0:0:0:0:0:0:0:1].

Seems like a great product when it works, I think I will try and find a different product

@j3k0
Copy link

j3k0 commented Mar 7, 2024

Same issue with "hostname not verified" after a restart (after pulling an image update). Any way to fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants