Full logs (cont.)
electrs logs
Attaching to electrs
electrs | [2022-01-13T00:20:02.741Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:03.744Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:04.752Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:05.755Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:06.757Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:07.760Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:08.762Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:09.765Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:10.767Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:11.770Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:12.772Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:13.775Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:14.777Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:15.780Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:16.785Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:17.787Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:18.793Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:19.796Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:20.798Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:21.801Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:22.803Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-01-13T00:20:23.805Z INFO electrs::daemon] waiting for RPC warmup: Loading P2P addresses…
electrs | [2022-01-13T00:20:27.703Z INFO electrs::daemon] waiting for 44 blocks to download (IBD)
electrs | [2022-01-13T00:20:50.377Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs | Error: electrs failed
electrs |
electrs | Caused by:
electrs | 0: bitcoind RPC polling failed
electrs | 1: daemon not available
electrs | 2: JSON-RPC error: transport error: Didn’t receive response data in time, timed out.
Tor logs
Attaching to umbrel_app_2_tor_1, umbrel_app_tor_1, tor, umbrel_app_3_tor_1
app_2_tor_1 | Jan 13 01:09:14.000 [warn] Received NETINFO cell with skewed time (OR:204.13.164.118:443): It seems that our clock is behind by 7 days, 20 hours, 16 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
app_2_tor_1 | Jan 13 01:09:14.000 [warn] Problem bootstrapping. Stuck at 30% (loading_status): Loading networkstatus consensus. (Clock skew -677809 in NETINFO cell from OR; CLOCK_SKEW; count 82; recommendation warn; host 24E2F139121D4394C54B5BCC368B3B411857C413 at 204.13.164.118:443)
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 42 connections have failed:
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 38 connections died in state connect()ing with SSL state (No SSL object)
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 4 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_2_tor_1 | Jan 13 01:09:14.000 [warn] Received directory with skewed time (DIRSERV:204.13.164.118:443): It seems that our clock is behind by 7 days, 20 hours, 16 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
app_2_tor_1 | Jan 13 01:09:14.000 [warn] Problem bootstrapping. Stuck at 30% (loading_status): Loading networkstatus consensus. (Clock skew -677809 in directory from DIRSERV; CLOCK_SKEW; count 83; recommendation warn; host ? at 204.13.164.118:443)
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 42 connections have failed:
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 38 connections died in state connect()ing with SSL state (No SSL object)
app_2_tor_1 | Jan 13 01:09:14.000 [warn] 4 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
tor | Jan 14 04:40:21.000 [warn] 107 connections have failed:
tor | Jan 14 04:40:21.000 [warn] 103 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
tor | Jan 14 04:40:21.000 [warn] 4 connections died in state connect()ing with SSL state (No SSL object)
tor | Jan 14 04:40:21.000 [warn] Our clock is 7 days, 20 hours, 19 minutes behind the time published in the consensus network status document (2022-01-22 01:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
tor | Jan 14 04:40:21.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 7 days, 20 hours, 19 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
tor | Jan 14 04:40:21.000 [warn] Problem bootstrapping. Stuck at 30% (loading_status): Loading networkstatus consensus. (Clock skew -677979 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 1074; recommendation warn; host ? at ?)
tor | Jan 14 04:40:21.000 [warn] 107 connections have failed:
tor | Jan 14 04:40:21.000 [warn] 103 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
tor | Jan 14 04:40:21.000 [warn] 4 connections died in state connect()ing with SSL state (No SSL object)
tor | Jan 14 04:40:21.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
app_3_tor_1 | Jan 14 01:17:42.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 0 circuits open. I’ve sent 199 kB and received 1010 kB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 63 connections with IPv4 and 0 with IPv6.
app_3_tor_1 | Jan 14 01:17:42.000 [notice] While bootstrapping, fetched this many bytes: 596835 (consensus network-status fetch)
app_3_tor_1 | Jan 14 01:17:42.000 [notice] Average packaged cell fullness: 67.403%. TLS write overhead: 18%
app_3_tor_1 | Jan 14 01:17:42.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
app_3_tor_1 | Jan 14 04:06:55.000 [warn] Our clock is 7 days, 19 hours, 53 minutes behind the time published in the consensus network status document (2022-01-22 00:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
app_3_tor_1 | Jan 14 04:06:55.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 7 days, 19 hours, 53 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
app_3_tor_1 | Jan 14 04:06:55.000 [warn] Problem bootstrapping. Stuck at 30% (loading_status): Loading networkstatus consensus. (Clock skew -676385 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 102; recommendation warn; host ? at ?)
app_3_tor_1 | Jan 14 04:06:55.000 [warn] 5 connections have failed:
app_3_tor_1 | Jan 14 04:06:55.000 [warn] 5 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_3_tor_1 | Jan 14 04:06:55.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
app_tor_1 | Jan 14 01:07:55.000 [warn] Our clock is 7 days, 19 hours, 52 minutes behind the time published in the consensus network status document (2022-01-21 21:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
app_tor_1 | Jan 14 01:07:55.000 [warn] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 7 days, 19 hours, 52 minutes, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
app_tor_1 | Jan 14 01:07:55.000 [warn] Problem bootstrapping. Stuck at 30% (loading_status): Loading networkstatus consensus. (Clock skew -676325 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 65; recommendation warn; host ? at ?)
app_tor_1 | Jan 14 01:07:55.000 [warn] 3 connections have failed:
app_tor_1 | Jan 14 01:07:55.000 [warn] 3 connections died in state handshaking (TLS) with SSL state error in HANDSHAKE
app_tor_1 | Jan 14 01:07:55.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
app_tor_1 | Jan 14 01:17:42.000 [notice] Heartbeat: Tor’s uptime is 1 day 0:00 hours, with 0 circuits open. I’ve sent 158 kB and received 1.48 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 42 connections with IPv4 and 0 with IPv6.
app_tor_1 | Jan 14 01:17:42.000 [notice] While bootstrapping, fetched this many bytes: 1203184 (consensus network-status fetch)
app_tor_1 | Jan 14 01:17:42.000 [notice] Average packaged cell fullness: 67.394%. TLS write overhead: 16%
app_tor_1 | Jan 14 01:17:42.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits.
App logs
bluewallet
lndhub_1 | https://github.com/browserslist/browserslist#browsers-data-updating
lndhub_1 | using config from env
lndhub_1 | using config {“rateLimit”:10000,“postRateLimit”:10000,“redis”:{“port”:6379,“host”:“10.21.21.31”,“family”:4,“password”:“moneyprintergobrrr”,“db”:0},“lnd”:{“url”:“10.21.21.9:10009”,“password”:""}}
lndhub_1 | updateDescribeGraph()
lndhub_1 | updateLightning()
lndhub_1 | 2022-01-13T00:19:46.435Z : info: [BOOTING UP] : “Listening on port 3008”
lndhub_1 | (node:45) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to ‘0’ makes TLS connections and HTTPS requests insecure by disabling certificate verification.
lndhub_1 | (node:45) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
lndhub_1 | lnd failure
lndhub_1 | Error: 14 UNAVAILABLE: No connection established
lndhub_1 | at Object.callErrorFromStatus (/lndhub/node_modules/@grpc/grpc-js/src/call.ts:81:24)
lndhub_1 | at Object.onReceiveStatus (/lndhub/node_modules/@grpc/grpc-js/src/client.ts:334:36)
lndhub_1 | at Object.onReceiveStatus (/lndhub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34)
lndhub_1 | at Object.onReceiveStatus (/lndhub/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
lndhub_1 | at /lndhub/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
lndhub_1 | at processTicksAndRejections (internal/process/task_queues.js:79:11) {
lndhub_1 | code: 14,
lndhub_1 | details: ‘No connection established’,
lndhub_1 | metadata: Metadata { internalRepr: Map {}, options: {} }
lndhub_1 | }
lndhub_1 | npm ERR! code ELIFECYCLE
lndhub_1 | npm ERR! errno 3
lndhub_1 | npm ERR! lndhub@1.3.3 start: babel-node index.js
lndhub_1 | npm ERR! Exit status 3
lndhub_1 | npm ERR!
lndhub_1 | npm ERR! Failed at the lndhub@1.3.3 start script.
lndhub_1 | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
lndhub_1 |
lndhub_1 | npm ERR! A complete log of this run can be found in:
lndhub_1 | npm ERR! /lndhub/.npm/_logs/2022-01-13T00_19_50_048Z-debug.log
btc-rpc-explorer
web_1 | 2022-01-14T05:02:59.585Z btcexp:app Verifying RPC connection…
web_1 | 2022-01-14T05:03:02.658Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {“request”:“getnetworkinfo”})
web_1 | 2022-01-14T05:03:02.658Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:02.659Z btcexp:error Error 32ugegdfsde: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {})
web_1 | 2022-01-14T05:03:02.659Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:02.659Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getblockchaininfo”}}, userData: [object Object] (json: {“request”:“getblockchaininfo”})
web_1 | 2022-01-14T05:03:02.659Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:29.589Z btcexp:app Verifying RPC connection…
web_1 | 2022-01-14T05:03:32.642Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {“request”:“getnetworkinfo”})
web_1 | 2022-01-14T05:03:32.643Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:32.643Z btcexp:error Error 32ugegdfsde: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {})
web_1 | 2022-01-14T05:03:32.643Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:32.644Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getblockchaininfo”}}, userData: [object Object] (json: {“request”:“getblockchaininfo”})
web_1 | 2022-01-14T05:03:32.644Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:03:59.594Z btcexp:app Verifying RPC connection…
web_1 | 2022-01-14T05:04:02.659Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {“request”:“getnetworkinfo”})
web_1 | 2022-01-14T05:04:02.659Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:04:02.660Z btcexp:error Error 32ugegdfsde: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getnetworkinfo”}}, userData: [object Object] (json: {})
web_1 | 2022-01-14T05:04:02.660Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
web_1 | 2022-01-14T05:04:02.660Z btcexp:error Error RpcError-001: Error: connect EHOSTUNREACH 10.21.21.8:8332, json: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332,“userData”:{“request”:“getblockchaininfo”}}, userData: [object Object] (json: {“request”:“getblockchaininfo”})
web_1 | 2022-01-14T05:04:02.661Z btcexp:errorVerbose Stack: Error: connect EHOSTUNREACH 10.21.21.8:8332
web_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
lightning-terminal
web_1 | 2022-01-20 20:15:07.205 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {mailbox.terminal.lightning.today:443 mailbox.terminal.lightning.today:443 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup mailbox.terminal.lightning.today on 127.0.0.11:53: read udp 127.0.0.1:56860->127.0.0.11:53: i/o timeout”. Reconnecting…
web_1 | 2022-01-20 20:16:18.981 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {pool.lightning.finance:12010 pool.lightning.finance:12010 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup pool.lightning.finance on 127.0.0.11:53: read udp 127.0.0.1:59088->127.0.0.11:53: i/o timeout”. Reconnecting…
web_1 | 2022-01-20 20:16:49.071 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {pool.lightning.finance:12010 pool.lightning.finance:12010 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup pool.lightning.finance on 127.0.0.11:53: read udp 127.0.0.1:51396->127.0.0.11:53: i/o timeout”. Reconnecting…
web_1 | 2022-01-20 20:16:58.369 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {mailbox.terminal.lightning.today:443 mailbox.terminal.lightning.today:443 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup mailbox.terminal.lightning.today on 127.0.0.11:53: read udp 127.0.0.1:56107->127.0.0.11:53: i/o timeout”. Reconnecting…
web_1 | 2022-01-20 20:17:14.770 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {swap.lightning.today:11010 swap.lightning.today:11010 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp: lookup swap.lightning.today on 127.0.0.11:53: read udp 127.0.0.1:48034->127.0.0.11:53: i/o timeout”. Reconnecting…
web_1 | 2022-01-13 00:19:18.240 [INF] SESS: Checking for schema update: latest_version=0, db_version=0
web_1 | 2022-01-13 00:19:18.243 [INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
web_1 | 2022-01-13 00:19:18.243 [INF] SESS: Mailbox RPC server listening on mailbox:c714e9944451f8040d5b2003bf05d55cdb88faf87ad107aa682ebdf0bac5d4c60815b78ced1b822585221d45767d5bc9fb1f5040df03910448e8ef46358053d0@mailbox.terminal.lightning.today:443
web_1 | 2022-01-13 00:19:18.253 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | 2022-01-13 00:19:18.484 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
web_1 | 2022-01-13 00:19:18.486 [INF] LITD: Listening for http on: [::]:3004
web_1 | 2022-01-13 00:19:18.490 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | ----------------------------------------------------------
web_1 | Lightning Terminal (LiT) by Lightning Labs
web_1 |
web_1 | Operating mode remote
web_1 | Node status locked
web_1 | Alias ??? (node is locked)
web_1 | Version ??? (node is locked)
web_1 | Web interface 127.0.0.1:8443, 0.0.0.0:3004 (open https://127.0.0.1:8443 or http://localhost:3004 in your browser)
web_1 | ----------------------------------------------------------
web_1 | 2022-01-13 00:19:18.697 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
web_1 | 2022-01-13 00:19:18.700 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | 2022-01-13 00:19:18.701 [INF] LNDC: Connected to lnd
web_1 | 2022-01-13 00:19:18.702 [WRN] GRPC: [core] grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | 2022-01-13 00:19:18.704 [ERR] LITD: Could not start subservers: error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”
web_1 | 2022-01-13 00:19:18.705 [INF] SGNL: Received shutdown request.
web_1 | 2022-01-13 00:19:18.705 [INF] SGNL: Shutting down…
web_1 | 2022-01-13 00:19:18.705 [INF] SGNL: Gracefully shutting down.
web_1 | error subscribing to lnd wallet state: lnd version incompatible, need at least v0.13.0-beta, got error on state subscription: rpc error: code = Unavailable desc = connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”
lnbits
Attaching to lnbits_web_1
web_1 | running migration tipjar.1
web_1 | /app/lnbits/app.py:60: RuntimeWarning: × The backend for LndWallet isn’t working properly: ‘<_InactiveRpcError of RPC that terminated with:
web_1 | status = StatusCode.UNKNOWN
web_1 | details = “wallet locked, unlock it to enable full RPC access”
web_1 | debug_error_string = “{“created”:”@1639740837.447188909",“description”:“Error received from peer ipv4:10.21.21.9:10009”,“file”:“src/core/lib/surface/call.cc”,“file_line”:1063,“grpc_message”:“wallet locked, unlock it to enable full RPC access”,“grpc_status”:2}"
web_1 | >’
web_1 | RuntimeWarning,
web_1 | [2021-12-17 11:33:57 +0000] [42] [INFO] Running on http://0.0.0.0:3007 (CTRL + C to quit)
web_1 | [2021-12-17 11:34:33 +0000] [41] [INFO] Running on http://0.0.0.0:3007 (CTRL + C to quit)
mempool
mariadb_1 | 2022-01-13 1:17:44 0 [Note] Server socket created on IP: ‘::’.
mariadb_1 | 2022-01-13 1:17:44 0 [Warning] ‘proxies_priv’ entry ‘@% root@f19e8c3af4eb’ ignored in --skip-name-resolve mode.
mariadb_1 | 2022-01-13 1:17:44 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2022-01-13 1:17:44 0 [Note] Added new Master_info ‘’ to hash table
mariadb_1 | 2022-01-13 1:17:44 0 [Note] mysqld: ready for connections.
mariadb_1 | Version: ‘10.5.12-MariaDB-1:10.5.12+maria~focal’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
mariadb_1 | 2022-01-13 1:17:44 0 [Note] InnoDB: Buffer pool(s) load completed at 220113 1:17:44
mariadb_1 | 2022-01-13 1:17:44 3 [Warning] Aborted connection 3 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)
api_1 | Jan 14 04:56:43 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 04:56:46 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 04:56:46 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 04:57:49 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 04:57:52 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 04:57:52 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 04:58:36 [51] DEBUG: Statistics cache created
api_1 | Jan 14 04:58:55 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 04:58:58 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 04:58:58 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 05:00:01 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 05:00:04 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 05:00:04 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 05:01:08 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 05:01:11 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 05:01:11 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 05:02:14 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 05:02:17 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 05:02:17 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
api_1 | Jan 14 05:03:20 [51] DEBUG: updateMempoolInfo: connect EHOSTUNREACH 10.21.21.8:8332
api_1 | Jan 14 05:03:23 [51] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | Jan 14 05:03:23 [51] DEBUG: {“errno”:“EHOSTUNREACH”,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.8”,“port”:8332}
ride-the-lightning
web_1 |
web_1 | [2022-01-13T01:38:58.364Z] INFO: RTLConf => Initial RTL Configuration Received.
web_1 |
web_1 | [2022-01-13T01:38:58.581Z] INFO: RTLConf => Updating Selected Node…
web_1 |
loop_1 | 2022-01-13 00:18:48.840 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
loop_1 | 2022-01-13 00:18:50.092 [INF] LNDC: Connected to lnd
loop_1 | 2022-01-13 00:18:50.858 [INF] LNDC: Waiting for lnd to unlock
loop_1 | loopd exited with an error: rpc error: code = DeadlineExceeded desc = latest connection error: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”
web_1 | [2022-01-13T01:38:58.584Z] INFO: RTLConf => Selected Node Updated.
web_1 |
web_1 | [2022-01-13T01:39:11.439Z] INFO: Authenticate => Authenticating User…
web_1 |
web_1 | [2022-01-13T01:39:11.441Z] ERROR: Authenticate => Invalid Password! Failed IP ::ffff:192.168.86.43: {“error”:“Invalid password.”}
web_1 |
web_1 | [2022-01-13T01:39:23.334Z] INFO: Authenticate => Authenticating User…
web_1 |
web_1 | [2022-01-13T01:39:23.338Z] INFO: Authenticate => User Authenticated.
web_1 |
web_1 | [2022-01-13T01:39:23.352Z] INFO: RTLConf => Getting RTL Configuration…
web_1 |
web_1 | [2022-01-13T01:39:23.354Z] INFO: RTLConf => RTL Configuration Received.
web_1 |
web_1 | [2022-01-13T01:39:23.381Z] INFO: RTLConf => Updating Selected Node…
web_1 |
web_1 | [2022-01-13T01:39:23.381Z] INFO: RTLConf => Selected Node Updated.
web_1 |
web_1 | [2022-01-13T01:39:23.491Z] INFO: GetInfo => Getting LND Node Information…
web_1 |
web_1 | [2022-01-13T01:39:26.610Z] ERROR: GetInfo => Get Info Error: {“name”:“RequestError”,“message”:“Error: connect EHOSTUNREACH 10.21.21.9:8080”,“cause”:{“errno”:-113,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.9”,“port”:8080},“error”:{“errno”:-113,“code”:“EHOSTUNREACH”,“syscall”:“connect”,“address”:“10.21.21.9”,“port”:8080},“options”:{“url”:“https://10.21.21.9:8080/v1/getinfo",“rejectUnauthorized”:false,“json”:true,“headers”:{},“method”:“GET”,“qs”:{},“simple”:true,“resolveWithFullResponse”:false,"transform2xxOnly”:false}}
sphinx-relay
sphinx-relay | => 2022-01-14 05:03:41 [lightning] reconnecting… attempt #32530
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:03:44 [lightning] reconnecting… attempt #32531
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:03:47 [lightning] reconnecting… attempt #32532
sphinx-relay | [lightning] [ ‘listChannels’ ]
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:03:50 [lightning] reconnecting… attempt #32533
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:03:54 [lightning] reconnecting… attempt #32534
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:03:57 [lightning] reconnecting… attempt #32535
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:00 [lightning] reconnecting… attempt #32536
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:03 [lightning] reconnecting… attempt #32537
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:06 [lightning] reconnecting… attempt #32538
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:09 [lightning] reconnecting… attempt #32539
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:12 [lightning] reconnecting… attempt #32540
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:15 [lightning] reconnecting… attempt #32541
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | [lightning] [ ‘listChannels’ ]
sphinx-relay | => 2022-01-14 05:04:18 [lightning] reconnecting… attempt #32542
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
sphinx-relay | => 2022-01-14 05:04:21 [lightning] reconnecting… attempt #32543
sphinx-relay | [lightning] ERROR Error: 14 UNAVAILABLE: failed to connect to all addresses
