BlueWallet / LndHub

Wrapper for Lightning Network Daemon. It provides separate accounts for end-users
http://LndHub.io
MIT License
784 stars 198 forks source link

LNDhub 1.3 on myNode failing often #161

Open godSaysHODL opened 3 years ago

godSaysHODL commented 3 years ago

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

Overtorment commented 3 years ago

can you post a bit more logs?

this one looks suspicious: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted

godSaysHODL commented 3 years ago

can you post a bit more logs?

this one looks suspicious: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted

Yes, is there any risk of exposing sensitive info from the logs? Wasnt sure about account numbers showing or anything

-- Logs begin at Wed 2021-03-24 17:22:23 CDT, end at Thu 2021-03-25 07:42:49 CDT. -- Mar 25 07:42:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:42:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:42:12 myNode lndhub[27570]: code: 8, Mar 25 07:42:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:42:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:42:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:42:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:42:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:42:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:42:12 myNode lndhub[27570]: code: 8, Mar 25 07:42:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:42:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:42:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:42:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:42:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:42:12 myNode lndhub[27570]: updated Mar 25 07:42:12 myNode lndhub[27570]: updateLightning() Mar 25 07:41:48 myNode lndhub[27570]: 54f94216-f730-43b0-9bdc-8c0d041b2464 ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:48 +0000] "GET /getuserinvoices HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:48 myNode lndhub[27570]: 2021-03-25T12:41:48.093Z : info: [/getuserinvoices] : ["54f94216-f730-43b0-9bdc-8c0d041b2464","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:48 myNode lndhub[27570]: 2021-03-25T12:41:48.092Z : info: [/getuserinvoices] : ["54f94216-f730-43b0-9bdc-8c0d041b2464"] Mar 25 07:41:47 myNode lndhub[27570]: 93b0f6fd-86eb-4b3d-9439-08cf80cbdac7 ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:47 +0000] "GET /getpending HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:47 myNode lndhub[27570]: 2021-03-25T12:41:47.988Z : info: [/getpending] : ["93b0f6fd-86eb-4b3d-9439-08cf80cbdac7","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:47 myNode lndhub[27570]: 2021-03-25T12:41:47.987Z : info: [/getpending] : ["93b0f6fd-86eb-4b3d-9439-08cf80cbdac7"] Mar 25 07:41:47 myNode lndhub[27570]: b4fde68d-aa7a-4cfd-8fb3-01e6b0facc20 ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:47 +0000] "GET /gettxs?limit=10&offset=0 HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:47 myNode lndhub[27570]: 2021-03-25T12:41:47.879Z : info: [/gettxs] : ["b4fde68d-aa7a-4cfd-8fb3-01e6b0facc20","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:47 myNode lndhub[27570]: 2021-03-25T12:41:47.879Z : info: [/gettxs] : ["b4fde68d-aa7a-4cfd-8fb3-01e6b0facc20"] Mar 25 07:41:42 myNode lndhub[27570]: 995f86c8-0eed-4510-8b02-70337ce43313 ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:42 +0000] "POST /addinvoice HTTP/1.1" 200 46 "-" "okhttp/3.12.1" Mar 25 07:41:42 myNode lndhub[27570]: 2021-03-25T12:41:42.314Z : info: [/addinvoice] : ["995f86c8-0eed-4510-8b02-70337ce43313","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:42 myNode lndhub[27570]: 2021-03-25T12:41:42.314Z : info: [/addinvoice] : ["995f86c8-0eed-4510-8b02-70337ce43313"] Mar 25 07:41:42 myNode lndhub[27570]: f8f2bbf3-4f63-4272-b341-535363e18dca ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:42 +0000] "GET /balance HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:42 myNode lndhub[27570]: 2021-03-25T12:41:42.126Z : info: [/balance] : ["f8f2bbf3-4f63-4272-b341-535363e18dca","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:42 myNode lndhub[27570]: 2021-03-25T12:41:42.124Z : info: [/balance] : ["f8f2bbf3-4f63-4272-b341-535363e18dca"] Mar 25 07:41:28 myNode lndhub[27570]: 6b098db5-4b4a-4f07-a78e-fabea38503eb ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:28 +0000] "GET /getuserinvoices HTTP/1.1" 200 91047 "-" "okhttp/3.12.1" Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.901Z : info: [/getuserinvoices] : ["6b098db5-4b4a-4f07-a78e-fabea38503eb","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.900Z : info: [/getuserinvoices] : ["6b098db5-4b4a-4f07-a78e-fabea38503eb"] Mar 25 07:41:27 myNode lndhub[27570]: c974d46b-fb6f-4f39-b7f3-676ea5fcb356 ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:27 +0000] "GET /getpending HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.794Z : info: [/getpending] : ["c974d46b-fb6f-4f39-b7f3-676ea5fcb356","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.792Z : info: [/getpending] : ["c974d46b-fb6f-4f39-b7f3-676ea5fcb356"] Mar 25 07:41:27 myNode lndhub[27570]: 48728f02-f848-427b-b1ff-fb67ce8315ef ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:27 +0000] "GET /gettxs?limit=10&offset=0 HTTP/1.1" 304 - "-" "okhttp/3.12.1" Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.675Z : info: [/gettxs] : ["48728f02-f848-427b-b1ff-fb67ce8315ef","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:27 myNode lndhub[27570]: 2021-03-25T12:41:27.674Z : info: [/gettxs] : ["48728f02-f848-427b-b1ff-fb67ce8315ef"] Mar 25 07:41:27 myNode lndhub[27570]: bf016a0d-90e2-47f4-9350-d7929984cd9d ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:27 +0000] "GET /balance HTTP/1.1" 200 35 "-" "okhttp/3.12.1" Mar 25 07:41:26 myNode lndhub[27570]: 2021-03-25T12:41:26.715Z : info: [/balance] : ["bf016a0d-90e2-47f4-9350-d7929984cd9d","userid: 3892dfb6376847476fea71f4b783eb08fc16963fe8a6929e"] Mar 25 07:41:26 myNode lndhub[27570]: 2021-03-25T12:41:26.714Z : info: [/balance] : ["bf016a0d-90e2-47f4-9350-d7929984cd9d"] Mar 25 07:41:26 myNode lndhub[27570]: 268ebad1-ad3b-4c65-9d1a-d01e9a274eac ::ffff:107.115.44.161 - - [25/Mar/2021:12:41:26 +0000] "POST /auth?type=refresh_token HTTP/1.1" 200 118 "-" "okhttp/3.12.1" Mar 25 07:41:26 myNode lndhub[27570]: 2021-03-25T12:41:26.521Z : info: [/auth] : ["268ebad1-ad3b-4c65-9d1a-d01e9a274eac"] Mar 25 07:41:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:41:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:41:12 myNode lndhub[27570]: code: 8, Mar 25 07:41:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:41:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:41:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:41:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:41:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:41:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:41:12 myNode lndhub[27570]: code: 8, Mar 25 07:41:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:41:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:41:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:41:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:41:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:41:12 myNode lndhub[27570]: updated Mar 25 07:41:12 myNode lndhub[27570]: updateLightning() Mar 25 07:40:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:40:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:40:12 myNode lndhub[27570]: code: 8, Mar 25 07:40:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:40:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:40:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:40:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:40:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:40:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:40:12 myNode lndhub[27570]: code: 8, Mar 25 07:40:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:40:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:40:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:40:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:40:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:40:12 myNode lndhub[27570]: updated Mar 25 07:40:12 myNode lndhub[27570]: updateLightning() Mar 25 07:39:13 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:39:13 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:39:13 myNode lndhub[27570]: code: 8, Mar 25 07:39:13 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:39:13 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:39:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:39:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:39:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:39:13 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:39:13 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:39:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:39:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:39:12 myNode lndhub[27570]: code: 8, Mar 25 07:39:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:39:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:39:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:39:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:39:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:39:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:39:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:39:12 myNode lndhub[27570]: updated Mar 25 07:39:12 myNode lndhub[27570]: updateLightning() Mar 25 07:38:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:38:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:38:12 myNode lndhub[27570]: code: 8, Mar 25 07:38:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:38:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:38:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:38:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:38:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:38:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:38:12 myNode lndhub[27570]: code: 8, Mar 25 07:38:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:38:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:38:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:38:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:38:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:38:12 myNode lndhub[27570]: updated Mar 25 07:38:12 myNode lndhub[27570]: updateLightning() Mar 25 07:37:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:37:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:37:12 myNode lndhub[27570]: code: 8, Mar 25 07:37:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:37:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:37:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:37:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:37:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:37:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:37:12 myNode lndhub[27570]: code: 8, Mar 25 07:37:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:37:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:37:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:37:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:37:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:37:12 myNode lndhub[27570]: updated Mar 25 07:37:12 myNode lndhub[27570]: updateLightning() Mar 25 07:36:13 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:36:13 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:36:13 myNode lndhub[27570]: code: 8, Mar 25 07:36:13 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:36:13 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:36:13 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:36:13 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:36:13 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:36:13 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:36:13 myNode lndhub[27570]: code: 8, Mar 25 07:36:13 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:36:13 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:36:13 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:36:13 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:36:13 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:36:12 myNode lndhub[27570]: updated Mar 25 07:36:12 myNode lndhub[27570]: updateLightning() Mar 25 07:35:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:35:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:35:12 myNode lndhub[27570]: code: 8, Mar 25 07:35:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:35:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:35:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) Mar 25 07:35:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) Mar 25 07:35:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) Mar 25 07:35:12 myNode lndhub[27570]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) Mar 25 07:35:12 myNode lndhub[27570]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted Mar 25 07:35:12 myNode lndhub[27570]: metadata: Metadata { internalRepr: Map {}, options: {} } } Mar 25 07:35:12 myNode lndhub[27570]: details: 'Bandwidth exhausted', Mar 25 07:35:12 myNode lndhub[27570]: code: 8, Mar 25 07:35:12 myNode lndhub[27570]: at processTicksAndRejections (internal/process/task_queues.js:79:9) Mar 25 07:35:12 myNode lndhub[27570]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:249:24) Mar 25 07:35:12 myNode lndhub[27570]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)

godSaysHODL commented 3 years ago

it just failed again so I have fresh logs

Overtorment commented 3 years ago

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.

godSaysHODL commented 3 years ago

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.

It is weird, but I can assure you I'm hosting on a raspberry pi via myNodeBTC and not a cloud provider

As soon as I attempt to click into the lndhub HTML page after these errors are raised, it refuses to connect, kills lndhub, and restarts automatically. Do you think this is on the myNode side of things?

Overtorment commented 3 years ago

sorry for the late reply. is the problem still there..?

when it was introduced, in 1.3..? which version did you run before that? maybe I can take a look at the diff and spot some issues

xraid commented 3 years ago

// Some resource has been exhausted, perhaps a per-user quota, or perhaps the // entire file system is out of space. 'RESOURCE_EXHAUSTED': 8,

what does "df -h" say

maybe the 1 gb channel.db on 32bit systems

Overtorment commented 3 years ago

btw LND has built-in disk space check, and if there's no space on device it terminates safely.

xraid commented 3 years ago

do lncli addinvoice and lncli payinvoice work ?

godSaysHODL commented 3 years ago

During this bandwidth exhaustes event no, however going to the lndhub HTML page resets lndhub and it works again without this error about 2 minutes after that restart

xraid commented 3 years ago

free -m

maybe ram memory on your node machine is at peek ?

also what version LND is installed

lncli -v

godSaysHODL commented 3 years ago

v0.12.1 LND and ram is at 80.8% according to myNode performance boxes

xraid commented 3 years ago

can You try delete line 2 3 4 in config.js and restart LndHub

// bitcoind: { // rpc: 'http://login:password@1.1.1.1:8332/wallet/wallet.dat', // },

godSaysHODL commented 3 years ago

Not sure how to get to config.js on mynode

Any idea where that would be in the myNode filesystem?

xraid commented 3 years ago

i asked around since i am not familiar with MyNode . and Hamish says : "There may be exceptions but most apps have a directory under /opt/mynode/. LndHub has a directory, /opt/mynode/LndHub/ which looks like it contains the install. " so in /opt/mynode/LndHub/config.js comment out line 2 3 4 as shown above

then start LndHub and report back

xraid commented 3 years ago

You can also try this command and then start LndHub . this command besides comment out the bitcoin directive also creates a config.js.bak file with original content

at terminal commandline in MyNode :

// first read the file into terminal to se contents

cat /opt/mynode/LndHub/config.js

// then issue

sed -i'.bak' -e '/bitcoind/,/}/ s/^/\/\/ /' /opt/mynode/LndHub/config.js

// verify changes read the file into terminal to se contents again

cat /opt/mynode/LndHub/config.js

and now also there is a original file in /opt/mynode/LndHub/config.js.bak

start LndHub

godSaysHODL commented 3 years ago

I haven't tried that stuff, but today I did add two more gigs of virtual ram from the external drive. Will see if this makes a difference. At almost 80% ram before, now it's hovering around 60

Overtorment commented 3 years ago

hmm. configuring swap might help too.

godSaysHODL commented 3 years ago

Swap configured to max, still failing. Not sure why

godSaysHODL commented 3 years ago

Has anyone else had this problem yet (mynode users)

Overtorment commented 3 years ago

can you ask mynode support? this is big wtf: RESOURCE_EXHAUSTED: Bandwidth exhausted

tehelsper commented 3 years ago

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.

dm8try commented 3 years ago

Has anyone else had this problem yet (mynode users)

I'm having this problem, too. Blue Wallet fails to connect to MyNode, there are many error messages ("lnd failure ... bandwidth exhausted") in the LND hub log file.

No idea when it started, I've been having this issue since I first started playing with the lightning node on MyNode, around couple of weeks ago.

godSaysHODL commented 3 years ago

You can fix it temporarily by going to the http://mynode.local:3000

This will reboot it in about 1-2 minutes

godSaysHODL commented 3 years ago

This got worse in latest version. .31 Can't figure out how to restart it now

tehelsper commented 3 years ago

I've downgraded to LndHub version 1.2.0 and 1.3.0 and both of those versions seems to be working far better. After restarting LndHub with the new version, the updates immediately start to succeed.

Example: May 12 23:44:36 myNode lndhub[7924]: updateLightning() May 12 23:44:36 myNode lndhub[7924]: updated May 12 23:45:36 myNode lndhub[7924]: updateLightning() May 12 23:45:36 myNode lndhub[7924]: updated May 12 23:46:36 myNode lndhub[7924]: updateLightning() May 12 23:46:36 myNode lndhub[7924]: updated

How risky would it be to downgrade LndHub to version 1.3.0 for myNode users? I noticed the database schema doc had been updated, but I'm not very familiar with how compatible downgrades may be.

godSaysHODL commented 3 years ago

I'm gonna ask them to pop in here. Can you try a test wallet with 1-2 transactions upgrading and then downgrading

godSaysHODL commented 3 years ago

I wonder if the database would be deleted or just incompatible 🤔

tehelsper commented 3 years ago

I just noticed this issue was logged against v1.3.0 - it may still have issues, but in my test environment, it immediately improved the situation compared to v1.3.3.

I would guess it's just incompatible, but I'm not sure what the side-effects may be.

godSaysHODL commented 3 years ago

At 1.3.0 at least it would reboot and fix itself

godSaysHODL commented 3 years ago

Screenshot_20210512-221018

Got a response that may help in this screenshot^ I will try this. Can I edit config file easily from myNode SSH terminal?

xraid commented 3 years ago

at terminal commandline in MyNode :

// first read the file into terminal to se contents

cat /opt/mynode/LndHub/config.js

// then issue

sed -i'.bak' -e '/bitcoind/,/}/ s/^/\/\/ /' /opt/mynode/LndHub/config.js

// verify changes read the file into terminal to se contents again

cat /opt/mynode/LndHub/config.js

and now also there is a original file in /opt/mynode/LndHub/config.js.bak

start LndHub


se if problem exist after restart

i think it is some legacy code where lndhub uses bitcoind wallet while it could / should ? only use the LND wallet

on OSX i comment out bitcoind in config fixes errors at start and code has a legacy ? fallback import addr from bitcoind wallet if bitcoind is configured that it should not do since we only use LND wallet . could be legacy cruft ?

xraid commented 3 years ago

also try se if Your bitcoind wallet is activated

bitcoin-cli getbalance mine returns 0.00000000

while lncli walletbalance lncli listunspent has coins

Overtorment commented 3 years ago

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

updateDescribeGraph();
setInterval(updateDescribeGraph, 120000);
godSaysHODL commented 3 years ago

I commented out those lines using vim and restarted. It seems to work for now!!

as-schug commented 3 years ago

some more logs from LNDHUB and LND, as it tries to create an invoice. LND fails, but the invoice in LND is os

May 13 10:12:29 myNode lndhub[12187]: lnd failure: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted May 13 10:12:29 myNode lndhub[12187]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) May 13 10:12:29 myNode lndhub[12187]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:334:36) May 13 10:12:29 myNode lndhub[12187]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34) May 13 10:12:29 myNode lndhub[12187]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) May 13 10:12:29 myNode lndhub[12187]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24) May 13 10:12:29 myNode lndhub[12187]: at processTicksAndRejections (internal/process/task_queues.js:79:9) May 13 10:12:29 myNode lndhub[12187]: code: 8, May 13 10:12:29 myNode lndhub[12187]: details: 'Bandwidth exhausted', May 13 10:12:29 myNode lndhub[12187]: metadata: Metadata { internalRepr: Map {}, options: {} } } May 13 10:12:31 myNode lndhub[12187]: 2021-05-13T13:12:31.539Z : info: [/addinvoice] : ["0e8a4874-de1a-45e3-b354-351f697e5369"] May 13 10:12:31 myNode lndhub[12187]: 2021-05-13T13:12:31.543Z : info: [/addinvoice] : ["0e8a4874-de1a-45e3-b354-351f697e5369","userid: 113a49a3304790d6ca6ee8f95405b8d733ebfe2ee3b8093c"] 2021-05-13 10:12:31.605 [WRN] INVC: client=2 for invoice notifications missed an update, add_index=0, new add event index=185 2021-05-13 10:12:31.606 [WRN] INVC: client=0 for invoice notifications missed an update, add_index=0, new add event index=185 2021-05-13 10:12:31.606 [WRN] INVC: client=1 for invoice notifications missed an update, add_index=0, new add event index=185 2021-05-13 10:12:31.610 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: rpc error: code = Unavailable desc = transport is closing 2021-05-13 10:12:31.610 [INF] INVC: Cancelling invoice subscription for client=1 May 13 10:12:31 myNode lndhub[12187]: 0e8a4874-de1a-45e3-b354-351f697e5369 ::ffff:192.168.6.1 - - [13/May/2021:13:12:31 +0000] "POST /addinvoice HTTP/1.1" 200 46 "-" "okhttp/3.12.12" 2021-05-13 10:12:31.615 [ERR] RPCS: [/lnrpc.Lightning/SubscribeInvoices]: rpc error: code = Unavailable desc = transport is closing 2021-05-13 10:12:31.615 [INF] INVC: Cancelling invoice subscription for client=0 May 13 10:12:31 myNode lndhub[12187]: { Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted May 13 10:12:31 myNode lndhub[12187]: at Object.callErrorFromStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call.ts:81:24) May 13 10:12:31 myNode lndhub[12187]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client.ts:570:32) May 13 10:12:31 myNode lndhub[12187]: at Object.onReceiveStatus (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48) May 13 10:12:31 myNode lndhub[12187]: at process.nextTick (/opt/mynode/LndHub/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24) May 13 10:12:31 myNode lndhub[12187]: at processTicksAndRejections (internal/process/task_queues.js:79:9) May 13 10:12:31 myNode lndhub[12187]: code: 8, May 13 10:12:31 myNode lndhub[12187]: details: 'Bandwidth exhausted', May 13 10:12:31 myNode lndhub[12187]: metadata: Metadata { internalRepr: Map {}, options: {} } } May 13 10:12:31 myNode lndhub[12187]: Node NOT Exiting...

