-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LNDhub failure for "bandwidth" issue #522
Comments
This is the main thing that is confusing to the bluewallet guys and they asked me to ask yall 👀 |
I've never seen it before either. Does it always occur or is it in a good state for a bit? There have been a few LND issues with large nodes in 32 bit. I'm working on a 64 bit image (beta is available online), but I would wait to upgrade if you have serious funds on that device. The new image seems promising, but doesn't have much runtime yet. |
Yeah this happens about 1 to 2 times a day.. only LNDhub is affected, but if I click on the :3000 webpage, it reboots LNDhub after 1-2 minutes without needing a full reset of the node |
MyNode started this after I upgraded to Mynode version 0.2.31. Version 0.2.30 was all fine. |
Seems to be an issue between LndHub and LND. The fact that is seems to be worse after a LndHub upgrade seems to point to something it is doing. I'm wondering if upgrading to 64-bit lnd helps. |
How do I downgrade LNDHub?
Em qua., 5 de mai. de 2021 às 02:15, Taylor Helsper <
***@***.***> escreveu:
… Seems to be an issue between LndHub and LND. The fact that is seems to be
worse after a LndHub upgrade seems to point to something it is doing.
I'm wondering if upgrading to 64-bit lnd helps.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#522 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQE4WGQK7HR23XZ422AMVHTTMDH7HANCNFSM435PW4NQ>
.
--
Atenciosamente,
Antonio Sidinei Schug
|
You could update the mynode_app_versions.sh file and re-run the upgrade script. There are dev instructions for how to modify files in the readme. |
On latest version I cannot successfully reboot LNDhub to work. It is full broken 😅 If I reinstall LNDhub will it delete wallets associated? How can I backup user accounts? Is there an easy CLI command to rerun upgrade on LNDhub or revert state to a few updates ago |
What does the log show now? In the latest version, LNDHub was upgraded to 1.3.3 which I was hoping would help, but seems to have possibly made things worse. If LNDHub is failing, it should auto-restart, but if it just is in a failed state where it can't talk to lnd, it may stay in a broken state. The LNDHub data is stored in a redis database, so a re-install should not lose any data, but I also don't think it will help resolve any issues. |
-- Logs begin at Wed 2021-05-12 19:11:57 CDT, end at Wed 2021-05-12 19:56:27 CDT. -- |
Interesting. Did you restart LNDHub manually? It looks like it restarted once. I'm getting the error on one of my node's as well and it just has LNDHub enabled with like one channel in lnd. Even a lnd + lndhub restart immediately starts seeing errors. May 12 20:47:17 myNode lndhub[14374]: updateDescribeGraph() |
Yes I've restarted, reinstalled, etc No luck since latest update it is perpetually not working right 🥲 I run LNDhub for a few people, so I've gotta find a way to get it going back to previous versions asap |
1 similar comment
Yes I've restarted, reinstalled, etc No luck since latest update it is perpetually not working right 🥲 I run LNDhub for a few people, so I've gotta find a way to get it going back to previous versions asap |
I'm trying upgrading to the tip of LndHub now. Unfortunately, I'm still not sure what is causing the issue. I'm afraid downgrades won't work because the database doesn't look backwards compatible. |
FYI, downgrading to 1.2.0 performs updates successfully. I don't know if data about transactions, accounts, etc... would persist though. May 12 23:15:38 myNode lndhub[8734]: updateLightning() |
Yikes that is very scary. I'm not sure I can afford to lose the database. There must have been big changes to these updates 👀😬 |
v1.3.0 also appears to be working fine. I just saw that updates were made to the database schema when upgrading to the most recent versions - makes me think downgrading may not keep all data. That's a better question for BlueWallet. |
So Bluewallet team in the other thread found the issue, and also overtorment says that downgrading shouldn't hurt the schema. The fix is very easy though, commenting out two lines of code from the controller/api.js |
So these fixes were temporary. Beggggging someone to revert fully back to pre 1.3.0 I have people on my LNDhub hitting me up multiple times a day upset from errors. I can't constantly be manually restarting. Is there a way to code in an automatic LNDhub restart if the bandwidth exhausted happens? |
You can try manually downgrading to version 1.2.0 by editing /usr/local/share/mynode/mynode_app_versions.sh + reboot + upgrade via application page. Have you tried that yet? I'm worried there are backwards incompatible changes that may not work for everyone, but you can definitely do the downgrade yourself. Are you using an SSD or HDD? |
SSD |
MyNode hardware (please complete the following information):
**issue found here, but bluewallet team doesn't understand what it could be on their side: BlueWallet/LndHub#161 (comment)
The text was updated successfully, but these errors were encountered: