Grafana lates stuck in activating

  • What Grafana version and what operating system are you using?
    CentOS 7 latest
    Version 9.4.7 (commit: 4add91f03d, branch: HEAD)

  • What are you trying to achieve?
    systemctl star grafana-server

  • How are you trying to achieve it?
    systemctl (re)start grafana-server

  • What happened?
    systemctl status stuck in activating.

  • What did you expect to happen?
    systemctl status active.

  • Can you copy/paste the configuration(s) that you are having problems with?
    I don’t think at the moment, is it configuration related. If you need anything, let me know.

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
    The following systemd message is logged periodically. Grafana process re-spawns, so process id changes each time. Additionally, there is MySQL message error also.
    Apr 9 11:44:28 localhost systemd: Got notification message from PID 3804, but reception only permitted for main PID 3803
    Apr 9 11:48:56 localhost mysqld: 2023-04-09 11:48:56 66 [Warning] Aborted connection 66 to db: ‘grafana’ user: ‘grafana’ host: ‘localhost’ (Got an error reading
    communication packets)

  • Did you follow any online instructions? If so, what is the URL?
    Not relevant.

Grafana visualization works, but depending on the exact time of the request (re-spawning), not all panels might be displayed.
I’d like to ask you, if there is any incompatibility between Grafana latest and CentOS7 systemd versions.

We hit a similar situation when we updated to the latest version of Grafana. I think there is an issue with the server process not forking correctly on startup. We ended up changing the systemd service type from notify to simple as a workaround. I tried installing an empty Grafana on a clean CentOS 7.9 machine and it installed with the notify type. The service started as expected so I think there might be an issue with the upgrade process.

1 Like

@chrisnpro welcome - and thanks for that additional detail, some nice hints in there about what might be going on. I’m going to check and see the appropriate team to see if we can get a look on this, appreciate the report from you and @bofh16 (classic username there :laughing:)

issue now filed as a bug in the grafana repo on GitHub, where we will track from there:

Is there a plan to fix this, please?

I’m not sure, what has changed, but the problem is not presented in:
Version 10.1.1 (commit: 0cfa76b22d, branch: HEAD)