godSaysHODL commented 3 years ago

@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

as-schug commented 3 years ago

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!!"

godSaysHODL commented 3 years ago

Sweet! So that fix worked for you, too?

as-schug commented 3 years ago

Yes... Some tests worked just fine. Thank you again!!!

Overtorment commented 3 years ago

hmm, so if that was the source of problems... ill prepare a release where that functionality is disabled by default

dm8try commented 3 years ago

@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.

tehelsper commented 3 years ago

I timed the lncli version of that command and noticed something interesting. Getting the response took 17-20s on a RP4, but the acceptortimeout has a default value of 15s, which may be related. I can't find many examples of users setting it, but ti sounds like it's an RPC timeout type setting. I saw slightly different behavior after increasing it, but there were still failures.

@Overtorment Moving that to being off by default sounds great. Thanks!

Overtorment commented 3 years ago

released as https://github.com/BlueWallet/LndHub/releases/tag/v1.3.4

godSaysHODL commented 3 years ago

@tehelsper even with the commented out code, lndhub fails maybe once to twice per day. Luckily, with the commented code, it can be rebooted by doing simple application restart and waiting 20 seconds...

Any idea if we can add some code in myNode to detect "bandwidth exhausted" logs, and reboot the application automatically?

Unless 1.3.4 works flawlessly which I havent been able to try yet

tehelsper commented 3 years ago

Was that with the manual patch or with myNode version 0.2.32? I had one other change that might have helped a bit.

godSaysHODL commented 3 years ago

That was just with manual patch. I am doing the mynode upgrade today though.

godSaysHODL commented 3 years ago

Still been having the same issues with 1.3.4 👀

xraid commented 3 years ago

Did You try comment out the bitcoind in config ?

if not can You try and restart -- report back -- thanks

bitcoind is not used (needed) since new on-chain addrs is using LND's wallet for on-chain not bitcoind wallet and scanning bitcoind for addrs in watch is unnecessary since LND wallet is already up to date with regards its on-chain addr.

START bitcoind doc importaddress importaddress "address" ( "label" rescan p2sh ) Adds an address or script (in hex) that can be watched as if it were in your wallet but cannot be used to spend. Requires a new wallet backup. Note: This call can take over an hour to complete if rescan is true, during that time, other rpc calls may report that the imported address exists but related transactions are still missing, leading to temporarily incorrect/bogus balances and unspent outputs until rescan completes. If you have the full public key, you should call importpubkey instead of this. Hint: use importmulti to import more than one address. Note: If you import a non-standard raw script in hex form, outputs sending to it will be treated as change, and not show up in many RPCs. Note: Use “getwalletinfo” to query the scanning progress. END bitcoind doc

xraid commented 3 years ago

file : rpc.proto / SubscribeTransactions creates a uni-directional stream from the server to the client in which any newly discovered transactions relevant to the wallet are sent over. / rpc SubscribeTransactions (GetTransactionsRequest) returns (stream Transaction); end file : rpc.proto

above could be used instead of : if (config.bitcoind) return this._bitcoindrpc.request('importaddress', [address, address, false]);

meaning LNDHub is asking its LND wallet for tx hapening with regards to its on-chain addrs and do not need configure bitcoind