# Graylog no longer works following an upgrade to Graylog Server 7.1.4 **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [July 2, 2026, 6:36am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409 "2026-07-02T06:36:02Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 6:36am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/1 "2026-07-02T06:36:02Z")
Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question. **Don’t forget to select tags to help index your topic!** **1. Describe your incident:** After upgrading from Graylog Server 7.0.x to 7.1.4, it no longer works. However, the upgrade went ahead without any error messages. **2. Describe your environment:** - OS Information: Ubuntu 22.04.5 LTS - Package Version: graylog-server/stable,now 7.1.4-1 amd64 mongodb-org/jammy/mongodb-org/7.0,now 7.0.37 amd64 opensearch/stable,now 2.19.5 amd64 - Service logs, configurations, and environment variables: These messages appear when the status is: **3. What steps have you already taken to try and solve the problem?** No changes after a reboot, and Apache2 is also running without any problems. Nevertheless, when I try to access the website, I get a “Service Unavailable” message. **4. How can the community help?** What could be the problem following the upgrade? Best regards ---
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 7:39am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/2 "2026-07-02T07:39:31Z")
`/usr/share/graylog-server/jvm/bin/java --version` `openjdk 21.0.11 2026-04-21 LTS` `OpenJDK Runtime Environment Temurin-21.0.11+10 (build 21.0.11+10-LTS)` `OpenJDK 64-Bit Server VM Temurin-21.0.11+10 (build 21.0.11+10-LTS, mixed mode, sharing)` The Java version should be fine and is included with Graylog Server anyway. But what should the permissions and ownership of the files be? I’ve read here and there that you need to adjust the ‘Owner:Group’ settings. ---
**Author:** ![Tdvorak](https://avatars.discourse-cdn.com/v4/letter/t/a88e57/32.png) [@Tdvorak](https://community.graylog.org/u/Tdvorak)\ **Post date:** [July 2, 2026, 7:46am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/3 "2026-07-02T07:46:49Z")
Could you please look at the server log and post it here, at least the full exception, which is visible partially in your _systemctl status graylog-server_ output? ---
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 8:05am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/4 "2026-07-02T08:05:43Z")
Where exactly can I find the log? ---
**Author:** ![Tdvorak](https://avatars.discourse-cdn.com/v4/letter/t/a88e57/32.png) [@Tdvorak](https://community.graylog.org/u/Tdvorak)\ **Post date:** [July 2, 2026, 8:23am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/5 "2026-07-02T08:23:27Z")
Usually, it’s this file: _/var/log/graylog-server/server.log_ ---
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 8:27am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/6 "2026-07-02T08:27:00Z")
[20260702\_server.pdf](https://community.graylog.org/uploads/short-url/mVNIXO102qK38XI5GsYR2NhpzxN.pdf) (685.7 KB) I had to turn it into a PDF. It’s only from 2 July 26. I did the update today; everything was working fine before that. ---
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 9:35am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/7 "2026-07-02T09:35:07Z")
[20260702\_server.pdf](https://community.graylog.org/uploads/short-url/a4kUVRp8pKrQpdAMlxzeP1PJwhz.pdf) (518.9 KB) I’ve just renamed the log file to .pdf. Once you’ve downloaded it, you can rename it back to .log, and it’ll probably be easier to read than the converted PDF. ---
**Author:** ![Tdvorak](https://avatars.discourse-cdn.com/v4/letter/t/a88e57/32.png) [@Tdvorak](https://community.graylog.org/u/Tdvorak)\ **Post date:** [July 2, 2026, 10:22am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/8 "2026-07-02T10:22:31Z")
You seem to be affected by this problem: [7.1 regression: server fails to start on noexec data dir (oshi/JNA UnsatisfiedLinkError) · Issue #26471 · Graylog2/graylog2-server · GitHub](https://github.com/Graylog2/graylog2-server/issues/26471) The recommended workaround is for now: Point Graylog’s native-library directory at an exec-capable location. Create one owned by the Graylog user: ` mkdir -p /opt/graylog/libnative/jna` ` chown -R graylog:graylog /opt/graylog/libnative` Add these to the GRAYLOG\_SERVER\_JAVA\_OPTS line in /etc/default/graylog-server (Debian/Ubuntu) or /etc/sysconfig/graylog-server (RHEL/RPM): ` -Djna.tmpdir=/opt/graylog/libnative/jna -Dio.netty.native.workdir=/opt/graylog/libnative` Then restart: ` systemctl restart graylog-server` Confirm your chosen path is not itself on a noexec mount `findmnt -T /opt/graylog` ---
**Author:** ![reni](https://avatars.discourse-cdn.com/v4/letter/r/a9adbd/32.png) [@reni](https://community.graylog.org/u/reni)\ **Post date:** [July 2, 2026, 10:39am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/9 "2026-07-02T10:39:40Z")
Yes 😀 Here is my addition: `#Fix nach Update-Problem - 20260702` `GRAYLOG_SERVER_JAVA_OPTS="$GRAYLOG_SERVER_JAVA_OPTS -Djna.tmpdir=/opt/graylog/libnative/jna -Dio.netty.native.workdir=/opt/graylog/libnative"` That helped, and Graylog is now working again. Thank you very much! ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [July 16, 2026, 10:40am UTC](https://community.graylog.org/t/graylog-no-longer-works-following-an-upgrade-to-graylog-server-7-1-4/37409/10 "2026-07-16T10:40:39Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.