I just had a uptime monitor alert to say the node has gone offline, I checked docker and sure enough the docker was off, I manually restarted it an noticed it has updated to v1.71.2.
What normally happens to other dockers is it states there is an update so i can manually do this, but for Storj this isn’t the case, it seems to auto update on its own accord but shuts the docker down and doesn’t restart it.
This not ideal as if it happened at say 12am when i am sleeping i would not know it was offline until the morning which would mean 7 hrs of downtime
How do i make sure the Storj docker doesn’t auto update like this? or fix it so it auto restarts?
Right now, in Unraid, i have in the Extra Paremeters bit: “–mount type=bind,source=”/mnt/disks/Storj_Node_1/storj-certs/identity/storagenode/“,destination=/app/identity --mount type=bind,source=”/mnt/disks/Storj_Node_1/storj/“,destination=/app/config”
shall I add --restart unless-stopped at the end of this?
I also may add this happened on the previous update too for me, i thought it was a one off, until this one didnt auto start as well.
Is there anyway we can get a heads up on updates? so we can be ready for it?
Well, LittleSkunk will post up the release notes just before release. However, releases are staggered so you might not get it right away when it first goes out, and may get it sometime later in the week depending on where you fall in the release schedule.
You may want to investigate a way to monitor whether your nodes are online or not and receive notification when they go offline.
I had this happen last night, two nodes updated to 1.71.2 at 4:30am and didnt restart. Just noticed and restarted them now. Not sure how monitoring helps in the middle of the night. This doesnt happen all the time so it cant be a docker config issue, right? All my nodes are restart unless-stopped.
If you did not redirect them to the file, they are lost when the container is recreated.
However, if you did not remove the container and just started, then they probably should be still there
docker logs storagenode
you may use option --since to provide a start date and time, see
docker logs --help
And stopped container means that --restart policy is not specified, so you need to add --restart unless-stopped to your docker run command. I can guess, but you likely uses the Community storagenode application for UnRaid and looks like it doesn’t include this parameter.
It happened few times also on my nodes, first time I saw that on version ~1.68. Not sure what triggers this. I am now trying “–restart always” policy, but I am not sure about disadvantages, so I don’t recommend.
From docker docs it looks like, restart policy is reset, when you do manual “docker stop container” and then manual docker start.