-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Panic in libp2p after ~24 hours #18
Comments
This panic can happen if the SHA-256 hash of the local public key plus the remote nonce is the same as the SHA-256 hash of the remote public key plus the local nonce. In other words, this is very very unlikely, as in "will never happen in the history of the Universe likely". |
What did I win ? ;)
|
More seriously, I will keep monitoring for that one. If no feedback after a reasonable amount of time, we will close it. If the issue happens again, I will start guessing BTC addresses with this machine :) |
I ran into this issue 3 times today. |
Is it possible that you have the same network public key (the It still shouldn't panic even if it is the case, but knowing that may help pin-point the exact problem. |
libp2p/rust-libp2p#480 should fix the issue. It will be pulled into substrate soon-ish. |
I don´t think so but I can check if you still need. Do you ? |
I think to have the same problem... |
Is there anything I can do? Right now I have this problem several times a day, so i think to create a scritpt to start and stop process once an hour, is it a good solution for now? |
@dbpatty If you are building from source, using the latest libp2p should fix it. Find the line that says: libp2p = { git = "https://github.com/libp2p/rust-libp2p", rev = "<something>", default-features = false, features = ["libp2p-secio", "libp2p-secio-secp256k1"] } And replace the |
ok thank you I'll try |
I don't find this line, in which file is it? |
@tomaka this is fixed, yeah? |
Yes! |
The cause of the underlying issue is still unknown (libp2p/rust-libp2p#479), but we replaced the panic with an error that disconnects the remote. |
* fix * Update consensus/src/lib.rs Co-Authored-By: Bastian Köcher <bkchr@users.noreply.github.com>
* fix * Update consensus/src/lib.rs Co-Authored-By: Bastian Köcher <bkchr@users.noreply.github.com>
Version 0.2.15-3720d74-x86_64-linux-gnu
The node crashed after ~24 hours
Node start logs
Node crash logs
The text was updated successfully, but these errors were encountered: