Great script. Extremely helpfull. One thing Jonh... have you noticed that the lastest versions (3 and above) require you to restart the nodes to get the rewards JSON exported correctly? If the evenstream has rewards info from the previous epoch and the current one, because the node wasn't restarted since the epoch changed, the JSON comes incomplete.
3.00 and 3.02 have this behaviour ... 3.03 I'll only be able to check next epoch. In this epoch I have 9 layers with rewards and v3.02 was only showing 4 of them... if I ran v.2 it would show and export the 9 layers. After I restarted all the nodes, all versions show and export the 9 layers correctly.
i checked and i still have a node with previous epoch layers, but json comes out correct with only this epoch layer. im unable to recreate error. Are you in latest spacemesh version?
Yes... all my 12 nodes are running the latest version (v1.3.11) since the day it came out. Take notice that I'm mentioning the JSON export, but also it didn't show the number 1 in the RWD column for the nodes I hadn't restarted.
Thank you for posting this video. But I found this very confusing. You mentioned at 1:57 that "you may have to copy this to snap", but didn't give an example of where to copy. The ports in config files are 8083..8085, but the port in monitor is 9012. I tried to follow the video, but cann't take the monitor work, and it makes me wonder if it's the monitor settings, to the node that's not working. Please help!
Smapp uses by default ports 9092 and 9093, if you changed this then there's nothing else to copy. Just point the monitor to those ports. Please note that smapp won't allow remote connection to port 9093 or equivalent. Not sure if they fixed this yet.
Thank you, sir! Would really recommend using json instead on .ps1 files to add objects like ports. $configFile = Get-Content -Path '\path\to\file.json' | ConvertFrom-Json
That json file can serve everything you're doing. You can add all the node data in that file and always retrieve it from there - basically it can act like a database, and it's just one file which you can even keep on a network, instead of local.
Thanks for the suggestion. It's actually on the list.it will make updates easier. As for restarting node it's a bad idea. If node stopped it's because there's a problem and won't fix by itself. I did though about it first, same thing we had with GPU miners. But nodes it's a bit different.
Fantastic Jonh!
You are a legend, glad you provide windows users salvation!
Great script. Extremely helpfull.
One thing Jonh... have you noticed that the lastest versions (3 and above) require you to restart the nodes to get the rewards JSON exported correctly?
If the evenstream has rewards info from the previous epoch and the current one, because the node wasn't restarted since the epoch changed, the JSON comes incomplete.
I haven't experienced this. But we did restrict GRPC readings on V3.0.2
3.00 and 3.02 have this behaviour ... 3.03 I'll only be able to check next epoch.
In this epoch I have 9 layers with rewards and v3.02 was only showing 4 of them... if I ran v.2 it would show and export the 9 layers.
After I restarted all the nodes, all versions show and export the 9 layers correctly.
@@hcdigital504 thx for reporting. I will take a look.
i checked and i still have a node with previous epoch layers, but json comes out correct with only this epoch layer. im unable to recreate error. Are you in latest spacemesh version?
Yes... all my 12 nodes are running the latest version (v1.3.11) since the day it came out.
Take notice that I'm mentioning the JSON export, but also it didn't show the number 1 in the RWD column for the nodes I hadn't restarted.
Is there a guide to help me figure out how many 2 TiB nodes I can run on a 3900X with raid 0 2x12TB HDD's
Sadly no.
This is awesome! Thx
Thank you for posting this video. But I found this very confusing. You mentioned at 1:57 that "you may have to copy this to snap", but didn't give an example of where to copy. The ports in config files are 8083..8085, but the port in monitor is 9012. I tried to follow the video, but cann't take the monitor work, and it makes me wonder if it's the monitor settings, to the node that's not working. Please help!
Smapp uses by default ports 9092 and 9093, if you changed this then there's nothing else to copy. Just point the monitor to those ports.
Please note that smapp won't allow remote connection to port 9093 or equivalent. Not sure if they fixed this yet.
Hi thanks for the educational videos ! I’m curious how much smh did u get for mining?
Hi, at the moment, 1TB gives about 40-60 SMH /m
Thank you, sir!
Would really recommend using json instead on .ps1 files to add objects like ports. $configFile = Get-Content -Path '\path\to\file.json' | ConvertFrom-Json
That json file can serve everything you're doing. You can add all the node data in that file and always retrieve it from there - basically it can act like a database, and it's just one file which you can even keep on a network, instead of local.
Would be nice if instead of sending an email, you just/also restart the node through cli
Thanks for the suggestion. It's actually on the list.it will make updates easier.
As for restarting node it's a bad idea. If node stopped it's because there's a problem and won't fix by itself.
I did though about it first, same thing we had with GPU miners. But nodes it's a bit different.
Hi, in the future will the monitor also have a SME eligibilities tab?
Already doing that. Check latest version updated today.
Will make a video soon as there's another cool feature I need to explain
@@minerondemand Thanx, got it. Maybe just an idea would be to show the layer numbers.
Can I find port1 and port2 of each node in the config file?
Need more info about your problem.
@@minerondemand I'm wondering about port 1 and port 2 of each node, where can I find it in the config file. for example listener port 9092 etc
i actually show that at 1:27 if you are using conig-mainnet.json @@thinvivu3811
another one...