Graylog2 / docker-compose

A set of Docker Compose files that allow you to quickly spin up a Graylog instance for testing or demo purposes.
Apache License 2.0
395 stars 138 forks source link

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

Open bpauly opened 1 year ago

bpauly commented 1 year ago

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.

hertell commented 11 months ago

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 commented 10 months ago

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 commented 6 months ago

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