TeslaLogger icon indicating copy to clipboard operation
TeslaLogger copied to clipboard

Synology upgrade unable to locate GrafinaDB

Open IMgoRt opened this issue 1 year ago • 4 comments

Following the usual update instructions, on the last step docker-compose up - d the following occurs

ERROR: for grafana Cannot start service grafana: Bind mount failed: '/volume1/docker/TeslaLogger/TeslaLogger/GrafanaDB' does not exists

Attempting chmod 777 TeslaLogger/GrafanaDB gives: chmod: cannot access 'TeslaLogger/GrafanaDB': No such file or directory

IMgoRt avatar Jul 01 '23 12:07 IMgoRt

The Problem is, you have to create it by yourself. An empty folder should do it. But why, I don't know. It should be automatically created as described in docker docs. https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

I'll try to check if there is another solution.

bassmaster187 avatar Jul 01 '23 23:07 bassmaster187

The Problem is, you have to create it by yourself. An empty folder should do it. But why, I don't know. It should be automatically created as described in docker docs. https://docs.docker.com/storage/bind-mounts/#differences-between--v-and---mount-behavior

I'll try to check if there is another solution.

Thanks, that fixed it, but it leads to this issue: https://github.com/bassmaster187/TeslaLogger/issues/1076

IMgoRt avatar Jul 02 '23 08:07 IMgoRt

creating a empty folder works for me too 👍 the GrafanaDB error disappear but now i have the issue with the #1076 and i think all my data are gone :-(

hagmann-sg avatar Oct 22 '23 07:10 hagmann-sg

Weird, doesn't work for me at all

Created the folder and did a chmod 777, still the same issue

adieball avatar Nov 16 '23 21:11 adieball