Open ghost opened 3 years ago
@miguelfreitas As far as I can see, the seed3.* node is down and seed/2 nodes doesn't contain IPs with standard port 28333 (there are no so many nodes with 28333: my server sees just 2 nodes on that IP, but one of them is the server itself). IMHO, either twister-seeder
should be modified to support seeding from nonstd
subdomains as well, or we need a few extra public nodes on the standard port.
Not sure, but after disabling resolving service to free 53 port for twister-seeder, I able to receive new addresses only by adding direct IP to mainnet_seeds array
btw, I think we should add new active service nodes to this list.
https://github.com/miguelfreitas/twister-seeder/issues/7#issuecomment-805861772
it seems that problem was fixed by changing DNSStubListener option to NO the /etc/systemd/resolved.conf
DNSStubListener=no
Thanks to @dryabov
According to pre-defined seeder nodes I'm right that all seeder currently offline?
I'm asking because currently twister network delivers messages with high latency (about 1 day)
host
>As was said in following issue I ready to provide 24/7 virtual or dedicated machine. Which is twister seeder requirements? How many space estimated needed to store and transmitte the network data?
@dryabov, could you help us to setup the seeder node by joining to the @twisterarmy community and it resources? Also I ready to donate for any help about documentation of this issue.
The Segmentation fault error (#6) is formally solved as we can run a node on the older OS distributive. I not have a lot of time to learn all the things but cat help with resources.