Server start failure after 9.2.1 upgrade on Raspberry PI 3B

Hello everyone, after upgrading from 9.2.0 to 9.2.1 grafana-server fails to start on Raspberry Pi 3B.

Oct 22 10:21:07 pi3B systemd[1]: /lib/systemd/system/grafana-server.service:35: Unknown lvalue 'RestrictSUIDSGID' in section 'Service', ignoring
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 1.
Oct 22 10:21:08 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:08 pi3B systemd[1]: Started Grafana instance.
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Main process exited, code=killed, status=11/SEGV
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 2.
Oct 22 10:21:08 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:08 pi3B systemd[1]: Started Grafana instance.
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Main process exited, code=killed, status=11/SEGV
Oct 22 10:21:08 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 3.
Oct 22 10:21:09 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:09 pi3B systemd[1]: Started Grafana instance.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Main process exited, code=killed, status=11/SEGV
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 4.
Oct 22 10:21:09 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:09 pi3B systemd[1]: Started Grafana instance.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Main process exited, code=killed, status=11/SEGV
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:09 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 5.
Oct 22 10:21:09 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:10 pi3B systemd[1]: Started Grafana instance.
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Main process exited, code=killed, status=11/SEGV
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Service RestartSec=100ms expired, scheduling restart.
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 6.
Oct 22 10:21:10 pi3B systemd[1]: Stopped Grafana instance.
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Start request repeated too quickly.
Oct 22 10:21:10 pi3B systemd[1]: grafana-server.service: Failed with result 'signal'.
Oct 22 10:21:10 pi3B systemd[1]: Failed to start Grafana instance.

Executing grafana-server results in “Memory-Error” .
A complete uninstall/reinstall did not help, downgrading (to 9.2.0) fixes the issue but I assume an issue for 9.2.1 on PI 3B .

Linux pi3B 5.15.41-v7+ #1557 SMP Mon May 23 16:46:23 BST 2022 armv7l GNU/Linux “(10 (buster)”

Hi @schlaubstar,

Thanks for opening this post.

What happens if you directly call the grafana-server command in the terminal?

And what is the output of the command apt policy grafana

Lastly, Can you please check if there is sufficient disk and memory space avail on the device (because a Memory error could be an indication of OOM).