Someone might be able to help if provide more info like version of LND used, and more specifics from the log files.
If can't resolve then you may want to recover funds with force closures on the channel via your static channel backup file.
Discussion
Thank you, appreciate any help:
LND version v0.16.3
To troubleshoot, a few weeks ago, I did perform some software updates. I was previously on either LND v0.16.2
Ram 4gb
Cpu usage: 78%
Ram usage: 43%
Screenshots with log to follow:
nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl
Sign up for a GitHub account and open an issue at https://github.com/lightningnetwork/lnd/issues
Make sure to include the logs in the ticket, especially the stack trace. FWIW in all that soup, the relevant error is that "invalid hash state identifier", but I don't know what it means.
Thank you, it was easy creating a github account, only an email required. Posted issue. Will update once resolved.
I’ll suggest you send these logs to myNode telegram group. There are people there that might better understand the problem
I guess ill figure out how to join telegram, i hope they dont require a phone number nor a non-shared IP address
Cant signup for telegram without a phone number 🫤
Yeah but you can hide phone number in settings
Id rather not give a service my phone number to begin with.
Update: logged as Issue in github (signup only required an email). bitcoin gui shows an old block height & old transactions but bitcoin logs shows current height. From bitcoin i deleted peers.dat and then rebooted, that did not work. So still same issue with LND not connecting.