Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
p2p/discover/table.go:389] no seed nodes found #2635
i was trying to run another node in a separate container in my computer to let one node with public blockchain and the other with a private blockchain to use it to test some contracts.
The main blockchain seams that got a default configuration from other path settted before (private blockchain) but a new one only says "p2p/discover/table.go:389] no seed nodes found" all the time, how can i fix this new one with public and let him synchronize with public?
Steps to reproduce the behaviour
i installed the main node as you mentioned in the wiki, at the begining it only synchronizes and it looked like it was mining but i let it mine over 2 days and no reward was received, then i set another node with a private network and it mined succesfully but when i came back to the main node, it started to work with a private network. After that i just let it go the main node with a private blockchain and i tried to set another container to configure it with a public node and i tried to started and it just said all the time:
i also tried with maxpeers 25, maxpeers 50, maxpeers 100 and it works in the same way
Long story short... I found this post:
You might try the following to verify if something messed up your iptables, like it was the problem on my system:
The "before" test:
Retest a container and see if it finds peers. In my case, this was happening.
Then the "after" test:
The difference is clear:
NAT IP tables before the re-install with containers not finding peers:
NAT IP tables after the re-install with container now finding peers again:
You may just try to add the 2 missing rules.
As you, I did nothing special around my network. I didn't touch the iptables, nor a firewall. I simply started a container to connect to the production network, then I played with containers to build my private test network, next the "thing was broken".
I'm currently looking into what could had have gone wrong. If I find find out what touched the iptables, I'll post it back here.
Hope this helps.