Has anyone earned?
I have had 6 nodes running for about 20 hrs and no earnings at all. Is this expected at the moment?
Below is a screenshot that has on the upper edge the current situation and below that is a screenshot from yesterday.
I run these from home, from Ubuntu laptop.
Connection mode: Automatic
Port range: Auto
5 nodes, earned 1 atto since the update.
5 nodes and 3 attos. It looks like attos are being earned based off the blockchain explorer though.
4 nodes running for about a day have yielded 1 payment for me:
Computer 1
Network A
3 Nodes
Win10
Home-network mode
Port forward
Computer 2
Network B
1 Node
Win10
Home-network mode
No port forward
The solution is for launchpad to do as safenode-manager and upgrade one node and restart it immediately then move onto the next. If safenode-manager kills all at once then restarts then it should do it one at a time as well
This way the time is in terms of a minute or two which should not see it shunned by any other node.
Temp shunning is another attack vector. In blackout situations or long term stoppage then the node should know from its logs it was stopped for a long time and use the old secret_key to decode its record_store and restart with new secret_key for a new peer_id and re-encode its record_store while offering up its records.
It doesn’t work like that. If you redirected ports in the router and did not set them in the LP, it does not know that there are redirected ports and uses random ones.
Check out the Dev Forum
The launchpad performs the upgrade in the same way as safenode-manager. At least as far as I’m aware.
I was pretty sure safenode-manager did the upgrade one node at a time, restarting the node in the process (stop, upgrade, start for each node in turn).
Is that not the case?
Yeah, they are both processing one node at a time. I don’t see where the difference is?
Its in the quote I quoted. Launchpad leaves the nodes stopped and the user has to start all the nodes again with ctrl+s
And you seemed to be saying the safenode-manager is leaving them started since that’d be the way to process one at a time since the node program is sitting in the .local/bin directory and just download new version sitting it there.
Or are you saying safenode-manager also leaves the nodes stopped and the user has to do a safenode-manager start command again
Leaving them stopped was changed, so I am pretty sure that description is outdated now. But, even if they were left stopped, they are still being processed for upgrade one at a time, in sequence.
As far as you know both launchpad and safenode-manager start the nodes again for the user, or have I read what you are saying wrong?
The issue above was not the processing one at a time but the potential length of time they are left stopped which the OP suggested launchpad does.
Yeah, as far as I’m aware, they do now. So the description is outdated. We discussed changing it on a call we had before we released the latest version.
Edit: the node manager always did this, but for some reason the launchpad opted to leave them stopped. It was the behaviour of the launchpad that changed.
