Same here Win 10 1.77.2.
Back to 1.76.2 or we have to wait.
Есть ли уже решение проблемы? Или пока что оставаться на 1.76.2?
Just for stats - my 2 my nodes running on Windows after update to v.1.77.2 ignore stop commands too (both GUI aka windows control panel and CLI - via CMD or PowerShell).
But there is some difference: I DO see log entry in storagenode.log then i try to stop it
INFO Stop/Shutdown request received.
But nothing more happens - node continues to work as usual ignoring stop request. No any additional errors. It just dont stop after getting and confirming request.
You do not need to do anything. Please wait for the auto update.
на русском
Вам не нужно ничего делать, пожалуйста, дождитесь автоматического обновления
Error 1023: The service did not respond to the start or control request in a timely fashion.
Had this issue on 3 nodes when preparing to reboot the PCs for a Windows 10 update. Storj and Nomachine are the only apps running on the PCs. Pcs are mostly idle.
Any fix?
Not now, but devs are aware of the issue and are trying to fix this.
See
As a workaround you could downgrade to 1.76.2
else you just have to wait.
Thanks for the quick reply. Since the node appears to be running fine after the reboot, I’ll wait for 1.77.4.
Обновил узел до версии 1.78.1 (для пробы). Проблема с остановкой службы никуда не исчезла. Служба не останавливается также как и на 1.77.2
@Alexey , что делать со всем этим? Новые версии выходят, а проблема не решена. Зазор от последней нормально работающей версии 1.76.2 - увеличивается
You may track this issue:
There is no gap, the rollout is stopped, the recommended version is still 1.76.2 and no new version is rolled out: https://version.storj.io/
на русском
Можете отслеживать баг на GitHub
Разница не увеличивается, обновление остановлено. Рекомендуемая версия 1.76.2: https://version.storj.io/
My Windows node running version 1.77.2 has been trying to update to version 1.78.2 for 24 hours but the storagenode-updater log shows timeout errors (due to the storagenode service not stopping).
To fix the issue I did the following:
- Force stop the storagenode.exe process
- Restart the storagenode-updater service
1 Like
That’s the damn “Die Hard” bug in storagenode win version.
2 Likes
Just to follow up … version 1.78.2 also does not allow the storage-node service to stop cleanly. I again had to force stop the storagenode.exe process when I changed config.yaml parameters.
same here. Please developers to deal with it, it hell problem, also to update need to do it manualy.
We are aware of this issue and already have a fix by @elek here: https://review.dev.storj.io/c/storj/storj/+/10347
3 Likes
Вижу, что проблема решена. Версия 1.78.3 работает хорошо. Спасибо
1 Like
v1.78.3 is under roll-out. This problem should be fixed from this version. Please let us know if you see similar problems with version >= v1.78.3.
And if you run Storagenode as a windows service, you may need to manually kill the process (or reboot) to be restarted (if you upgraded to any version between 1.77.0 and 1.78.3.)
3 Likes
Thanks. My node had been trying to update for 7 hours but was failing. I killed the process and let the updater run…
2023-05-11T10:29:01.621+0100 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.78.3"}
2023-05-11T10:29:01.621+0100 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T10:29:02.033+0100 INFO Current binary version {"Service": "storagenode", "Version": "v1.78.2"}
2023-05-11T10:29:02.034+0100 INFO Download started. {"From": "https://github.com/storj/storj/releases/download/v1.78.3/storagenode_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode_windows_amd64.336174633.zip"}
2023-05-11T10:29:03.185+0100 INFO Download finished. {"From": "https://github.com/storj/storj/releases/download/v1.78.3/storagenode_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode_windows_amd64.336174633.zip"}
2023-05-11T10:29:03.443+0100 INFO Restarting service. {"Service": "storagenode"}
2023-05-11T10:29:13.450+0100 ERROR Error updating service. {"Service": "storagenode", "error": "timeout", "errorVerbose": "timeout\n\tmain.serviceWaitForState:172\n\tmain.restartService:73\n\tmain.update:68\n\tmain.loopFunc:31\n\tstorj.io/common/sync2.(*Cycle).Run:99\n\tmain.cmdRun:136\n\tstorj.io/private/process.cleanup.func1.4:399\n\tstorj.io/private/process.cleanup.func1:417\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomOptions:113\n\tstorj.io/private/process.ExecWithCustomConfigAndLogger:79\n\tstorj.io/private/process.ExecWithCustomConfig:74\n\tstorj.io/private/process.Exec:64\n\tmain.(*service).Execute.func1:56\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}
...
2023-05-11T17:21:24.478+0100 INFO Running on version {"Service": "storagenode-updater", "Version": "v1.78.3"}
2023-05-11T17:21:24.478+0100 INFO Downloading versions. {"Server Address": "https://version.storj.io"}
2023-05-11T17:21:24.902+0100 INFO Current binary version {"Service": "storagenode", "Version": "v1.78.2"}
2023-05-11T17:21:24.902+0100 INFO Download started. {"From": "https://github.com/storj/storj/releases/download/v1.78.3/storagenode_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode_windows_amd64.279935294.zip"}
2023-05-11T17:21:25.922+0100 INFO Download finished. {"From": "https://github.com/storj/storj/releases/download/v1.78.3/storagenode_windows_amd64.zip", "To": "C:\\WINDOWS\\TEMP\\storagenode_windows_amd64.279935294.zip"}
2023-05-11T17:21:26.138+0100 INFO Restarting service. {"Service": "storagenode"}
2023-05-11T17:21:26.178+0100 INFO Service restarted successfully. {"Service": "storagenode"}
2023-05-11T17:21:26.265+0100 INFO Current binary version {"Service": "storagenode-updater", "Version": "v1.78.3"}
2023-05-11T17:21:26.265+0100 INFO Version is up to date {"Service": "storagenode-updater"}
Edit - I can confirm the storagenode service now cleanly restarts.
1 Like