-
Notifications
You must be signed in to change notification settings - Fork 880
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
lightningd hanging, not opening RPC port, not syncing, reducing latest block by 15 #2687
Comments
The last thing I am seeing on
This poll is thus the main io-loop. The issue is that topology should be scanning forward for new blocks continuously, but strace shows it has only scanned one block, then after reading it, topology updates the db, but suddenly we enter the main loop (which we should not, because, topology should have its own loop....?). @cdecker there may be a race condition? The main |
I believe I have cracked this issue. After starting up plugins and the core daemons ( lightning/lightningd/lightningd.c Lines 744 to 747 in 1141243
As the comment says, it does an Looking inside lightning/lightningd/chaintopology.c Lines 896 to 897 in 1141243
Now, just prior to the above lightning/lightningd/chaintopology.c Line 894 in 1141243
In particular, we only execute lightning/lightningd/chaintopology.c Lines 29 to 38 in 1141243
And if we look at the logs:
Looks like fee estimation from We search for this text lightning/lightningd/bitcoind.c Lines 157 to 159 in 1141243
And we scroll down a little and also see that, in case of such a failure, the lightning/lightningd/bitcoind.c Lines 163 to 165 in 1141243
Of course, it uses a timer..... which the lightning/lightningd/chaintopology.c Lines 896 to 897 in 1141243
TLDR: If fee estimation completely fails, we retry 1 second later. Unfortunately, the initial @cdecker @rustyrussell it seems to me that the simplest solution is to write a |
…e, have chaintopology use it. Fixes: ElementsProject#2687
…e, have chaintopology use it. Fixes: ElementsProject#2687
Signed-off-by: Christian Decker <decker.christian@gmail.com>
…e, have chaintopology use it. Fixes: ElementsProject#2687
Signed-off-by: Christian Decker <decker.christian@gmail.com>
…e, have chaintopology use it. Fixes: #2687
https://drop.geekbox.info/feeestimateerror.log It seems the error was the whole time, that my bitcoind was 17.1 and did not support the 2nd paramter to the getsmartfeeestimate.... your patch made the verbose error message visible, but a check if the available bitcoind has the required features or minimum version would be helpful for sure, too. |
@svewa okay, I shall open a separate new issue. |
No, you get that because bitcoind could not |
Did you change your datetime (had a powercut or something) recently ? What are the bitcoin logs on an |
Yes, I did. Just see the output in https://drop.geekbox.info/feeestimateerror.log
When you run this very command |
I have c-lightning running for over a year now, but some time maybe two month ago I noticed it stopped and would not properly start again. I tried updating to 0.7.0 and now to latest git, does not help.
config file:
starting lightningd:
when stracing it with -f the following output is produced:
http://drop.geekbox.info/strace.log
The text was updated successfully, but these errors were encountered: