-
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
failed: WIRE_EXPIRY_TOO_SOON (reply from remote) #875
Comments
Was your blockchain up to date? The expiry time is computed from the current block height, so if |
It looks like bitcoind is up to date and lightningd is behind. I'll wait for it to catch up and try again. |
Notice that we recently fixed a bug that caused |
I updated around 10am. Was it that recent? |
No, you should have it then ^^ |
well, that error cleared, but it's just a different error now. WIRE_TEMPORARY_CHANNEL_FAILURE |
It's alternating between that error and WIRE_UNKNOWN_NEXT_PEER despite two channeld_normal channels. |
I'm starting to think I need to close everything, wait for funds to settle, and start from scratch. I fear I have compounded errors in my database. If it will help with development, I will continue to troubleshoot. Otherwise I'm gonna delete everything c-lightning start from a clean slate tomorrow. |
Are both hops yours? Those error might be coming from the intermediate node, not your own. |
no, both hops are not mine. I'm connected to two nodes (other people's nodes) with state channeld_normal. getroute works correctly, but pay fails every time. I'm connected to and 035f1498c929d4cefba4701ae36a554691f526ff60b1766badd5a49b3c8b68e1d8@78.63.23.25:9735 |
I can't see the route you would have taken, but I think that simply the intermediate hop lost connection (or closed the channel) with the destination, hence the |
I'm having the same problem.
Maybe there's an issue with that node and I should close the channel and try opening another one to a different node? |
Can you show us the result of a |
@cdecker sure:
|
Also, here's the debug output from lightningd (for the I'd be happy to take a hint on how to begin reading this ;) |
I am now getting
|
Sorry for the delay in looking at this. Checking the routing table it seems that we are indeed chosing a delay that is too small:
Which if I'm not mistake requires the |
For reference, when I try to route from your node
Notice the much higher expiry delta of 144 as per routing table. |
Hey, thanks for the response. Yes, I'm getting the same result for getroute:
If I understand correctly, the delay is something that my node should calculate and set it according to what the channels in the route require (e.g. 144), but it's actually setting it to lower values (e.g. 4)? |
Meanwhile, I've opened another channel and succesfully bought myself a few stickers so I'm a happy camper :) But I'm still interested in this so I'm trying to recreate the previous situation. But now I have another problem. My
If I now try to find a route for 100M msatoshi, it should only be able to through channel But getroute shows a route through another peer/channel with only 30M msat:
Am I misunderstanding something? (Thanks for your patience :) |
Thanks @darkobodnaruk for the update, glad it worked out with the new channel. It's really strange that the routing algo would choose to set a delta of 4, when it knows about the larger delta required by the channel. At the moment I can't really reproduce it, but I'll keep an eye open for it. Regarding us choosing the channel with insufficient capacity, that's ok, with #638 merged we now hand back these failures to |
while attempting to send a payment I get the following error:
lightning-cli pay lnbc565992510p1pd8xucypp58k5h2ajge5cvhjvyj4ffx38g59ha9k8s49neh42lpwg834t2gsfqdzsgfkx7cmtwd68yetpd5azqdpw8yujq42ngssxvmeqv9hxggzvd9nksarwd9hxwgznw35kx6m9wgs8sgp3cqpgd922x80d34ayxl46ff9a5uv6qzu9ca9cfy9ts7mernq47pam8jfr9rzlu3wn7zfcrtrf0rg7wj754tre20ty3yzc6mek6h9q70ng0pgqc7r7aa
lightningd(22294): Sending 56600873 over 2 hops to deliver 56599251
lightningd(22294): peer 029efce538a7f6ba7873b1bd00e0028ca39a658b96af326d349fa45bfa34226073: htlc 11 failed from 0th node with code 0x100e (WIRE_EXPIRY_TOO_SOON)
{ "code" : -1, "message" : "failed: WIRE_EXPIRY_TOO_SOON (reply from remote)" }
The text was updated successfully, but these errors were encountered: