-
Notifications
You must be signed in to change notification settings - Fork 895
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
WIRE_TEMPORARY_CHANNEL_FAILURE from own peer with "UNUSUAL routing_failure" #956
Comments
Yes, routing does not pay attention to the state of the local channels, it simply selects a short route. Currently routing depends on (routes are marked unroutable for only 20 seconds, in the optimistic hope that the condition changes within that time, so your Just keep retrying until you get a code 205 routing failure or a code 203 permanent failure at destination. The UNUSUAL routing_failure is normal for local failures. It would be unusual for remote failures. I should probably change that... |
"erring node" means the one that reported the error, not the node that is somehow erroneous. In your particular case "First peer not ready" means it is the communication with the peer that is problematic; it would be |
Thanks for the reply and info, @ZmnSCPxj. After rebuilding at d5effc (and closing some small channels, as well as waiting for others in weird closing states to go away, which might be related), failure shifted to:
But overriding the
Since I'll leave the ticket open based on your comment about |
Yes, that is #863, sorry I am somewhat blocked about it...
Fixed by #962, so already done. @cdecker, close please? |
Cool, thanks again. Closing. |
Issue and Steps to Reproduce
Built at b3d4e1:
Should be built past fixes for #638, #893, which have similar symptoms. Seems like different symptoms from #952, afaict.
Attempting to pay a
mainnet.yalls.org
article:In logs with
--log-level=debug
:If I'm reading the output right, the "erring node" is ourselves:
Retrying
pay
repeatedly as suggested by @ZmnSCPxj on #952 (comment) leads to a different failure symptom after 5+ tries (may be legitimate, haven't looked):getinfo
outputThe text was updated successfully, but these errors were encountered: