Start failed on Synology VM Debian (bullseye) x86-64

Grafana Installation
1

Hi
I have running debain bullseye on my Synology-VMM.

**hostnamectl**
**   Static hostname: raspberry**
**         Icon name: computer-vm**
**           Chassis: vm**
**        Machine ID: 5f6f92fe44e049d596a066d3bfb87649**
**           Boot ID: 5127ed08d94f4f88bb883515dcc1e0e9**
**    Virtualization: microsoft**
**  Operating System: Debian GNU/Linux 11 (bullseye)**
**            Kernel: Linux 5.10.0-30-amd64**
**      Architecture: x86-64**
-------------------

And I was truing to install grafan on it. I used the last version from here [Installation from Webpage](https://grafana.com/docs/grafana/latest/setup-grafana/installation/debian/)

But I have still the same issue:
-------------------
sudo systemctl status grafana-server
● grafana-server.service - Grafana instance
     Loaded: loaded (/lib/systemd/system/grafana-server.service; enabled; vendo>
     Active: failed (Result: signal) since Thu 2024-06-13 14:06:31 CEST; 1min 2>
       Docs: http://docs.grafana.org
    Process: 980 ExecStart=/usr/share/grafana/bin/grafana server --config=${CON>
   Main PID: 980 (code=killed, signal=SYS)
        CPU: 115ms

Jun 13 14:06:31 raspberry systemd[1]: grafana-server.service: Scheduled restart>
Jun 13 14:06:31 raspberry systemd[1]: Stopped Grafana instance.
Jun 13 14:06:31 raspberry systemd[1]: grafana-server.service: Start request rep>
Jun 13 14:06:31 raspberry systemd[1]: grafana-server.service: Failed with resul>
Jun 13 14:06:31 raspberry systemd[1]: Failed to start Grafana instance.

Maybe someone can help me. Thanks.

2
3

Hi, just tested:

journalctl -u grafana-server
-- Journal begins at Sat 2024-04-27 04:52:57 CEST, ends at Thu 2024-06-13 21:21:30 CEST. --
Jun 11 09:38:27 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:38:27 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:38:27 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:27 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 1.
Jun 11 09:38:27 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:38:27 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:38:27 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:38:27 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 2.
Jun 11 09:38:28 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:38:28 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 3.
Jun 11 09:38:28 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:38:28 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:38:28 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 4.
Jun 11 09:38:29 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:38:29 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 5.
Jun 11 09:38:29 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Start request repeated too quickly.
Jun 11 09:38:29 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:38:29 raspberry systemd[1]: Failed to start Grafana instance.
Jun 11 09:41:49 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:41:49 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:41:49 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:41:50 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 1.
Jun 11 09:41:50 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:41:50 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:41:50 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
Jun 11 09:41:50 raspberry systemd[1]: grafana-server.service: Failed with result 'signal'.
Jun 11 09:41:50 raspberry systemd[1]: grafana-server.service: Scheduled restart job, restart counter is at 2.
Jun 11 09:41:50 raspberry systemd[1]: Stopped Grafana instance.
Jun 11 09:41:50 raspberry systemd[1]: Started Grafana instance.
Jun 11 09:41:50 raspberry systemd[1]: grafana-server.service: Main process exited, code=killed, status=31/SYS
4

Please use formatting for logs. I bet some security rule is blocking Grafana:
journalctl _AUDIT_TYPE_NAME=SECCOMP
Or watch full logs (be familiar with journalctl command) for details and find correlations.

5

What I have now to do? Iám not profesional on it