lightningnetwork
Query from peers failed warning
Background
I am creating a new lnd node on kubernetes with postgresql, so far is going well (graph and blockchain synced) but I am having a warning each 20 seconds which is increasing the log very fast and I want to be sure that this is not a big issue before migrate the coins from one node to this new one.
Your environment
- lncli version 0.15.0-beta commit=v0.15.0-beta
- Linux lnd-mainnet-tor-0 5.15.0-39-generic x86_64
- Bitcoin Core version v23.0.0
Steps to reproduce
Initialize the node, after wallet unlock and the node starts to operate I get those warnings.
Expected behaviour
Don't get so many warnings.
Actual behaviour
Here is part of the log
2022-08-10 12:19:43.940 [WRN] BTCN: Query(3054) from peer 90.156.26.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:19:51.247 [WRN] BTCN: Query(7381) from peer 31.42.176.138:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:20:15.941 [WRN] BTCN: Query(3054) from peer 136.62.35.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:20:23.249 [WRN] BTCN: Query(7381) from peer 60.240.210.155:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:20:47.942 [WRN] BTCN: Query(3054) from peer 136.62.35.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:20:55.249 [WRN] BTCN: Query(7381) from peer 90.156.26.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:21:19.943 [WRN] BTCN: Query(3054) from peer 31.42.176.138:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:21:27.251 [WRN] BTCN: Query(7381) from peer 60.240.210.155:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:21:51.943 [WRN] BTCN: Query(3054) from peer 136.62.35.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:21:59.252 [WRN] BTCN: Query(7381) from peer 90.156.26.148:8333 failed, rescheduling: did not get response before timeout
2022-08-10 12:22:23.944 [WRN] BTCN: Query(3054) from peer 136.62.35.148:8333 failed, rescheduling: did not get response before timeout
Looks like a problem with querying data from bitcoin peers. Do you use neutrino or a pruned node?
Observation: those nodes have service feature of 1033, which decodes to NODE_NETWORK, NODE_WITNESS, NODE_NETWORK_LIMITED, but not NODE_COMPACT_FILTERS.
There may be an issue with these specific peers to serve block data, they may not support this and therefore time out. If that's the case I think that we as the client could recognize that. If you were able to sync to the chain and to the graph, then I would not see this as a problem, but perhaps somebody else knows better.
Do you think is a good idea we just disconnect from those nodes 4 nodes and move on?
I think you could do that and add other peers (perhaps one of those: https://bitnodes.io/nodes/?q=1097).
Closing since this is an issue w/ selected peers. If you use connect instead of addpeer, then you'll also seek out more peers over time.
