Vasyl Tretiakov
@blacks1
70 Following
11 Followers
Casts
Casts + replies
Vasyl Tretiakov
@blacks1
@cassie could this duplicate BlockNumber property be a typo? http://quilibrium.com/docs/operatingsystem/filesystem
0 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
Based on my observations, every ~2 days the node gets struck with leader frame polling and needs to be restarted. I'm not sure if it's the bandwidth bottleneck (I should have 100 Mbps) or the hardware (the specs seem to meet minimum requirements).
1 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
Ryzen 5800 @ 3.2/4.4 GHz (8 cores/16 threads), 16 GB DDR4 @ 3200 MHz, 1 TB NVMe SSD. But I haven't earned anything yet after around a week of experiments, ~2 days of direct internet connection :)
1 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
Correction, the leader frames are not incrementing since the morning. So it seems like the node is stuck, but without health check guidance I can't be sure. A node restart could mean another day of connecting to the peers...
1 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
It's annoying to me too. I'm working via mobile data :)
1 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
Attempts to put the machine in DMZ or configure port forwarding didn't seem to make the node work well. I did manage to get the node sync behind NAT/firewall. As that takes over a day, it could be worthy to proceed with that, I guess. If 1.4.18 fixes the challenges of working from behind NAT/firewall, that's great.
0 reply
0 recast
0 reaction
Vasyl Tretiakov
@blacks1
I think I got it working from home (any node health validation checks are welcome) by plugging the internet provider's cable directly into the node machine. The problem with working from behind NAT/firewall seems to be at least the node listening on UDP port 8336. Leader frames are incrementing, peer count is 84001.
2 replies
0 recast
0 reaction