Graylog2 / Graylog2/graylog-docker

Updating to 4.3.4 or later causes a core dump

Open
#222 3 comments 0 reactions 0 assignees View on GitHub
triaged
Dominant language
Shell
Stars
435
Forks
130
PR merge metrics
No merged PRs in 30d

Description

Versions up to 4.3.3 worked fine for me.

After upgrading to 4.3.4, 4.3.5 or 4.3.6 I got core dumps.

I stripped down my docker-compose.yml to the bare minimum, and even this does not work:
```
version: '2'
services:
graylog:
image: graylog/graylog:4.3.3
restart: always
```

`docker-compose up --build --force-recreate` results in:
```
Creating graylog_graylog_1 ... done
Attaching to graylog_graylog_1
graylog_1 | #
graylog_1 | # There is insufficient memory for the Java Runtime Environment to continue.
graylog_1 | # Cannot create GC thread. Out of system resources.
graylog_1 | # An error report file with more information is saved as:
graylog_1 | # /usr/share/graylog/hs_err_pid7.log

```

`docker logs -f graylog_graylog_1` shows the core dump:
```
...
VM Arguments:
jvm_args: -Dlog4j2.formatMsgNoLookups=true -Djdk.tls.acknowledgeCloseNotify=true -XX:+UnlockExperimentalVMOptions -XX:NewRatio=1 -XX:MaxMetaspaceSize=256m -XX:+ResizeTLAB -XX:-OmitStackTraceInFastThrow -Dlog4j.configurationFile=/usr/share/graylog/data/config/log4j2.xml -Djava.library.path=/usr/share/graylog/lib/sigar/ -Dgraylog2.installation_source=docker
java_command: /usr/share/graylog/graylog.jar server -f /usr/share/graylog/data/config/graylog.conf
java_class_path (initial): /usr/share/graylog/graylog.jar
Launcher Type: SUN_STANDARD

Environment Variables:
JAVA_HOME=/opt/java/openjdk
PATH=/usr/share/graylog/bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Signal Handlers:
SIGSEGV: [libjvm.so+0xb3b0d0], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGBUS: [libjvm.so+0xb3b0d0], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGFPE: [libjvm.so+0x963540], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGPIPE: [libjvm.so+0x963540], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGXFSZ: [libjvm.so+0x963540], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGILL: [libjvm.so+0x963540], sa_mask[0]=11111111011111111101111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGUSR1: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGUSR2: [libjvm.so+0x963af0], sa_mask[0]=00000000000000000000000000000000, sa_flags=SA_RESTART|SA_SIGINFO
SIGHUP: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGINT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGTERM: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGQUIT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none

...
```

Reverting back to 4.3.3 shows no errors at all.

Please advise.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.