search

Ride-The-Lightning / RTL

Ride The Lightning - A full function web browser app for LND, C-Lightning and Eclair
MIT License
752 stars 158 forks source link

Get Forwarding History Failed #1031

Open shinghim opened 2 years ago

shinghim commented 2 years ago

Describe the bug After logging into the RTL client, the client is unable to load the forwarding history after showing that it is loading for 1-5 minutes.

To Reproduce Steps to reproduce the behavior:

  1. Navigate to the RTL login page
  2. Input password
  3. Wait for the forwarding history to load
  4. See error

Screenshots Capture

Your environment

Additional context Add any other context about the problem here.

ShahanaFarooqui commented 2 years ago

Which version of C-lightning-REST and CLN are you on?

shinghim commented 2 years ago

c-lightning-rest v0.7.2 CLN v0.11.1

ShahanaFarooqui commented 2 years ago

We haven’t tested it with CLN v0.11.1 yet. Will test it as soon as we upgrade. Thanks for opening the issue.

shinghim commented 2 years ago

i've had this happen using several of the previous versions, but just thought of opening a ticket today. Appreciate all the work you do! Please let me know if you need me to grab any logs or any other info

ShahanaFarooqui commented 2 years ago

Do you have large number of forwarding events on your node? Some of the CLN users recently complained about RTL hanging up due to that. I am currently working on the same issue #1029. So your issue might resolve with this too.

Thank you for your kind words.

shinghim commented 2 years ago

Not sure what constitutes a large number, but I have around 3750 forwarding events, so hopefully this will get addressed in the other issue you mentioned

ShahanaFarooqui commented 2 years ago

@shinghim Could you please confirm if the issue still persists with cl-rest >v0.9.0 & rtl > v0.13.0 as I am unable to reproduce the error on my end.

clarketowson commented 1 year ago

My node has this issue as well. I have a large number of forwarding events. Total number: 5318. I also have a large number of routing events. My node has been up since March 2021. Two years and eight months total.

I created an issue about it here: [https://github.com/btcpayserver/btcpayserver/discussions/5523] (url)

I'm running rtl 0.11.2 on BTCPay Server v1.3.5.0. I'm very conservative with upgrades as it's a production server. I will soon build a 2nd BTCPay server and keep that server always at the latest version of BTCPay and use that as my backup server if anything goes amiss with the production server.

@saubyk and @ShahanaFarooqui I would like to encourage that this bug please be looked at and hopefully fixed with some urgency if that's possible. It's actually a very important emerging problem from a KYC/AML perspective for nodes like mine in Australia that will need to submit suspicious transaction reports to the regulator and for times the regulator might come knocking. Not being able to produce the forwarding events is a serious compliance issue and will become increasingly so in the years ahead especially for large nodes in countries like the USA that need to be fully compliant.

The other related issue I noted is a number of the docker container processes restart when this issue occurs including lightning and rtl.

I think the fix should ensure that a large number of forwarding and routing events can be handled. A number high enough that very busy nodes can produce perhaps 5 years worth of events. Excel has a limit of 1,048,576 rows. CSV files as I understand them have no limits of rows you can add to them.

I'm happy to help with screenshots and detailed notes from my node regarding this issue.

Kind Regards,

Clarke

Clarke Towson CEO INTJ Billing

m: +61 432 359 166 a: 7 Cullen Court Spotswood Victoria 3015 AUSTRALIA w: https://intjbilling.com/ e: clarketowson@intjbilling.com