You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I've tried everything in my capacity to get around this and can't sort it myself and would be grateful for some guidance as to what to do next in order to id the bug and make the cln-application work.
I did so far:
Reinstall the Debian os (tried Debian 10, 11, 12)
Tried in several virtual machines, and on two different PC (real hardware)
Tried 0.0.6 all the way down to 0.0.1
Tried several lightningd releases, from the latest one, some older ones, including the master branch.
Tried several npm/node version, -omit=dev, -audit fix, -force, everything. Has no change whatsoever.
All in all, I've spent little over one week trying to make it work and regardless of what I try, I keep getting the lightningd.log filled with tens of thousand of errors and the CPU fluctuate between 0% to 100% every 2 or 3 seconds.
Before I give up all hope in ever be able to using a lightning network, can one of the dev have a look and advise what/where I need to look in hope to have this functional please. That would be great. thanks
Reported by: @GTC
Reference: ElementsProject/cln-application#76
Hi. I've tried everything in my capacity to get around this and can't sort it myself and would be grateful for some guidance as to what to do next in order to id the bug and make the cln-application work.
I did so far:
Reinstall the Debian os (tried Debian 10, 11, 12)
Tried in several virtual machines, and on two different PC (real hardware)
Tried 0.0.6 all the way down to 0.0.1
Tried several lightningd releases, from the latest one, some older ones, including the master branch.
Tried several npm/node version, -omit=dev, -audit fix, -force, everything. Has no change whatsoever.
All in all, I've spent little over one week trying to make it work and regardless of what I try, I keep getting the lightningd.log filled with tens of thousand of errors and the CPU fluctuate between 0% to 100% every 2 or 3 seconds.
Before I give up all hope in ever be able to using a lightning network, can one of the dev have a look and advise what/where I need to look in hope to have this functional please. That would be great. thanks
Log Sample:
2024-11-11T05:26:41.273Z DEBUG 02a65e7dccf5bee5ddce99e09379fedd27572d0f97ac18053b0035e10545f4f53c-connectd: peer_out INVALID 22859
2024-11-11T05:26:41.275Z DEBUG 02a65e7dccf5bee5ddce99e09379fedd27572d0f97ac18053b0035e10545f4f53c-connectd: peer_out INVALID 22859
2024-11-11T05:26:41.278Z DEBUG 02a65e7dccf5bee5ddce99e09379fedd27572d0f97ac18053b0035e10545f4f53c-connectd: peer_out INVALID 22859
2024-11-11T05:26:41.281Z DEBUG 02a65e7dccf5bee5ddce99e09379fedd27572d0f97ac18053b0035e10545f4f53c-connectd: peer_out INVALID 22859
2024-11-11T05:26:41.284Z DEBUG 02a65e7dccf5bee5ddce99e09379fedd27572d0f97ac18053b0035e10545f4f53c-connectd: peer_out INVALID 22859
x10k x20k x30k... it's endlessly spamming the log like above...
The text was updated successfully, but these errors were encountered: