There is an empty cell in the audit column for each node’s summary line.
I think something like this would fit there:
V: 1.109.2 - UT: 129h 45m
or
1.109.2 - 129h 45m
Request for your next update. Please pull console port from config.yaml per node. For example: audit reports as shown above, are not possible, if node ports are not sequential from 14002. Additionally Main GUI will not properly display actual ports in use per node, it only assumes.
Great stuff btw, your app is appreciated.
@Vadim
Since you are an expert Windows StorJ node operator, do you have an idea how can I solve the following situation?
I have an old Windows 8.1 PC with 4HDD and 4 working nodes and I would like to move these nodes to a different Windows 11 PC.
I would like to take off the HDDs from the old PC and put them into the new one.
Is there a way to “import” the nodes on the new PC?
I understand that I need to adjust the paths in the config files, but how can I add the nodes as service (also the updater for the first node, but this is not so crucial)?
When I moved to other pc my nodes, I just installed them from 0 first node without HDD with same identities, then added other with toolbox. Then just changed conf files of installed with old. Then Add HDD and move DBs, and check that all paths are OK in conf according to new pc. Also dont forget pc firewall to open ports. Do not start nodes before all done, because it will start audit and pool new data. If you put Hdds and DBs before instal it can rewrite something during install. or just install Data and DBs to temperary folder, then when you replace config and fix paths.
1 Like
The first node would start automatically after install, so you may use a wrong temp identity (with not enough difficulty or unsigned and the temp data path) or disable the rule on the router/firewall to deny connections to the node. When all paths and data will be in place - update the config and restart the node, then you may enable the router/firewall rule to allow connections to your node.
2 Likes
Hello , some help. I do run the node toolbox for a couple of months and its great, really without any serious problem. In windows 11 and 3 nodes+ 1 main node.
The only problem i would like to resolve is the auto update. I need to do manual update to the nodes form the main node but some times i forget and my nodes go offline because of non accepted version (old).
Is there any way to auto-update the nodes?
thank you!
I am in process of renew of installer of my auto updater, it update automatically every node on pc. and check updates every 20-72h.
It is separate app working as service. On other hand you just gave me idea, to not make separate installer, but add to toolbox install button. then all will be in one place.
3 Likes
Unfortunately if the version is old and stop working the updater in your app is not updating at all. It updates only online nodes and not offline.
My solution to this is just copy the storagenode.exe from the main node to the folders of the other nodes and thats it. So if you want to add an autoupdater included just make it copy the “storagenode.exe” every day from the main node to the secondary.
You may also try to install a storagenode-updater for each node:
1 Like
it not possible if node is running. first need to stop node, I think about it how to make it better.
1 Like
Release ToolBox · TonyTosol/Storj-Node-Toolbox (github.com)
Now you can try.
It add updater service, that will update all nodes on this pc automaticly.
5 Likes
I installed the new version with the updater…Great news. Finally i wont have to update manually every week…
THANK YOU Vadim!!!
Just first wanted to say you are a lifesaver for making and maintaining this tool. However, I am trying to use the new version to update my nodes. When I start the service, it just turns of the first non-main node and stops.
I then used the previous version, started the stopped node (it started okay), pressed update manually and it worked fine so it seems like there is some issue with the auto updater.
Let me know if there’s any logs or something else I can provide to help troubleshoot this
How long did you waited? It checks that node service stop up to 400s
because nodes some times stops very long time, it started from 1.10 version mostly.
Also if node stopped and not updating, you can restart update service, it will update even if it off.
I waited a few minutes, definitely not 400 seconds though. Since I already updated my nodes I won’t be able to test it, but when the new version hits my nodes I will give it another shot!
I had the same problem and had to manually update and start the node. Then I went back to the previous version. As other users said, Thanks Vadim for maintaining this software. I use it regularly.
Me too…the new updater doesn.t work. My nodes went offline. I restarted them and stop - start the updater but again the updater stoped the nodes without update them and remain stopped in old version.
I think it needs a fix!
60% of the time it works ALL the time -Ohhh yeah!
Would you like to help to solve the issue?
1 Like