Support for Graylog 5.x

[pschichtel]

When upgrading the image to 5.0.1 graylog fails to start up with the following message:

Unrecognized VM option 'UseCGroupMemoryLimitForHeap'

I guess the reason for this is that fact that graylog 5 runs on Java 17.

Other significant changes in graylog 5:

• Minimum MongoDB version is now 5, with support for 6.
• Support for OpenSearch 2.x has been added.

[mazmar]

I am facing the same issue, but one thing to note is that 4.3.8 already supports mongodb 5.x so I was able to upgrade mongodb and still run the 4.3.8.

as @pschichtel said it crashes on the uncrecognized option

[pschichtel]

I removed the option in a local copy of the chart and graylog starts up as expected, but I'm still facing other issues while attempting to use OpenSearch (using the opensearch operator). Once I have it running I intent to open a PR.

[pschichtel]

4.3.8 already supports mongodb 5.x

@mazmar do you have a source for this?

[pschichtel]

Ok found it.

The Graylog 5 upgrade documentation confirms it: https://go2docs.graylog.org/5-0/upgrading_graylog/upgrading_graylog.html#version-compatibility
The Graylog 4.x installation documentation does not list it, but I guess they haven't updated that one: https://go2docs.graylog.org/4-x/downloading_and_installing_graylog/installing_graylog.html

[mazmar]

Sorry, yes you are correct they did not update the documentation for 4.x I did not notice that. I only checked the upgrade instructions last week.

Anyway, I've set the heap manually as it said in values.yaml and it doesn't use the option UseCGroupMemoryLimitForHeap. It started correctly after that and I didn't need to adjust anything else. I am running unsupported ES 7.14.

Only problem is that after upgrading mongo to last version 5 from bitnami the arbitter is broken :( but that is not part of this chart. I will upgrade to mongo 6 this week.

[dsiperek-vendavo]

I was able to upgrade also by just setting the heapSize in value.yaml file.

[pauronda-visma]

Hi there.
I followed your steps:

• set heapSize
• used last bitnami mongodb (version 6.0.3) chart
• used opensearch 2.3.0 deployed with official helm chart
• Graylog image: graylog/graylog:5.0.2

It almost worked, but it gets stuck in this point:
/entrypoint.sh: line 56: 37 Killed "${JAVA_HOME}/bin/java" ${GRAYLOG_SERVER_JAVA_OPTS} -jar -Dlog4j.configurationFile=${GRAYLOG_HOME}/config/log4j2.xml -Djava.library.path=${GRAYLOG_HOME}/lib/sigar/ -Dgraylog2.installation_source=docker ${GRAYLOG_HOME}/graylog.jar server -f ${GRAYLOG_HOME}/config/graylog.conf

I feel that maybe is the ${GRAYLOG_SERVER_JAVA_OPTS} parameter in -jar on the entrypoint.sh

charts/charts/graylog/templates/configmap.yaml

Line 241 in 4e91670

"${JAVA_HOME}/bin/java" \

Could you help me?

[pauronda-visma]

Hi again,
sorry for bothering you.

It worked after modifying entrypoint.sh

I hardcoded the Java VM options from graylog 5 docker repository and worked.

-Dlog4j2.formatMsgNoLookups=true -Djdk.tls.acknowledgeCloseNotify=true -XX:+UnlockExperimentalVMOptions -XX:-OmitStackTraceInFastThrow -XX:+UseG1GC -server

More info:
https://github.com/Graylog2/graylog-docker/blob/56c630a6c43a98b49802555bea314cf132f1a86a/docker/oss/Dockerfile#L67

EDIT: I realized it can be passed as a value using greylog.javaOpts

charts/charts/graylog/values.yaml

Line 62 in 3e07a73

javaOpts: "-Dlog4j2.formatMsgNoLookups=true -Djdk.tls.acknowledgeCloseNotify=true -XX:+UnlockExperimentalVMOptions -XX:NewRatio=1 -XX:MaxMetaspaceSize=256m -server -XX:+ResizeTLAB -XX:-OmitStackTraceInFastThrow"

[pschichtel]

@pauronda-visma Intersting. for me it started, but the UI was unable to perform search API requests against the OpenSearch instance. I haven't been able to get back to my local setup for this.

[pauronda-visma]

Same was for me, but after removing the value graylog.elasticsearch.version on values.yaml it worked for me.
https://github.com/KongZ/charts/blob/main/charts/graylog/values.yaml#L403

More info:
#133
Graylog2/graylog2-server#14236

[luizjr]

Error, not connecting to opensearch cluster

[luizjr]

I managed to update, and I made a pull request.

#138