I can confirm that one of my nodes failed to restart after updating to 1.21.2
1 Like
Same here, yes. It failed to start after the upgrade.
1 Like
Thank you for reporting such issue. We are going to update the documentation to instruct users to set their configuration to Restart=always.
5 Likes
what’s the link to the latest documentation please?
1 Like
I would pay more attention to a potentially critical bug, abnormal memory consumption of “systemd-journal”:
Yesterday:
Today:
I still working on determining the root cause and preventing it, will post a solution soon ™
PS. you can check memory consumption on your side with:
ps -A --sort -rss -o comm,pmem,rss | head -n 20
2 Likes
PSA: the v1.22.2 ARM binary zip file appears to have two files in it, causing the following error during the update.
2021-02-17T14:25:53.336-0700 ERROR Error updating service. {"Service": "storagenode", "error": "archive should contain only one file", "errorVerbose": "archive should contain only one file\n\tmain.unpackBinary:94\n\tmain.downloadBinary:61\n\tmain.update:44\n\tmain.loopFunc:
26\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tmain.cmdRun:126\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/spf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/
private/process.Exec:65\n\tmain.main:11\n\truntime.main:204"}
The zip file for the AMD64 binary does not have this issue:
The __MACOSX folder is likely tripping up the updater service.
I’ve manually updated my ARM node for this version.
3 Likes
@littleskunk anyone know if there’s an installer yet? Sorry to sound like a broken record but ive finally got my internet connection at the new house and I’m ready to setup all my nodes again after running GE last year.
Also, if there’s no installer, should I setup my new production nodes using this? Is this production ready?
Any issues playing it safe and setting my new nodes up with docker? Will the new Multi-node Dashboard work with docker setup?
Cheers
@will.topping, for what it’s worth, I’ve been using this since v1.15.3 and it’s been equally stable as the Docker nodes. I know a .deb or something is preferable, but the installation isn’t too onerous. As linked by @ACarneiro last month, I’ll pat myself on the back for the following instructions. A couple binary downloads, creating a dedicated user, and a couple systemd service files and it’ll be up and running. Perhaps something to hold you over until an installer is released.
2 Likes
Thanks @fmoledina I just spotted your post in the other thread and think I’m gonna give it a go and hope for the best! I may be back with questions 
So my Linux node hasn’t updated to the latest version.
Having had a look at my logs, I get the following error:
Feb 19 18:11:27 Juno storagenode-updater[31170]: 2021-02-19T18:11:27.258Z ERROR Error updating service. {“Service”: “storagenode”, “error”: “archive should contain only one file”, “er
rorVerbose”: “archive should contain only one file\n\tmain.unpackBinary:94\n\tmain.downloadBinary:61\n\tmain.update:44\n\tmain.loopFunc:26\n\tstorj.io/common/sync2.(*Cycle).Run:152\n\tmain.cmdRun:126\n\ts
torj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:842\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:950\n\tgithub.com/s
pf13/cobra.(*Command).Execute:887\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.main:11\n\truntime.main:204”}
Any thoughts on what is wrong and what I can do to fix it?
I really need to start opening my eyes… 
So presumably this is not something I can fix, I just have to wait until it’s fixed server side?
You need to download the archive manually from the releases page on Github and install it just like you would have done the very first time. It won’t update automatically as it won’t be able to get past the multiple files error shown.
Meh… 
I’ll wait for the next version to be out. It’ll be no problem being one or two releases behind… 
Well being 2 releases behind would be a problem as you would stop receiving data.
And being 3 releases behind would get you disqualified.
So, keep a sharp eye on versions, still ^^
See:
Ah, thanks. In my mind it was OK up to 2 and stop receiving data at 3.
It’s very irritating that the Linux updater isn’t working, especially when the fix is so bloody trivial!
@littleskunk Can you please remove the rogue _MacOSX folder and put it somewhere else so the Linux updater can work again?
2 Likes
I hope that the v1.24.4 release fixes this. It is currently being rolled out.
3 Likes
