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
Payment could not be completed #5043
Comments
I am getting the same error in mediated transfers. After a few hours of letting the nodes stay idle and then restarting them. Direct transfers work. but in case of one hop or two hop mediated transfers I get the following messages.
The second payment is |
I'm having the exact same issue |
As far as i could see in the logs for target node The node's last known presence state was REACHABLE:
Once the payment is initialized, Raiden queries the PFS for routes to be able to send the payment forward. However, the PFS returns zero routes for the payment.
Making the payment ffail because of the lack of routes. |
I also have this issue almost all the time now. I tried with scenarios and triggering transfers manually via the WebUI. The PFS returns 0 routes most of the time, because it does not see all nodes of the route I have plenty of logs, if needed for debugging. But it looks like everyone can reproduce that error. This is one example of a mediated transfer I tried from '0xb232E968923c7EFB813c5a10E3FFb4E92768f625' (Source) to '0x336EeCAB15Fe67bA0293c7B7a33D1ee4c2abD4A3' (Target). I tried it 3 times in 4 minutes, nodes were running all the time.
Basically, the target '0x336EeCAB15Fe67bA0293c7B7a33D1ee4c2abD4A3' was not reachable from the pfss perspective. |
Maybe it is not a matrix issue afterall ...
Here are the full logs |
From the case that Talel posted above, what we know so far is:
Looking at the code for the transfer, we are lacking a check to make sure balance >= transfer amount. So this is what could be done in this case, otherwise it's a user issue trying to send more than deposited. |
@nephix can you provide the logs and tell us when exactly this issue occurs? |
It appears that Dominik's issue was that the BF1 scenario was setting |
I'll close this issue as the context seems to be separate between Dominik's case and Talel's one. |
@Dominik1999 sorry I don't have my logs anymore. I will try to save them if I encounter the same issue again |
I tried to pay via a channel that was opened automatically when I joined the TestToken token network and kept getting a message saying: “Payment could not be completed because there is no route available”.
I also tried to make a payment to another of my own nodes that I had opened a channel directly with and got the same message on the first couple of tries before the payment went through. This scenario happened with the Mediated Transfers as well, error message a couple of times before the payment passed.
Raiden 0.200.0rc1
raiden-debug_2019-10-07T11:28:06.284028.log.zip
node_0faa9bcd.zip
The text was updated successfully, but these errors were encountered: