LndHub: LNDhub 1.3 on myNode failing often
having to restart LNDhub almost daily. Wallet gets code 7 error if I’m creating an invoice, or code 4 if I’m paying an invoice. I goto lndhub address to investigate, and lndhub officially fails and restarts itself to work again properly. Only been happening since 1.3 update.
– Logs begin at Wed 2021-03-24 05:42:39 CDT, end at Wed 2021-03-24 19:01:18 CDT. –
Mar 24 19:00:58 myNode systemd[1]: lndhub.service: Failed with result ‘exit-code’.
Mar 24 19:00:58 myNode systemd[1]: lndhub.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! /home/bitcoin/.npm/_logs/2021-03-25T00_00_58_882Z-debug.log
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! A complete log of this run can be found in:
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! Failed at the lndhub@1.3.0 start script.
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR!
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! Exit status 3
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! lndhub@1.3.0 start: babel-node index.js
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! errno 3
Mar 24 19:00:58 myNode lndhub[30998]: npm ERR! code ELIFECYCLE
Mar 24 19:00:58 myNode lndhub[30998]: lnd failure
Mar 24 19:00:58 myNode lndhub[30998]: 2021-03-25T00:00:58.309Z : info: [/] : [“673669fe-bb87-4c59-b59d-12246927b69f”]
Mar 24 19:00:57 myNode lndhub[30998]: metadata: Metadata { internalRepr: Map {}, options: {} } }
Mar 24 19:00:57 myNode lndhub[30998]: details: ‘Bandwidth exhausted’,
Mar 24 19:00:57 myNode lndhub[30998]: code: 8,
Mar 24 19:00:57 myNode lndhub[30998]: at processTicksAndRejections (internal/process/task_queues.js:79:9)
Mar 24 19:00:57 myNode lndhub[30998]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24)
Mar 24 19:00:57 myNode lndhub[30998]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted
Mar 24 19:00:57 myNode lndhub[30998]: metadata: Metadata { internalRepr: Map {}, options: {} } }
Mar 24 19:00:57 myNode lndhub[30998]: details: ‘Bandwidth exhausted’,
Mar 24 19:00:57 myNode lndhub[30998]: code: 8,
Mar 24 19:00:57 myNode lndhub[30998]: at processTicksAndRejections (internal/process/task_queues.js:79:9)
Mar 24 19:00:57 myNode lndhub[30998]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36)
Mar 24 19:00:57 myNode lndhub[30998]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24)
Mar 24 19:00:57 myNode lndhub[30998]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted
About this issue
- Original URL
- State: open
- Created 3 years ago
- Comments: 80 (37 by maintainers)
hmm, so if that was the source of problems… ill prepare a release where that functionality is disabled by default
@as-schug go into terminal in your myNode and navigate to opt/mynode/LndHub/controllers
You can do this by entering these three commands
cd … cd … cd opt/mynode/LndHub/controllers
open api.js in vim text editor with the command:
“vi api.js”
vim starts in command mode, so don’t type anything yet. Move the cursor via your arrow keys until you find these lines:
updateDescribeGraph(); setInterval(updateDescribeGraph, 120000);
Once your cursor is over the u in “update” from the first line, press “i” on your keyboard to enter vim “insert mode”
Type //
Now hit ESC to re-enter command mode Use the down arrow to navigate to the ‘s’ in setinterval
press ‘i’ again to activate insert mode
Type ‘//’ once again
You have now commented out the lines and they should look like this
//updateDescribeGraph(); //setInterval(updateDescribeGraph, 120000);
Hit ESC to enter command mode one last time
type :w and hit enter to write your changes and save the document
Type :q and hit enter to quit the editor
Finally goto the applications menu in your myNode UI and restart LNDhub
Everything should work now
thank you, worked for me, too.
hey all, downgrading should be easy, as there are no database changes between releases.
https://github.com/BlueWallet/LndHub/compare/v1.3.0...v1.3.3
im reading the diff between 1.3.0 and 1.3.3, and what caught my attention is
can someone comment out those 2 lines in controllers/api.js ? and see if that helps?
Yes… Some tests worked just fine. Thank you again!!!
Oh my… That´s great. Thank you man. I saw your post but I missed “I commented out those lines using vim and restarted. It seems to work for now!!”
More users seem to be seeing this issue with the 1.3.3 upgrade. Any ideas? The underlying Lightning daemon seems to be fine and users report they can properly send and receive funds via other wallets.
your logs are safe to share, i checked.
this
'Bandwidth exhausted'bothers me. nowhere in lnd+lndhub stack it should be raised. it feels like your lnd is hosted somewhere on googlecloud and it simply exhausted all bandwidth.