Potential JVM bug issue?


(jubilee) #1

For the past few weeks, I’ve been able to deploy Graylog successful. Lately, however, in an attempt to redeploy Graylog, I’ve been experiencing JVM options.

Error Logs

Current master is

Launching logging-graylog-0 as master

pod/logging-graylog-0 labeled

Downloading Graylog Plugins...

Downloading https://github.com/graylog-labs/graylog-plugin-slack/releases/download/3.0.0/graylog-plugin-slack-3.0.0.jar ...

Downloading https://github.com/omise/graylog-plugin-function-check-diff/releases/download/1.0.0/graylog-plugin-function-check-diff-1.0.0.jar ...

Downloading https://github.com/omise/graylog-plugin-custom-alert-condition/releases/download/v1.0.0/graylog-plugin-custom-alert-condition-1.0.0.jar ...

Downloading https://github.com/Graylog2/graylog-plugin-auth-sso/releases/download/2.5.0/graylog-plugin-auth-sso-2.5.0.jar ...

Downloading https://github.com/graylog-labs/graylog-plugin-internal-logs/releases/download/2.4.0/graylog-plugin-internal-logs-2.4.0.jar ...

Downloading https://github.com/graylog-labs/graylog-plugin-metrics-reporter/releases/download/2.4.0-beta.3/metrics-reporter-prometheus-2.4.0-beta.3.jar ...

Starting graylog

Graylog Home /usr/share/graylog

Graylog User graylog

JVM Options

bash: line 39: gosu: command not found

(Ben van Staveren) #2

Actually, nothing to do with JVM Options - looks like gosu isn’t installed on the docker image you’re using.


(jubilee) #3

Thanks for the response @benvanstaveren! It turns out that the docker image graylog2/server was Deprecated I’ve since then updated the docker image to graylog2/graylog:2.5 I was hoping it would fix the problem, but the issue persists.

Current master is IP
Launching logging-graylog-0 as coordinating
pod/logging-graylog-0 labeled
Starting graylog
Graylog Home /usr/share/graylog
Graylog User graylog
JVM Options -Djava.net.preferIPv4Stack=true -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow -Xms1024m -Xmx1024m
error: failed switching to "graylog": operation not permitted```

(Jan Doberstein) #4

what image did you use? When did you pull this image? (what checksum?)

Where did you run this image in? Kubernetes, Openshift, DockerSwarm?
How does your configuration look like?

We worked in the last weeks on switching away from gosu so the image has changed multiple times.


(jubilee) #5

“What image did you use?” I’m using the docker image to graylog2/graylog:2.5.
“Where did you run this image in?” Yes, I’m currently running the Graylog on Kubernetes via Helm Chart.

Graylog config file:

Below is the snippet of my Docker environment for Graylog.

env:
        - name: GRAYLOG_SERVER_JAVA_OPTS
          values: "-Xms1g -Xmx1g -XX:NewRatio=1 -server -XX:+ResizeTLAB -XX:+UseConcMarkSweepGC -XX:+CMSConcurrentMTEnabled -XX:+CMSClassUnloadingEnabled -XX:+UseParNewGC -XX:-OmitStackTraceInFastThrow"

Thanks a lot @jan


(Jan Doberstein) #6

graylog2/graylog:2.5.

That is not accurate as we rebuild the image multiple times - first with the release of 2.5.1 and second with some additional bug fixes in the image.

That is reason I had asked for the checksum - maybe you just want to pull the image again, just to be sure to have the latest 2.5 image. As this is working for me without a problem!


(system) closed #7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.