Is it possible to stop the auto update with the docker images? I keep having downtime due to the upgrade hanging (caused by a funky firewall that i cant control).
I’d much rather schedule my upgrades when it suits me. I’ve gone from 100% to 94% on some node with this last week of updates and the US nodes offline issue…
Hi @ShareIT, I came across the following configuration parameter, which might help you:
I had seen that and tried “disable” but it stops the node from starting with a error of “version cannot be NULL”.
Once seems to allow it to start, but have no idea what “once” actually means/does.
Dev’s?
const (
checkerModeOnce Mode = "once" // run the version checker once
checkerModePeriodic Mode = "periodic" // run the version checker periodically
checkerModeDisable Mode = "disable" // disable the version checker
)
I guess ‘once’ means only check for updates when the node starts.
Yeah, that’s what I thought, but the nodes were still coming up on v1.121.2 instead of 1.122.1.
I’ve since noticed that the git repo still has 1.121.2 tagged as the “latest”, which would explain why the other nodes aren’t updating.
They’re all set to once, and I’ll keep an eye on the repo. Once 122 goes latest, I’ll restart and see.
Thanks!
In the config you can change the version link from https://version.storj.io/ to you own. I think this could work
Good shout. I was going to just block https(443)
The “Once” didn’t work. just got notice of 2 nodes down. Grrrrr
Can you not get around the firewall with a workaround? Like a proxy or something else? I personally would prefer to get the auto update to work than have to manually check and update them every time
Going to bump this back up as I’ve just had another 3 nodes go down today. One node is running at 92% uptime now, thanks to the “helpful” auto updates. It’s been fine since my last post but now… 3 nodes down.
No, I can’t fix the firewall - it’s out of my control, and access to certain sites (including Git) are blocked. I simply want to be able to run an update script once the new “latest” release is available.
Part of my existing process, which had worked for months, was to check for a new latest; once one is available, a script runs that fires up a VPN, updates the node, stops the VPN and restarts the container. I’d like to have that control again.
As it stands, the auto update runs, tries to download a new version and the update hangs indefinitely (until I fire up the VPN, complete the update and restart)
Is this possible? “Once” didn’t stop it. “Disabled” stopped the node starting, and periodically is the default which breaks it anyway.
Have you tried increasing the time for –version.check-interval ?
Then only this way could help:
version-check-interval parameter can be used. I don’t know if it has a maximum limit. I just keep it to 4h. I used to have it set at 24h. You could set it to 999h and watch the logs if it checks sooner. This would be my workaround, cause I don’t know how to set up a local website, to replace the official one.
I would try it a different way. Not stopping Auto updates.
I would try to mirror https://version.storj.io/ to a localhost webserver. Then change the download url from the git one to the localhost server.
Then I would set up a script that checks at a fixed interval for changes and pulls them to the mirror (with the changed link to the file)
If a new version appears the pull the new file from git with an Http Proxy (there are enough free ones around that should work for this or you can setup your own on a different server. Or you could just download it from git to the server with access and then download it again from server to server)
Then change the config URL to localhost that should be enough to work.
I know that you can setup a http proxy for docker directly ( Proxy configuration | Docker Docs ) but I don’t know if the storage node would use it or if it even has the possibility to set a http proxy