-
Notifications
You must be signed in to change notification settings - Fork 664
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠️ Testnet is down (unknown catchain-related disastrous bug) #272
Comments
Well, recovering from the situation when somebody controlling 40% of testnet validators upgraded them to a buggy version that corrupted the local database, including current catchain state, is not simple. However, we see that this turned out to be possible, even though it required an emergency update of more than 2/3 of all validators. So let's think of this as an unplanned test of the behavior of the TON Blockchain in such harsh conditions. Such things are unlikely to happen in the mainnet, because nobody is expected to control such a large portion of the validators there, so they would not have been upgraded to a buggy version simultaneously. On the flip side, we see that no forks and no invalid blocks have been created during the several hours when the testnet was not working properly, so the Catchain consensus turned out to be robust enough to cope with this situation (as it should), even if it generated a lot of error messages in the process. We still value C and A of the CAP-theorem higher than P. |
Testnet has crashed approximately at 19:02:13 +0200.
I do not know exact reason but after starting up next FATAL occurs:
If I purge catchain receiver data, next error happens:
Also, there are lots of warnings in logs about incorrect signature of left fork blame, "CAIN: blaming source", a CATCHAIN_WARNING that it "got ill" (validator caught coronavirus?!).
Also there was information that one of validators got full disk nearly when this happened.
The network seems to be still down now (at least my validator tries to download something, state or catchain, and then fatals out).
The text was updated successfully, but these errors were encountered: