Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
LNDhub 1.3 on myNode failing often
See original GitHub issuehaving 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
Issue Analytics
- State:
- Created 2 years ago
- Comments:80 (37 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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