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
Raiden crashes with attribute error exception #2931
Raiden crashes with attribute error
I got the following stacktrace when restarting my node after 4 hours when it was oflline. I want to mention that before actually killing my node I closed all the channels, so this might be related to the settlement.
This is the most recent log: https://gist.github.com/CosminNechifor/6822a513869656fff49859570ef496a3
Also I will provide an archive which will contain all my logs and the database(this also might be helpful to have an exact view of what happened with my node):
Read through Requirements for safe usage mentioned in our documentation and make sure your usage follows the requirements.
When testing on kovan with
I waited with all my nodes online for them to settle, and as soon as the channels settled, one of the nodes crashed. After the initial crash when I would get the crash Cosmin mentioned above as soon as I would start the node. This would happen each time.
I tried to replicate the issue so I left the network for all of my nodes again. Again after the channels settled two nodes crashed. After restarting though each node would give a different error, but the initial crash seems to be the same. You can find the log here and the DBs here
referenced this issue
Oct 30, 2018
I believe I found the problem. The partner's balance proof was not available in the
The error manifested itself with a node which has two versions of the database (8 and 9), it's possible the corresponding message was received on a first run which used version 8, but the channel was closed on version 9. This is not a Raiden bug but improper usage.
A lot of our error seems to come from this. I have mentioned it multiple time in dev-raiden-testing that people should not be doing that but still it happened. Perhaps #3006 will help. Also the underlying reason #2984 happened was due to closing happening in one database and settling in another.
This was not the case. The channel with id 35 was opened on the database version 9, and the balance proof was in the database.