You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had this successfully running on my Synology previously, but re-initialized the volume and cannot get it to work again. When following the directions on this repo I get the following logs from supervisord ad infinitum.
2022-12-20 04:11:10,233 INFO spawned: 'grafana' with pid 5185
2022-12-20 04:11:11,256 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-12-20 04:11:11,731 INFO exited: grafana (exit status 1; not expected)
2022-12-20 04:11:11,731 INFO reaped unknown pid 5196
2022-12-20 04:11:11,733 INFO spawned: 'grafana' with pid 5205
2022-12-20 04:11:12,756 INFO success: grafana entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-12-20 04:11:12,757 INFO reaped unknown pid 5216
2022-12-20 04:11:12,767 INFO exited: grafana (exit status 1; not expected)
Looking in the grafana log I see complaints about the database being locked initially:
I had this successfully running on my Synology previously, but re-initialized the volume and cannot get it to work again. When following the directions on this repo I get the following logs from supervisord ad infinitum.
Looking in the grafana log I see complaints about the database being locked initially:
This lasts about 5 minutes, after which it no longer complains, but gets stuck in a loop without any apparent errors:
Owner of /var/lib/grafana is grafana:grafana. The telegraf service is running, but reporting errors writing to influxdb.
Any idea what's happening? This was tested with the same result both on latest and develop.
The text was updated successfully, but these errors were encountered: