Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- =====================
- = Umbrel debug info =
- =====================
- Umbrel version
- --------------
- 0.4.9
- Flashed OS version
- -----------------
- v0.4.9
- Raspberry Pi Model
- ------------------
- Revision : d03114
- Serial : 1000000031c9f137
- Model : Raspberry Pi 4 Model B Rev 1.4
- Firmware
- --------
- Oct 29 2021 10:47:33
- Copyright (c) 2012 Broadcom
- version b8a114e5a9877e91ca8f26d1a5ce904b2ad3cf13 (clean) (release) (start)
- Temperature
- -----------
- temp=42.3'C
- Throttling
- ----------
- throttled=0x0
- Memory usage
- ------------
- total used free shared buff/cache available
- Mem: 7.8G 588M 6.6G 9.0M 619M 7.1G
- Swap: 4.1G 0B 4.1G
- total: 7.5%
- system: 4.6%
- bitcoin: 1.7%
- lnd: 0.7%
- tor: 0.4%
- electrs: 0.1%
- Memory monitor logs
- -------------------
- 2021-12-09 12:35:32 Memory monitor running!
- 2021-12-09 15:31:18 Memory monitor running!
- Filesystem information
- ----------------------
- Filesystem Size Used Avail Use% Mounted on
- /dev/root 15G 3.0G 11G 22% /
- /dev/sda1 1.8T 5.6G 1.7T 1% /home/umbrel/umbrel
- Startup service logs
- --------------------
- Dec 09 15:31:21 umbrel umbrel startup[1059]: Creating umbrel_app_2_tor_1 ...
- Dec 09 15:31:21 umbrel umbrel startup[1059]: Creating dashboard ...
- Dec 09 15:31:21 umbrel umbrel startup[1059]: Creating umbrel_app_3_tor_1 ...
- Dec 09 15:31:21 umbrel umbrel startup[1059]: Creating electrs ...
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating electrs ... done
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating umbrel_app_3_tor_1 ... done
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating tor ... done
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating manager ...
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating umbrel_app_tor_1 ... done
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating umbrel_app_2_tor_1 ... done
- Dec 09 15:31:24 umbrel umbrel startup[1059]: Creating dashboard ... done
- Dec 09 15:31:26 umbrel umbrel startup[1059]: Creating manager ... done
- Dec 09 15:31:26 umbrel umbrel startup[1059]: Creating nginx ...
- Dec 09 15:31:26 umbrel umbrel startup[1059]: Creating lnd ...
- Dec 09 15:31:28 umbrel umbrel startup[1059]: Creating nginx ... done
- Dec 09 15:31:28 umbrel umbrel startup[1059]: Creating bitcoin ...
- Dec 09 15:31:28 umbrel umbrel startup[1059]: Creating lnd ... done
- Dec 09 15:31:29 umbrel umbrel startup[1059]: Creating bitcoin ... done
- Dec 09 15:31:29 umbrel umbrel startup[1059]: Creating middleware ...
- Dec 09 15:31:29 umbrel umbrel startup[1059]: Creating neutrino-switcher ...
- Dec 09 15:31:31 umbrel umbrel startup[1059]: Creating middleware ... done
- Dec 09 15:31:31 umbrel umbrel startup[1059]: Creating neutrino-switcher ... done
- Dec 09 15:31:32 umbrel umbrel startup[1059]: Removing status server iptables entry...
- Dec 09 15:31:32 umbrel umbrel startup[1059]: Removed existing iptables entry.
- Dec 09 15:31:32 umbrel umbrel startup[1059]: Starting installed apps...
- Dec 09 15:31:32 umbrel umbrel startup[1059]: Umbrel is now accessible at
- Dec 09 15:31:32 umbrel umbrel startup[1059]: http://umbrel.local
- Dec 09 15:31:32 umbrel umbrel startup[1059]: http://169.254.208.221
- Dec 09 15:31:32 umbrel systemd[1]: Started Umbrel Startup Service.
- External storage service logs
- -----------------------------
- -- Logs begin at Thu 2021-12-09 15:30:49 UTC, end at Thu 2021-12-09 19:31:06 UTC. --
- Dec 09 15:30:54 umbrel systemd[1]: Starting External Storage Mounter...
- Dec 09 15:30:54 umbrel external storage mounter[489]: Running external storage mount script...
- Dec 09 15:30:54 umbrel external storage mounter[489]: Found device "CT2000MX 500SSD1"
- Dec 09 15:30:54 umbrel external storage mounter[489]: Blacklisting USB device IDs against UAS driver...
- Dec 09 15:30:54 umbrel external storage mounter[489]: Rebinding USB drivers...
- Dec 09 15:30:54 umbrel external storage mounter[489]: Checking USB devices are back...
- Dec 09 15:30:54 umbrel external storage mounter[489]: Waiting for USB devices...
- Dec 09 15:30:55 umbrel external storage mounter[489]: Waiting for USB devices...
- Dec 09 15:30:56 umbrel external storage mounter[489]: Checking if the device is ext4...
- Dec 09 15:30:56 umbrel external storage mounter[489]: Yes, it is ext4
- Dec 09 15:30:57 umbrel external storage mounter[489]: Checking if device contains an Umbrel install...
- Dec 09 15:30:57 umbrel external storage mounter[489]: Yes, it contains an Umbrel install
- Dec 09 15:30:57 umbrel external storage mounter[489]: Bind mounting external storage over local Umbrel installation...
- Dec 09 15:30:57 umbrel external storage mounter[489]: Bind mounting external storage over local Docker data dir...
- Dec 09 15:30:57 umbrel external storage mounter[489]: Bind mounting external storage to /swap
- Dec 09 15:30:57 umbrel external storage mounter[489]: Bind mounting SD card root at /sd-card...
- Dec 09 15:30:57 umbrel external storage mounter[489]: Checking Umbrel root is now on external storage...
- Dec 09 15:30:58 umbrel external storage mounter[489]: Checking /var/lib/docker is now on external storage...
- Dec 09 15:30:58 umbrel external storage mounter[489]: Checking /swap is now on external storage...
- Dec 09 15:30:58 umbrel external storage mounter[489]: Setting up swapfile
- Dec 09 15:30:58 umbrel external storage mounter[489]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
- Dec 09 15:30:58 umbrel external storage mounter[489]: no label, UUID=88529693-091c-4651-8eb1-58cae7f8dac4
- Dec 09 15:30:58 umbrel external storage mounter[489]: Checking SD Card root is bind mounted at /sd-root...
- Dec 09 15:30:58 umbrel external storage mounter[489]: Starting external drive mount monitor...
- Dec 09 15:30:58 umbrel external storage mounter[489]: Mount script completed successfully!
- Dec 09 15:30:58 umbrel systemd[1]: Started External Storage Mounter.
- External storage SD card update service logs
- --------------------------------------------
- -- Logs begin at Thu 2021-12-09 15:30:49 UTC, end at Thu 2021-12-09 19:31:06 UTC. --
- Dec 09 15:31:18 umbrel systemd[1]: Starting External Storage SDcard Updater...
- Dec 09 15:31:18 umbrel external storage updater[976]: Checking if SD card Umbrel is newer than external storage...
- Dec 09 15:31:18 umbrel external storage updater[976]: No, SD version is not newer, exiting.
- Dec 09 15:31:18 umbrel systemd[1]: Started External Storage SDcard Updater.
- Karen logs
- ----------
- Stopping electrs ...
- Stopping umbrel_app_3_tor_1 ... done
- Stopping umbrel_app_2_tor_1 ... done
- Stopping middleware ... done
- Stopping umbrel_app_tor_1 ... done
- Stopping electrs ... done
- Stopping neutrino-switcher ... done
- Stopping lnd ... done
- Stopping bitcoin ... done
- Stopping nginx ... done
- Stopping dashboard ... done
- Stopping manager ... done
- Stopping tor ... done
- Removing middleware ...
- Removing neutrino-switcher ...
- Removing bitcoin ...
- Removing nginx ...
- Removing lnd ...
- Removing manager ...
- Removing umbrel_app_3_tor_1 ...
- Removing tor ...
- Removing umbrel_app_tor_1 ...
- Removing dashboard ...
- Removing umbrel_app_2_tor_1 ...
- Removing electrs ...
- Removing dashboard ... done
- Removing neutrino-switcher ... done
- Removing nginx ... done
- Removing tor ... done
- Removing bitcoin ... done
- Removing manager ... done
- Removing electrs ... done
- Removing middleware ... done
- Removing umbrel_app_2_tor_1 ... done
- Removing lnd ... done
- Removing umbrel_app_tor_1 ... done
- Removing umbrel_app_3_tor_1 ... done
- Removing network umbrel_main_network
- karen is running in /home/umbrel/umbrel/events
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
- Got signal:
- karen is getting triggered!
- ./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
- Got signal: backup
- karen is getting triggered!
- Deriving keys...
- Creating backup...
- No channel.backup file found, skipping backup...
- Docker containers
- -----------------
- NAMES STATUS
- neutrino-switcher Up 5 hours
- middleware Up 5 hours
- bitcoin Up 5 hours
- lnd Up 5 hours
- nginx Up 5 hours
- manager Up 5 hours
- electrs Up 5 hours
- umbrel_app_3_tor_1 Up 5 hours
- umbrel_app_2_tor_1 Up 5 hours
- dashboard Up 5 hours
- umbrel_app_tor_1 Up 5 hours
- tor Up 5 hours
- Umbrel logs
- -----------
- Attaching to middleware, manager
- manager |
- manager | umbrel-manager
- manager | Invalid JWT
- manager | /v1/external/price
- manager | NodeError: Invalid JWT
- manager | at /app/middlewares/auth.js:137:19
- manager | at allFailed (/app/node_modules/passport/lib/middleware/authenticate.js:107:18)
- manager | at attempt (/app/node_modules/passport/lib/middleware/authenticate.js:180:28)
- manager | at JwtStrategy.strategy.fail (/app/node_modules/passport/lib/middleware/authenticate.js:302:9)
- manager | at /app/node_modules/passport-jwt/lib/strategy.js:106:33
- manager | at /app/node_modules/jsonwebtoken/verify.js:133:14
- manager | at getSecret (/app/node_modules/jsonwebtoken/verify.js:90:14)
- manager | at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:94:10)
- manager | at Function.module.exports [as JwtVerifier] (/app/node_modules/passport-jwt/lib/verify_jwt.js:4:16)
- manager | at /app/node_modules/passport-jwt/lib/strategy.js:104:25
- manager | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 19:52:41 GMT] "GET /v1/external/price HTTP/1.0" 401 13 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- manager |
- manager | umbrel-manager
- manager | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 19:52:41 GMT] "GET /v1/system/storage HTTP/1.0" 200 89 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- manager |
- manager | umbrel-manager
- manager | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 19:52:41 GMT] "GET /v1/system/temperature HTTP/1.0" 200 2 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- manager |
- manager | umbrel-manager
- manager | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 20:04:03 GMT] "GET /v1/system/is-umbrel-os HTTP/1.0" 304 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- manager |
- manager | umbrel-manager
- manager | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 20:04:03 GMT] "GET /v1/system/memory HTTP/1.0" 200 84 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- middleware | NodeError: Invalid JWT
- middleware | at /app/middlewares/auth.js:38:19
- middleware | at allFailed (/app/node_modules/passport/lib/middleware/authenticate.js:107:18)
- middleware | at attempt (/app/node_modules/passport/lib/middleware/authenticate.js:180:28)
- middleware | at JwtStrategy.strategy.fail (/app/node_modules/passport/lib/middleware/authenticate.js:302:9)
- middleware | at /app/node_modules/passport-jwt/lib/strategy.js:106:33
- middleware | at /app/node_modules/jsonwebtoken/verify.js:133:14
- middleware | at getSecret (/app/node_modules/jsonwebtoken/verify.js:90:14)
- middleware | at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:94:10)
- middleware | at Function.module.exports [as JwtVerifier] (/app/node_modules/passport-jwt/lib/verify_jwt.js:4:16)
- middleware | at /app/node_modules/passport-jwt/lib/strategy.js:104:25
- middleware | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 20:04:02 GMT] "GET /v1/lnd/channel HTTP/1.0" 401 13 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- middleware |
- middleware | umbrel-middleware
- middleware | Invalid JWT
- middleware | /v1/lnd/transaction
- middleware | NodeError: Invalid JWT
- middleware | at /app/middlewares/auth.js:38:19
- middleware | at allFailed (/app/node_modules/passport/lib/middleware/authenticate.js:107:18)
- middleware | at attempt (/app/node_modules/passport/lib/middleware/authenticate.js:180:28)
- middleware | at JwtStrategy.strategy.fail (/app/node_modules/passport/lib/middleware/authenticate.js:302:9)
- middleware | at /app/node_modules/passport-jwt/lib/strategy.js:106:33
- middleware | at /app/node_modules/jsonwebtoken/verify.js:133:14
- middleware | at getSecret (/app/node_modules/jsonwebtoken/verify.js:90:14)
- middleware | at Object.module.exports [as verify] (/app/node_modules/jsonwebtoken/verify.js:94:10)
- middleware | at Function.module.exports [as JwtVerifier] (/app/node_modules/passport-jwt/lib/verify_jwt.js:4:16)
- middleware | at /app/node_modules/passport-jwt/lib/strategy.js:104:25
- middleware | ::ffff:10.21.21.2 - - [Thu, 09 Dec 2021 20:04:03 GMT] "GET /v1/lnd/transaction HTTP/1.0" 401 13 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 Safari/537.36"
- middleware |
- manager |
- manager | umbrel-manager
- middleware | umbrel-middleware
- Bitcoin Core logs
- -----------------
- Attaching to bitcoin
- bitcoin | 2021-12-09T18:51:45Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago)
- bitcoin | 2021-12-09T19:02:15Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago)
- bitcoin | 2021-12-09T19:04:33Z New outbound peer connected: version: 70015, blocks=713412, peer=37 (outbound-full-relay)
- bitcoin | 2021-12-09T19:05:31Z New outbound peer connected: version: 70016, blocks=713413, peer=39 (outbound-full-relay)
- bitcoin | 2021-12-09T19:05:33Z New outbound peer connected: version: 70016, blocks=713413, peer=40 (outbound-full-relay)
- bitcoin | 2021-12-09T19:12:45Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago)
- bitcoin | 2021-12-09T19:13:30Z New outbound peer connected: version: 70016, blocks=713416, peer=41 (outbound-full-relay)
- bitcoin | 2021-12-09T19:19:51Z Socks5() connect to 84.136.187.46:8333 failed: general failure
- bitcoin | 2021-12-09T19:20:06Z New outbound peer connected: version: 70015, blocks=713417, peer=42 (outbound-full-relay)
- bitcoin | 2021-12-09T19:20:12Z Synchronizing blockheaders, height: 227993 (~33.23%)
- bitcoin | 2021-12-09T19:21:30Z New outbound peer connected: version: 70016, blocks=713417, peer=43 (outbound-full-relay)
- bitcoin | 2021-12-09T19:23:15Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago)
- bitcoin | 2021-12-09T19:33:45Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago)
- bitcoin | 2021-12-09T19:34:58Z New outbound peer connected: version: 70016, blocks=713418, peer=44 (outbound-full-relay)
- bitcoin | 2021-12-09T19:36:21Z Synchronizing blockheaders, height: 229993 (~33.51%)
- bitcoin | 2021-12-09T19:37:06Z Synchronizing blockheaders, height: 231993 (~33.79%)
- bitcoin | 2021-12-09T19:38:52Z Synchronizing blockheaders, height: 233993 (~34.07%)
- bitcoin | 2021-12-09T19:39:32Z New outbound peer connected: version: 70016, blocks=713420, peer=45 (outbound-full-relay)
- bitcoin | 2021-12-09T19:39:34Z New outbound peer connected: version: 70015, blocks=713419, peer=46 (outbound-full-relay)
- bitcoin | 2021-12-09T19:39:39Z Socks5() connect to 114.108.130.140:8333 failed: general failure
- bitcoin | 2021-12-09T19:40:12Z Synchronizing blockheaders, height: 235993 (~34.35%)
- bitcoin | 2021-12-09T19:40:46Z Socks5() connect to 149.172.49.185:8333 failed: general failure
- bitcoin | 2021-12-09T19:42:18Z New outbound peer connected: version: 70016, blocks=713420, peer=48 (outbound-full-relay)
- bitcoin | 2021-12-09T19:44:05Z New outbound peer connected: version: 70016, blocks=713420, peer=49 (outbound-full-relay)
- bitcoin | 2021-12-09T19:44:15Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago)
- bitcoin | 2021-12-09T19:50:28Z New outbound peer connected: version: 70015, blocks=713420, peer=50 (outbound-full-relay)
- bitcoin | 2021-12-09T19:51:27Z New outbound peer connected: version: 70016, blocks=713420, peer=51 (outbound-full-relay)
- bitcoin | 2021-12-09T19:52:03Z New outbound peer connected: version: 70015, blocks=713420, peer=52 (outbound-full-relay)
- bitcoin | 2021-12-09T19:54:45Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago)
- bitcoin | 2021-12-09T20:00:42Z New outbound peer connected: version: 70015, blocks=713420, peer=53 (outbound-full-relay)
- LND logs
- --------
- Attaching to lnd
- lnd | 2021-12-09 15:31:45.084 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 15:31:47.814 [INF] LNWL: The wallet has been unlocked without a time limit
- lnd | 2021-12-09 15:31:47.816 [INF] CHRE: LightningWallet opened
- lnd | 2021-12-09 15:31:47.820 [INF] SRVR: Proxying all network traffic via Tor (stream_isolation=false)! NOTE: Ensure the backend node is proxying over Tor as well
- lnd | 2021-12-09 15:31:47.820 [INF] TORC: Starting tor controller
- lnd | 2021-12-09 15:31:47.824 [INF] HSWC: Cleaning circuits from disk for closed channels
- lnd | 2021-12-09 15:31:47.825 [INF] HSWC: Finished cleaning: no closed channels found, no actions taken.
- lnd | 2021-12-09 15:31:47.825 [INF] HSWC: Restoring in-memory circuit state from disk
- lnd | 2021-12-09 15:31:47.826 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
- lnd | 2021-12-09 15:31:47.835 [INF] LTND: Channel backup proxy channel notifier starting
- lnd | 2021-12-09 15:31:47.835 [INF] ATPL: Instantiating autopilot with active=false, max_channels=5, allocation=0.600000, min_chan_size=20000, max_chan_size=16777215, private=false, min_confs=1, conf_target=3
- lnd | 2021-12-09 15:31:47.836 [INF] LTND: We're not running within systemd
- lnd | 2021-12-09 15:31:47.836 [INF] LTND: Waiting for chain backend to finish sync, start_height=0
- lnd | 2021-12-09 15:33:29.489 [INF] BTCN: DNS discovery failed on seed x49.seed.bitcoin.sipa.be: tor host is unreachable
- lnd | 2021-12-09 15:33:29.490 [INF] BTCN: DNS discovery failed on seed x49.seed.bitcoinstats.com: tor host is unreachable
- lnd | 2021-12-09 15:33:29.490 [INF] BTCN: DNS discovery failed on seed x49.seed.bitcoin.jonasschnelli.ch: tor host is unreachable
- lnd | 2021-12-09 15:33:29.490 [INF] BTCN: DNS discovery failed on seed seed.bitnodes.io: tor host is unreachable
- lnd | 2021-12-09 15:33:29.490 [INF] BTCN: DNS discovery failed on seed dnsseed.bitcoin.dashjr.org: tor host is unreachable
- lnd | 2021-12-09 15:33:29.490 [INF] BTCN: DNS discovery failed on seed x49.dnsseed.bluematt.me: tor host is unreachable
- lnd | 2021-12-09 15:50:30.733 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 16:27:34.582 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 16:46:06.506 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 17:04:38.431 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp 35.190.38.75:443: i/o timeout
- lnd | 2021-12-09 17:23:10.356 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 17:41:42.281 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 18:00:14.204 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 18:37:18.054 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 19:14:21.904 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 19:32:53.828 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- lnd | 2021-12-09 19:51:25.752 [ERR] LNWL: unable to query web api for fee response: Get "https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json": dial tcp: i/o timeout
- electrs logs
- --------
- Attaching to electrs
- electrs | [2021-12-09T20:03:39.472Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:40.475Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:41.478Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:42.481Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:43.484Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:44.486Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:45.489Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:46.496Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:47.503Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:48.508Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:49.513Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:50.519Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:51.524Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:52.529Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:53.535Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:54.540Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:55.544Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:56.550Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:57.554Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:58.559Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:03:59.565Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:00.573Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:01.576Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:02.578Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:03.581Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:04.584Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:05.588Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:06.591Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:07.594Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- electrs | [2021-12-09T20:04:08.597Z INFO electrs::daemon] waiting for 235993 blocks to download (IBD)
- Tor logs
- --------
- Attaching to umbrel_app_3_tor_1, umbrel_app_2_tor_1, umbrel_app_tor_1, tor
- tor | Dec 09 18:32:22.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 928s after 18 timeouts and 582 buildtimes.
- tor | Dec 09 18:39:31.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish.
- tor | Dec 09 18:51:59.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [149 similar message(s) suppressed in last 780 seconds]
- tor | Dec 09 19:19:00.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [51 similar message(s) suppressed in last 1620 seconds]
- tor | Dec 09 19:19:51.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
- tor | Dec 09 19:33:32.000 [notice] We'd like to launch a circuit to handle a connection, but we already have 32 general-purpose client circuits pending. Waiting until some finish. [58 similar message(s) suppressed in last 900 seconds]
- tor | Dec 09 19:39:39.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
- tor | Dec 09 19:40:44.000 [notice] Extremely large value for circuit build timeout: 1051s. Assuming clock jump. Purpose 14 (Measuring circuit timeout)
- tor | Dec 09 19:40:46.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.
- tor | Dec 09 19:50:26.000 [notice] Guard rinderwahnRelay9L ($9288B75B5FF8861EFF32A6BE8825CC38A4F9F8C2) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 142/203. Use counts are 69/84. 170 circuits completed, 24 were unusable, 4 collapsed, and 207 timed out. For reference, your timeout cutoff is 495 seconds.
- app_2_tor_1 | Dec 09 17:49:58.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_2_tor_1 | Dec 09 17:50:11.000 [notice] Guard cubieserver ($BAE10387321FDD3279EA44320720B919777FE640) is failing to carry more streams on its circuits than usual. Most likely this means the Tor network is overloaded or your network connection is poor. Use counts are 43/62. Success counts are 62/167. 84 circuits completed, 19 were unusable, 3 collapsed, and 212 timed out. For reference, your timeout cutoff is 668 seconds.
- app_2_tor_1 | Dec 09 17:52:00.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 113 buildtimes.
- app_2_tor_1 | Dec 09 18:05:08.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_2_tor_1 | Dec 09 18:15:46.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_2_tor_1 | Dec 09 18:16:18.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 181 buildtimes.
- app_2_tor_1 | Dec 09 18:19:50.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 120s after 18 timeouts and 69 buildtimes.
- app_2_tor_1 | Dec 09 18:26:20.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 240s after 18 timeouts and 55 buildtimes.
- app_2_tor_1 | Dec 09 19:23:19.000 [warn] Guard Eigentor ($D447D8180D5FB67D0E3AD08AC0A123EF943D84D4) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 100/200. Use counts are 77/97. 116 circuits completed, 16 were unusable, 0 collapsed, and 192 timed out. For reference, your timeout cutoff is 155 seconds.
- app_2_tor_1 | Dec 09 19:25:00.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 123s after 18 timeouts and 159 buildtimes.
- app_3_tor_1 | Dec 09 17:57:11.000 [warn] Guard gGDHjdcC6zAlM8k08lY ($D405FCCF06ADEDF898DF2F29C9348DCB623031BA) is failing to carry an extremely large amount of streams on its circuits. This could indicate a route manipulation attack, network overload, bad local network connectivity, or a bug. Use counts are 44/101. Success counts are 217/299. 278 circuits completed, 61 were unusable, 0 collapsed, and 347 timed out. For reference, your timeout cutoff is 60 seconds.
- app_3_tor_1 | Dec 09 18:08:31.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_3_tor_1 | Dec 09 18:16:02.000 [warn] Guard masterchief ($99EC64FE9EF0E0ECEC3E125A2327C2779C1E7947) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 105/211. Use counts are 68/99. 143 circuits completed, 31 were unusable, 7 collapsed, and 227 timed out. For reference, your timeout cutoff is 130 seconds.
- app_3_tor_1 | Dec 09 18:16:03.000 [notice] Guard masterchief ($99EC64FE9EF0E0ECEC3E125A2327C2779C1E7947) is failing to carry more streams on its circuits than usual. Most likely this means the Tor network is overloaded or your network connection is poor. Use counts are 68/99. Success counts are 106/233. 144 circuits completed, 31 were unusable, 7 collapsed, and 227 timed out. For reference, your timeout cutoff is 130 seconds.
- app_3_tor_1 | Dec 09 18:18:41.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 130s after 18 timeouts and 445 buildtimes.
- app_3_tor_1 | Dec 09 18:19:59.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 261s after 18 timeouts and 26 buildtimes.
- app_3_tor_1 | Dec 09 18:23:15.000 [notice] Guard gGDHjdcC6zAlM8k08lY ($D405FCCF06ADEDF898DF2F29C9348DCB623031BA) is failing to carry more streams on its circuits than usual. Most likely this means the Tor network is overloaded or your network connection is poor. Use counts are 50/83. Success counts are 143/189. 177 circuits completed, 34 were unusable, 0 collapsed, and 440 timed out. For reference, your timeout cutoff is 521 seconds.
- app_3_tor_1 | Dec 09 18:24:54.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 233s after 18 timeouts and 103 buildtimes.
- app_3_tor_1 | Dec 09 18:26:14.000 [warn] Guard masterchief ($99EC64FE9EF0E0ECEC3E125A2327C2779C1E7947) is failing to carry an extremely large amount of streams on its circuits. This could indicate a route manipulation attack, network overload, bad local network connectivity, or a bug. Use counts are 38/118. Success counts are 115/261. 205 circuits completed, 88 were unusable, 2 collapsed, and 164 timed out. For reference, your timeout cutoff is 712 seconds.
- app_3_tor_1 | Dec 09 19:18:29.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 117 buildtimes.
- app_tor_1 | Dec 09 17:24:16.000 [notice] Guard cyrexlinuz ($73D5E9C3C85A36EB3C1A6A23C2FF00BF7FE03446) is failing to carry more streams on its circuits than usual. Most likely this means the Tor network is overloaded or your network connection is poor. Use counts are 15/25. Success counts are 20/44. 30 circuits completed, 10 were unusable, 0 collapsed, and 178 timed out. For reference, your timeout cutoff is 1187 seconds.
- app_tor_1 | Dec 09 17:45:55.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_tor_1 | Dec 09 17:45:55.000 [notice] Our circuit 0 (id: 1088) died due to an invalid selected path, purpose Hidden service: Establishing introduction point. This may be a torrc configuration issue, or a bug.
- app_tor_1 | Dec 09 17:46:06.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_tor_1 | Dec 09 17:46:20.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_tor_1 | Dec 09 17:50:28.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
- app_tor_1 | Dec 09 18:24:48.000 [notice] Guard cyrexlinuz ($73D5E9C3C85A36EB3C1A6A23C2FF00BF7FE03446) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 104/151. Use counts are 75/101. 130 circuits completed, 26 were unusable, 0 collapsed, and 236 timed out. For reference, your timeout cutoff is 993 seconds.
- app_tor_1 | Dec 09 18:24:50.000 [warn] Guard cyrexlinuz ($73D5E9C3C85A36EB3C1A6A23C2FF00BF7FE03446) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 105/211. Use counts are 75/101. 131 circuits completed, 26 were unusable, 0 collapsed, and 236 timed out. For reference, your timeout cutoff is 1001 seconds.
- app_tor_1 | Dec 09 19:23:23.000 [warn] parse error: Malformed object: missing object end line
- app_tor_1 | Dec 09 19:23:23.000 [warn] Unparseable microdescriptor found in download or generated string
- ================
- ==== Result ====
- ================
- The debug script did not automatically detect any issues with your Umbrel.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement