Just killed my last VPS. All in on Home Nodes now. 
13 Likes
Are you a Sloth?!
5 Likes
It would be really helpful if you could tell us how it was trained. I asked that question in the thread yesterday.
4 Likes
That’s the best gif Google would provide for Zen
4 Likes
Its getting 
in here.
Poor planning guys lets do node wars in winter next time! 
Legit thinking about turning some machines off!
First world problems.
3 Likes
But it is winter, what ya talking about.
8 Likes
Today I was restarting the nodes and one failed to start with this message:
Failed to start 1 service(s):
✕ safenode3: Could not connect to RPC endpoint 'https://127.0.0.1:60059'
Error:
0: Failed to start one or more services
Location:
sn_node_manager\src\cmd\node.rs:754
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
What could be the cause?
After that, I used the command to run nodes again and that node started working:
╔═════════════════════════════╗
║ Start Safenode Services ║
╚═════════════════════════════╝
Refreshing the node registry...
The safenode1 service is already running
The safenode2 service is already running
Attempting to start safenode3...
✓ Started safenode3 service
- PID: 10188
- Bin path: E:\safenode3\safenode.exe
- Data path: E:\safenode3
- Logs path: E:\safenode3
No Safe, no wave.
can you not get little Stirling engines on your systems to power your AC ?
2 Likes
I’m hoping Maidsafe solve the problem for me with 20GB nodes. I’ll be able to pawn some of my equipment then 
3 Likes
Yea it would decrease the node count in the node Olympics 
1 Like
Yesterday I think I discovered the problem of no earnings for my nodes. When I walked away from the computer, it went into a dormant state and despite the Internet being on, the nodes probably stopped working because I checked the data transfer usage status and it was almost at the same level as when I walked away from the computer.
The conclusion is that the nodes stop working, should this be the case, Is it a matter of settings in safenode-manager?
It depends what you mean by “dormant”. If the computer is sleeping, it will be in a state where it is almost switched off, and the node services will not be running. If you really want to leave the nodes running for an extended period of time, you would need to adjust your OS power settings so that the machine doesn’t go to sleep. Powering off the display should be fine, but it can’t go to sleep if you want to leave the nodes running.
2 Likes
So, running for 24hr this is about the best consistent uptime I have had. Generally speaking I feel there is a lot wrong here. The sheer number of connections per node seems to be the issue. This is on a box that can handle a lot more than what is running. Network hardware is enterprise grade, unsure whats choking this. any advice would be good. Even with these numbers I still cant get even 30 nodes running.
1 Like
Sorry, I misspoke, the computer has two positions: off and sleep. In this case, due to lack of movement, the computer went into “sleep” mode, i.e. it was not “off”, but the screen turned off. Should the nodes work then?
There was a discussion about this during early testing, and so I was convinced that if the computer was in “sleep” mode but powered on, the nodes should running.
When only the display is switched off, the computer isn’t sleeping. They are different things.
In the sleeping state, the machine is not completely switched off, but it goes into a very low power mode. In that low power state, mostly everything gets switched off (including the nodes) and critical OS state remains in RAM so that it can be recovered quickly and resume from where it left off.
If you want the nodes to remain running, you have to tell Windows to not go to sleep. You can have it power off the display, that’s fine, but the nodes will not run while the computer is sleeping. The operating system’s power management settings should distinguish between sleep and the display being powered off.
3 Likes
In Windows, there is a setting option “power and sleep”:
- for the screen power from battery / mains - here the screen can be extinguished,
- for sleep power from battery / mains - here there is a “never” option to be selected,
Is this how they should be set up, do I understand correctly?
You may have configuration or networking problem - connections are being dropped or not established correctly, that is why you are seeing so many of them but also zeros. How your network topology looks like and what parameters you used when you added nodes?
Which makes me ask @chriso, is it normal that on one location I have 300 peers per node on average and second location has only 80 peers per node on average? Everything looks running fine and stable, but the difference doesn’t make much sense to me. Only difference is first location is behind NAT with manual port forwarding, second location sits directly on public IP.
Sorry, but I would need to call on @qi_ma for this question.
Yeah, it’s the second of those. You want to prevent the machine from sleeping. Screen power off is fine.
1 Like
Thanks for your help. I think it would be useful to make a manual for testers who may be looking for the cause of the lack of income for the same reason, they don’t know that the computer in “sleep” state disconnects the nodes and then goes back to work when the computer is woken up, but the test subject may not know this.
3 Likes