I restarted my Start9 node (through the system option) and now Lightning doesn’t seem to want to restart and showing in the logs :
2025-10-06T18:16:45-04:00 2025-10-06 22:16:45.807 [WRN] BTWL: Received non-standard input sig= “A string of characters”, witness=[0000000000000000000000000000000000000000000000000000000000000000]
and it just keeps repeating for hours. I have a few open channels, what should I do?
One of the issues in not providing fuller logs is that there’s no context. I assume somewhere nearby in the logs it identifies the peer that is sending you this malformed string. Most likely they are having technical issues, most likely they are a peer you don’t have channel with. If you do have a channel with them, I’m not sure if their misconfiguration is a particular risk to you or not.
Also, for what its worth, warnings aren’t errors.
The problem was it seemed like it was stuck in a never ending loop which kept my LND node from being seen online for over a day.
I checked the channels list and was still intact, tried restarting the node a few times, but it didn’t change anything. Then I tried to block internet access and then connecting again and after doing that it triggered a pruning which then the warnings stopped and LND was able to start again. Never had this in years of running LND. I was about to try a manual pruning but it got triggered automatically I guess.
Now however I am missing liquidity, I’m thinking of trying to reset wallet transactions to trigger a rescan and hopefully find what is missing, but will let the node run for a while before trying that I think. Unless there’s something I should do?
I’m not sure what to tell you, I’ve seen nothing of the situation you’re facing other than a single line from the logs with no context.
You now mention pruning, something looping. What did you prune?
The two main actions under LND are ok to use, they won’t break anything.
It’s all very odd, I’m trying to describe as best I can. (deleted prior post by error)
Now, I let my node run for a few days, it ran routed payments fine, except it is still missing some liquidity.
I tried a Reset Wallet Transactions 24h ago and when LND restarted it started with those warnings again constantly, the GUI says LND is syncing, and the node is offline. Below is an example of the log after running 24h, LND looks like it is getting the new blocks from Core, but is still offline and getting these warnings, but now they are fewer and longer inbetween instead of constant:
2025-10-11T17:02:18-04:00 2025-10-11 21:02:18.928 [INF] NTFN: New block: height=918621, sha=0000000000000000000096f0970fa631378e9fd9b5449d6b7edfd15f8da425a1
2025-10-11T17:11:23-04:00 2025-10-11 21:11:23.086 [WRN] BTWL: Received non-standard input sig=035e040e04e4c7ea682f466f756e6472792055534120506f6f6c202364726f70676f6c642ffabe6d6d833cf9932adc40a05bc465bbf078c805188bd27c9be19848ed99c5bb2a980789010000000000000079a45248d8f8000000000000, witness=[0000000000000000000000000000000000000000000000000000000000000000]
2025-10-11T17:11:23-04:00 2025-10-11 21:11:23.086 [WRN] BTWL: Received non-standard input sig=035e040e04e4c7ea682f466f756e6472792055534120506f6f6c202364726f70676f6c642ffabe6d6d833cf9932adc40a05bc465bbf078c805188bd27c9be19848ed99c5bb2a980789010000000000000079a45248d8f8000000000000, witness=[0000000000000000000000000000000000000000000000000000000000000000]
2025-10-11T17:11:23-04:00 2025-10-11 21:11:23.248 [WRN] BTWL: Received non-standard input sig=035e040e04e4c7ea682f466f756e6472792055534120506f6f6c202364726f70676f6c642ffabe6d6d833cf9932adc40a05bc465bbf078c805188bd27c9be19848ed99c5bb2a980789010000000000000079a45248d8f8000000000000, witness=[0000000000000000000000000000000000000000000000000000000000000000]
2025-10-11T17:11:23-04:00 2025-10-11 21:11:23.372 [INF] NTFN: New block: height=918622, sha=00000000000000000001a15e86fafb76ebb9e95d846988f0135d471cafc900f2
2025-10-11T17:21:36-04:00 2025-10-11 21:21:36.050 [INF] NTFN: New block: height=918623, sha=0000000000000000000057add47de9d8d8e1cdd6e3ec8827fcf41c6bdd090cf9
2025-10-11T17:27:32-04:00 2025-10-11 21:27:32.632 [INF] NTFN: New block: height=918624, sha=00000000000000000001545ab2ef89b962d937c0b6667a06cf8330f055ca2e33
I’m letting it run a bit more, but soon I think I’ll try to restart it a few times to hopefully get my node back online before I start getting channels forced closed. I am able to connect to LND via Zeus/Bit Banana mobile wallets, but can’t transact. I don’t know what is possibly corrupted(?) or what to do about it. Any input would be appreciated, I can post more log, it’s huge and repeats or anything else which could be useful.
Restarted LND and the node reconnected properly and routed payments as usual. So it looks to be linked to trying to do a wallet rescan, tried a few more times and it always gets locked up with these warnings until it gets restarted.
Wallet rescans only look for onchain TXs.
It’s impossible for a lightning channel to “lose liquidity” (without complex splicing). It’s possible for a channel to close and to be lost. Is that what you mean? If you have channels force closing, you likely just need to wait for things to settle.