# Fatal error Java runtime after Dremio upgrade from 4.1.0 to 4.8.0 **URL:** \ **Category:** Uncategorized\ **Created:** [October 27, 2020, 1:45pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483 "2020-10-27T13:45:47Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 27, 2020, 1:45pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/1 "2020-10-27T13:45:47Z")
I have an EC2 instance with Dremio installed. Instance acts as master and coordinator node at the same time, no more Dremio instances exist. Dremio runs inside the Docker container with some volumes mapped. Steps that were taken to updated Dremio: 1. Stop Dremio container 2. Update Docker image (from `4.1.0` to `4.8.0`) by installing a new version from `tar` 3. Run image, log in to Docker image, run `dremio-admin upgrade` 4. After, start Dremio in the running container After starting Dremio again error occurs. After spending some time searching on the Internet, I could find anything that could help solve the issue. You can find `server.out` and error report in `logs.zip`. It doesn’t look like an error with Dremio, more like with Java. I do not know a lot about Java Runtime. Would really appreciate help with that. Thank you. OS: Debian 9 (container) OpenJDK 8 [logs.zip](https://community.dremio.com/uploads/short-url/zjPvh7cwcJz79RiVNXWgUoLDspO.zip) (28.4 KB) ---
**Author:** ![balaji.ramaswamy](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/balaji.ramaswamy/32/843_2.png) [@balaji.ramaswamy](https://community.dremio.com/u/balaji.ramaswamy)\ **Post date:** [October 27, 2020, 2:26pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/2 "2020-10-27T14:26:39Z")
@vmois What version of JDK is this? Also is this openJDK? ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 27, 2020, 4:15pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/3 "2020-10-27T16:15:54Z")
My image is based on OpenJDK 8 Docker container. Should I try a newer version? ---
**Author:** ![laurent](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/laurent/32/16_2.png) [@laurent](https://community.dremio.com/u/laurent)\ **Post date:** [October 28, 2020, 2:26am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/4 "2020-10-28T02:26:23Z")
By any chance, have you simply uncompressed Dremio 4.8.0 on top of Dremio 4.1.0 in your current image, or did you start from the openjdk8 docker image? ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 28, 2020, 10:24am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/5 "2020-10-28T10:24:02Z")
My base image is openjdk:8-jdk. Example of my Dockerfile: ```auto FROM openjdk:8-jdk ARG DOWNLOAD_URL=https://download.dremio.com/community-server/4.8.0-202009180238090394-b0a98b73/dremio-community-4.8.0-202009180238090394-b0a98b73.tar.gz RUN \ mkdir -p /opt/dremio \ && wget -q "${DOWNLOAD_URL}" -O dremio.tar.gz \ && tar vxfz dremio.tar.gz -C /opt/dremio --strip-components=1 \ && rm -rf dremio.tar.gz WORKDIR /opt/dremio ADD libs jars ADD conf/dremio.conf conf ADD conf/dremio-env conf EXPOSE 9047 31010 45678 47470 ENV DREMIO_HOME /opt/dremio ENTRYPOINT ["bin/dremio", "start-fg"] ``` What I did for the Dremio update is replaced the `DOWNLOAD_URL` from version 4.1.0 to 4.8.0 and re-run the build. ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 28, 2020, 11:20am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/6 "2020-10-28T11:20:09Z")
Also, will add extra JAVA runtime params from dremio conf: ```auto DREMIO_JAVA_SERVER_EXTRA_OPTS=" -XX:+UseG1GC -XX:G1HeapRegionSize=8M -XX:InitiatingHeapOccupancyPercent=25 -XX:+AggressiveOpts -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods" ``` Maybe, they affect the runtime and cause an error. @balaji.ramaswamy @laurent ---
**Author:** ![laurent](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/laurent/32/16_2.png) [@laurent](https://community.dremio.com/u/laurent)\ **Post date:** [October 28, 2020, 4:06pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/7 "2020-10-28T16:06:51Z")
I would try to disable the following options and see if the problem disappear or not: ```auto -XX:+AggressiveOpts -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods ``` Note that Dremio also publishes a Docker image available at [https://hub.docker.com/r/dremio/dremio-oss](https://hub.docker.com/r/dremio/dremio-oss) ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 28, 2020, 4:16pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/8 "2020-10-28T16:16:32Z")
Removing Java options doesn’t help. I will try to use the official Docker image. ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 28, 2020, 9:02pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/9 "2020-10-28T21:02:56Z")
My Docker image is essentially the same as the official Docker image. I checked the layers of the newest image (`docker history -no-trunc dremio/dremio-oss:4.8.0`). Also, checked the old Dockerfile ([https://github.com/dremio/dremio-cloud-tools/blob/master/images/dremio-oss/Dockerfile](https://github.com/dremio/dremio-cloud-tools/blob/master/images/dremio-oss/Dockerfile)). Generals Dremio install steps are the same, the same openjdk-8. ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [October 28, 2020, 9:19pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/10 "2020-10-28T21:19:36Z")
From logs, ‘aprMajorVersion’ ‘()I’ in ‘io/netty/internal/tcnative/Library’. Maybe, something there. ![Screenshot 2020-10-28 at 22.18.50](https://us1.discourse-cdn.com/flex020/uploads/dremio/original/2X/b/b8d59a6e706829d5eccf0d6525ca47d94c9e8317.png) ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [November 2, 2020, 8:50am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/11 "2020-11-02T08:50:28Z")
@balaji.ramaswamy @laurent any ideas regarding the issue? ---
**Author:** ![laurent](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/laurent/32/16_2.png) [@laurent](https://community.dremio.com/u/laurent)\ **Post date:** [November 2, 2020, 9:59pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/12 "2020-11-02T21:59:29Z")
I tried to reproduce with no luck. I noticed that your Docker includes external jars. Without the list of those, I cannot reproduce exactly your situation, but this is very likely that one of them might include a copy of netty native library in some form which might conflict and cause the crash you’re experiencing. ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [November 3, 2020, 9:52am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/13 "2020-11-03T09:52:58Z")
You can be right. The only external jar is `dremio-flight-connector-0.11.0-SNAPSHOT-shaded.jar`. This is quite an old version. The newest is `0.26.0`. I will try to run dremio with this version. ---
**Author:** ![vmois](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/vmois/32/2402_2.png) [@vmois](https://community.dremio.com/u/vmois)\ **Post date:** [November 3, 2020, 10:01am UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/14 "2020-11-03T10:01:41Z")
Using `dremio-flight-connector` version `0.26.0` solved the problem. Essentially, problem with external jars. Dremio is not failing shortly after the start and continues to work. Thank you very much for pointing in the right direction @laurent! ---
**Author:** ![laurent](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/laurent/32/16_2.png) [@laurent](https://community.dremio.com/u/laurent)\ **Post date:** [November 3, 2020, 4:07pm UTC](https://community.dremio.com/t/fatal-error-java-runtime-after-dremio-upgrade-from-4-1-0-to-4-8-0/6483/15 "2020-11-03T16:07:54Z")
Check out [Dremio 4.9.1](https://docs.dremio.com/release-notes/49-release-notes.html) recently released: flight connector is now built in.