Grafana fails to start after Hass OS upgrade to 5.8 - problem with plugin: grafana-image-renderer

[southseaboy]

Problem/Motivation

I cannot used the add-on currently. My environment is using a Home Assistant virtual appliance on Intel hardware (proxmox hypervisor). The original image used was from June 2020, since then core, supervisor and OS have been upgraded in place using the controls provided within the UI.

This morning I upgraded the OS to 5.8 and all except Grafana seems to be working OK (including Node-Red, Visual Studio, MariaDB and others).

I am still using HA Core 0.118.

Expected behavior

Add-on should start & run

Actual behavior

Add-on attempts to start, but terminates during start sequence - the major error appears to be:

t=2020-12-15T11:59:10+0000 lvl=eror msg="Stopped RenderingService" logger=server reason="Failed to start renderer plugin: timeout while waiting for plugin to start"

This appears to be related to the plugin grafana-image-renderer, which I believe is part of the add-on configuration as I get the same error even if I remove the additional plugins that I use.

Please see full log attached below..

Steps to reproduce

The add-on fails to start when manually triggered, or following a complete reboot of the virtual appliance.

My grafana config:

plugins:
  - grafana-clock-panel
  - natel-discrete-panel
  - grafana-piechart-panel
env_vars: []
ssl: true
certfile: fullchain.pem
keyfile: privkey.pem
log_level: info

Grafana log

grafana_addon_log.txt

System Health Info:

system_health_info.txt

Please let me know if there is any other information I can provide. Many thanks for this and your other really useful add-ons. Chris

[southseaboy]

OK its me - well at least my config somehow. Further investigation - I've spun up a new instance of HA using the latest OVA, and imported a snapshot of the Grafana add-on with my dashboards only (nothing else from my HA install). Grafana and all my dashboards come up fine (the influxdb datasource I use is external to HA). It may be that something in the update from HassOS 4.whatever to 5.8 didn't work properly, but because I'm using a VM it's and easy work-around. I shall restore a full snapshot and if that works will close the issue.

[github-actions[bot]]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!