Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
beam-node crashed if DNS lookup of one peer fail #288
This made me mistakenly think that the database is corrupted, so I removed
Platform and build
And your website is down and all nodes in your website are not work. What happened?
Update at 1/4/19 13:52:05 UTC: The website looks back, but the node list still doesn't work.
No, it is not my first running of the node. I have only restarted it, and it crashed, it cannot running again, denial of service totally.
From another perspective, if I fill in a wrong IP address in the peer configuration, the node will not crash.
In addition, even for the user who started the node for the first time, the node crash is very unfriendly. They may have filled more than one peer domains, and at least one of them may work. But as long as there is any DNS exception, the node has no chance to run at all. This makes people feel very discouraged.
And, if the domain name was good before, but suddenly it's down, then my node will cannot run again after I close it. And I have to edit the configure file.
And, the problem will be more serious if a peer domain name list is built into the node. Because a DNS issue with any domain in the list will cause the node to fail to start completely. And at this time the user cannot solve the problem by editing the configuration file, he must modify the source code and build it. This is a typical centralized denial of service risk.