# Node stuck on loading log in page **URL:** \ **Category:** Support and Troubleshooting\ **Created:** [April 10, 2024, 1:31pm UTC](https://community.umbrel.com/t/node-stuck-on-loading-log-in-page/16215 "2024-04-10T13:31:12Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![praisethesats1](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@praisethesats1](https://community.umbrel.com/u/praisethesats1)\ **Post date:** [April 10, 2024, 1:31pm UTC](https://community.umbrel.com/t/node-stuck-on-loading-log-in-page/16215/1 "2024-04-10T13:31:12Z")
![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/2X/0/0f52065e9f5b5b8e7acd3b2a6f1b122a7f98ad08.jpeg) ---
**Author:** ![praisethesats1](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@praisethesats1](https://community.umbrel.com/u/praisethesats1)\ **Post date:** [April 12, 2024, 1:44pm UTC](https://community.umbrel.com/t/node-stuck-on-loading-log-in-page/16215/2 "2024-04-12T13:44:42Z")
# Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sat Dec 9 03:53:33 2023 from fe80::1b0a:c5d0:b3b7:82c3%eth0 umbrel@umbrel:~ $ sudo ~/umbrel/scripts/debug [sudo] password for umbrel: # = Umbrel debug info = ## Umbrel version 0.5.4 ## Flashed OS version v0.5.4-patch-1 ## Raspberry Pi Model Revision : c03112 Serial : 1000000092127440 Model : Raspberry Pi 4 Model B Rev 1.2 ## Firmware May 9 2023 12:16:34 Copyright (c) 2012 Broadcom version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start) ## Temperature temp=54.5’C ## Throttling throttled=0x80000 ## Memory usage ``` total used free shared buff/cache available ``` Mem: 3.8G 2.1G 209M 190M 1.5G 1.4G Swap: 4.1G 1.7G 2.4G total: 54.8% system: 26.5% bitfeed: 14% mempool: 10.1% bitcoin: 2.9% electrs: 1.3% ## Memory monitor logs 2024-01-11 05:29:30 Warning memory usage at 91% 2024-01-11 06:47:32 Warning memory usage at 91% 2024-01-11 16:25:46 Warning memory usage at 91% 2024-01-12 10:12:08 Warning memory usage at 91% 2024-01-12 20:44:21 Warning memory usage at 91% 2024-01-13 08:10:34 Warning memory usage at 91% 2024-01-23 12:34:14 Warning memory usage at 91% 2024-01-27 20:24:14 Warning memory usage at 91% 2024-02-02 09:44:54 Warning memory usage at 91% 2024-02-03 16:06:30 Warning memory usage at 91% ## Filesystem information Filesystem Size Used Avail Use% Mounted on /dev/root 30G 30G 0 100% / /dev/sda1 916G 916G 0 100% /home/umbrel/umbrel ## Startup service logs – Logs begin at Fri 2024-04-12 13:19:16 UTC, end at Fri 2024-04-12 13:38:43 UTC. – – No entries – ## External storage service logs – Logs begin at Fri 2024-04-12 13:19:16 UTC, end at Fri 2024-04-12 13:38:43 UTC. – – No entries – ## External storage SD card update service logs – Logs begin at Fri 2024-04-12 13:19:16 UTC, end at Fri 2024-04-12 13:38:43 UTC. – – No entries – ## Karen logs ============================= Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/6636’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/1189’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/12179’: No space left on device GotGot signal: change-password karen is getting triggered! New password: Retype new password: passwd: Authentication token manipulation error passwd: password unchanged Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/30445’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/30921’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/29138’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/29814’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/25708’: No space left on device Got signal: backup karen is getting triggered! Deriving keys… Creating backup… mkdir: cannot create directory ‘/home/umbrel/umbrel/.backup/15464’: No space left on device ## Docker containers NAMES STATUS bitfeed\_web\_1 Up 3 months bitfeed\_app\_proxy\_1 Up 3 months bitfeed\_api\_1 Up 3 months bitcoin\_server\_1 Up 4 months electrs\_app\_1 Up 4 months bitcoin\_tor\_1 Up 4 months bitcoin\_bitcoind\_1 Restarting (1) 10 days ago bitcoin\_app\_proxy\_1 Up 4 months bitcoin\_i2pd\_daemon\_1 Up 2 months mempool\_app\_proxy\_1 Up 4 months mempool\_mariadb\_1 Up 4 months mempool\_api\_1 Up 4 months mempool\_web\_1 Up 4 months electrs\_tor\_1 Up 4 months electrs\_app\_proxy\_1 Up 4 months electrs\_electrs\_1 Restarting (1) 10 days ago nginx Up 4 months tor\_proxy Up 4 months manager Up 4 months dashboard Up 4 months auth Up 4 months ## Umbrel logs Attaching to manager manager | at authenticate (/app/node\_modules/passport/lib/middleware/authenticate.js:367:7) manager | at jwt (/app/middlewares/auth.js:150:5) manager | at Layer.handle [as handle\_request] (/app/node\_modules/express/lib/router/layer.js:95:5) manager | at next (/app/node\_modules/express/lib/router/route.js:137:13) manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:30 GMT] “POST /v1/account/refresh HTTP/1.0” 401 13 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:31 GMT] “GET /v1/account/registered HTTP/1.0” 200 19 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | [LND Seed Migration] Checking if seed should be migrated… manager | [LND Seed Migration] Lightning app not installed, skipping migration. manager | ::ffff:10.21.21.2 - admin [Wed, 10 Apr 2024 13:17:34 GMT] “POST /v1/account/login HTTP/1.0” 200 273 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | (node:28) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:3005 manager | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) manager | (node:28) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see [Command-line API | Node.js v25.2.1 Documentation](https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode)). (rejection id: 34) manager | (node:28) UnhandledPromiseRejectionWarning: Error: ENOSPC: no space left on device, write manager | (node:28) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see [Command-line API | Node.js v25.2.1 Documentation](https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode)). (rejection id: 35) manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:34 GMT] “GET /v1/account/info HTTP/1.0” 200 128 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:34 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:35 GMT] “GET /v1/system/is-umbrel-os HTTP/1.0” 200 4 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” manager | manager | umbrel-manager manager | ::ffff:10.21.21.2 - - [Wed, 10 Apr 2024 13:17:35 GMT] “GET /v1/account/info HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Safari/537.36” ## Tor Proxy logs Attaching to tor\_proxy tor\_proxy | Apr 01 21:51:41.000 [notice] While not bootstrapping, fetched this many bytes: 28909315 (consensus network-status fetch); 56327 (authority cert fetch); 104730780 (microdescriptor fetch) tor\_proxy | Apr 01 21:51:41.000 [notice] Average packaged cell fullness: 75.552%. TLS write overhead: 5% tor\_proxy | Apr 02 03:51:41.000 [notice] Heartbeat: Tor’s uptime is 115 days 0:00 hours, with 1 circuits open. I’ve sent 123.43 MB and received 270.75 MB. I’ve received 478 connections on IPv4 and 0 on IPv6. I’ve made 2761 connections with IPv4 and 0 with IPv6. tor\_proxy | Apr 02 03:51:41.000 [notice] While bootstrapping, fetched this many bytes: 701642 (consensus network-status fetch); 14104 (authority cert fetch); 12455389 (microdescriptor fetch) tor\_proxy | Apr 02 03:51:41.000 [notice] While not bootstrapping, fetched this many bytes: 28974940 (consensus network-status fetch); 56327 (authority cert fetch); 104730780 (microdescriptor fetch) tor\_proxy | Apr 02 03:51:41.000 [notice] Average packaged cell fullness: 75.550%. TLS write overhead: 5% tor\_proxy | Apr 02 09:51:41.000 [notice] Heartbeat: Tor’s uptime is 115 days 6:00 hours, with 0 circuits open. I’ve sent 123.62 MB and received 272.14 MB. I’ve received 479 connections on IPv4 and 0 on IPv6. I’ve made 2767 connections with IPv4 and 0 with IPv6. tor\_proxy | Apr 02 09:51:41.000 [notice] While bootstrapping, fetched this many bytes: 701642 (consensus network-status fetch); 14104 (authority cert fetch); 12455389 (microdescriptor fetch) tor\_proxy | Apr 02 09:51:41.000 [notice] While not bootstrapping, fetched this many bytes: 29027185 (consensus network-status fetch); 56327 (authority cert fetch); 105917272 (microdescriptor fetch) tor\_proxy | Apr 02 09:51:41.000 [notice] Average packaged cell fullness: 75.583%. TLS write overhead: 5% ## App logs bitcoin Attaching to bitcoin\_server\_1, bitcoin\_tor\_1, bitcoin\_bitcoind\_1, bitcoin\_app\_proxy\_1, bitcoin\_i2pd\_daemon\_1 i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t select next hop for M7gmwV-KRgCB~Xq89QmROPNc9NL~LNKzkxbjr0uveFo= i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t select next hop for VeXCyu9jnJRSimj22OjQ4OA~BJrKeTbWQ17OvOohvSY= i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t create outbound tunnel, no peers available i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t select next hop for cm5LTOu7yUMZaSSMIorWPZGtqDBztzgO9wQyzW64unU= i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t create inbound tunnel, no peers available i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t select next hop for VeXCyu9jnJRSimj22OjQ4OA~BJrKeTbWQ17OvOohvSY= i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t create outbound tunnel, no peers available i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t select next hop for M7gmwV-KRgCB~Xq89QmROPNc9NL~LNKzkxbjr0uveFo= i2pd\_daemon\_1 | 19:34:55@475/error - Tunnels: Can’t create inbound tunnel, no peers available bitcoind\_1 | Error: Settings file could not be written: bitcoind\_1 | - Error: Unable to open settings file /data/.bitcoin/settings.json.tmp for writing bitcoind\_1 | Error: Settings file could not be written: bitcoind\_1 | - Error: Unable to open settings file /data/.bitcoin/settings.json.tmp for writing bitcoind\_1 | Error: Settings file could not be written: bitcoind\_1 | - Error: Unable to open settings file /data/.bitcoin/settings.json.tmp for writing bitcoind\_1 | Error: Settings file could not be written: bitcoind\_1 | - Error: Unable to open settings file /data/.bitcoin/settings.json.tmp for writing bitcoind\_1 | Error: Settings file could not be written: bitcoind\_1 | - Error: Unable to open settings file /data/.bitcoin/settings.json.tmp for writing app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 2407b0d2084c … app\_proxy\_1 | Error: connect EHOSTUNREACH 10.21.21.4:3006 app\_proxy\_1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) { server\_1 | [WARNING] Invalid JSON detected in /bitcoin/.bitcoin/settings.json. Overwriting with empty JSON. server\_1 | settings.json backup created at /bitcoin/.bitcoin/settings.json.backup.1711314422374 server\_1 | [WARNING] Invalid JSON detected in /bitcoin/.bitcoin/settings.json. Overwriting with empty JSON. server\_1 | settings.json backup created at /bitcoin/.bitcoin/settings.json.backup.1711314482432 server\_1 | [WARNING] Invalid JSON detected in /bitcoin/.bitcoin/settings.json. Overwriting with empty JSON. server\_1 | settings.json backup created at /bitcoin/.bitcoin/settings.json.backup.1711314542470 server\_1 | [WARNING] Invalid JSON detected in /bitcoin/.bitcoin/settings.json. Overwriting with empty JSON. server\_1 | settings.json backup created at /bitcoin/.bitcoin/settings.json.backup.1711314602528 server\_1 | [WARNING] Invalid JSON detected in /bitcoin/.bitcoin/settings.json. Overwriting with empty JSON. server\_1 | settings.json backup created at /bitcoin/.bitcoin/settings.json.backup.1711314662574 tor\_1 | Apr 10 15:52:49.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 10 15:52:49.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 10 16:02:38.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 10 16:02:38.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 10 16:25:18.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 10 16:25:18.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 10 16:26:04.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 10 16:26:04.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 10 16:35:42.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 10 16:35:42.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later bitfeed Attaching to bitfeed\_web\_1, bitfeed\_app\_proxy\_1, bitfeed\_api\_1 api\_1 | :connection\_error api\_1 | :error: :ehostunreach api\_1 | 02:30:18.206 [error] :host: 10.21.21.8 api\_1 | :port: 28335 api\_1 | :connection\_error api\_1 | :error: :ehostunreach api\_1 | 02:30:18.207 [error] :host: 10.21.21.8 api\_1 | :port: 28333 api\_1 | :connection\_error api\_1 | :error: :ehostunreach app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | Validating token: 5a01482c4fe5 … app\_proxy\_1 | [HPM] WebSocket error: Error: read ECONNRESET app\_proxy\_1 | at TCP.onStreamRead (node:internal/stream\_base\_commons:217:20) { app\_proxy\_1 | errno: -104, app\_proxy\_1 | code: ‘ECONNRESET’, app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } web\_1 | 2024/03/21 19:58:41 [warn] 36#36: \*87 an upstream response is buffered to a temporary file /var/cache/nginx/proxy\_temp/8/02/0000000028 while reading upstream, client: 10.21.0.7, server: client, request: “GET /api/block/0000000000000000000203330f03dfbd1f8f2ac3cc37c4f33e606769f81162d1 HTTP/1.1”, upstream: “[http://10.21.0.6:8315/api/block/0000000000000000000203330f03dfbd1f8f2ac3cc37c4f33e606769f81162d1](http://10.21.0.6:8315/api/block/0000000000000000000203330f03dfbd1f8f2ac3cc37c4f33e606769f81162d1)”, host: “umbrel.local:8314”, referrer: “[http://umbrel.local:8314/](http://umbrel.local:8314/)” web\_1 | 10.21.0.7 - - [21/Mar/2024:19:58:41 +0000] “GET /api/block/0000000000000000000203330f03dfbd1f8f2ac3cc37c4f33e606769f81162d1 HTTP/1.1” 200 768912 “[http://umbrel.local:8314/](http://umbrel.local:8314/)” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “::ffff:192.168.1.25” web\_1 | 2024/03/21 20:12:06 [warn] 36#36: \*89 an upstream response is buffered to a temporary file /var/cache/nginx/proxy\_temp/9/02/0000000029 while reading upstream, client: 10.21.0.7, server: client, request: “GET /api/block/00000000000000000002829be33003a067c19fe3fd7b6d427b9fb2d2dacc73c7 HTTP/1.1”, upstream: “[http://10.21.0.6:8315/api/block/00000000000000000002829be33003a067c19fe3fd7b6d427b9fb2d2dacc73c7](http://10.21.0.6:8315/api/block/00000000000000000002829be33003a067c19fe3fd7b6d427b9fb2d2dacc73c7)”, host: “umbrel.local:8314”, referrer: “[http://umbrel.local:8314/](http://umbrel.local:8314/)” web\_1 | 10.21.0.7 - - [21/Mar/2024:20:12:06 +0000] “GET /api/block/00000000000000000002829be33003a067c19fe3fd7b6d427b9fb2d2dacc73c7 HTTP/1.1” 200 742989 “[http://umbrel.local:8314/](http://umbrel.local:8314/)” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “::ffff:192.168.1.25” web\_1 | 2024/03/21 20:16:32 [warn] 36#36: \*91 an upstream response is buffered to a temporary file /var/cache/nginx/proxy\_temp/0/03/0000000030 while reading upstream, client: 10.21.0.7, server: client, request: “GET /api/block/0000000000000000000356d53aaf7292bcb701ca72231ff8a40a1821a1f8ad2b HTTP/1.1”, upstream: “[http://10.21.0.6:8315/api/block/0000000000000000000356d53aaf7292bcb701ca72231ff8a40a1821a1f8ad2b](http://10.21.0.6:8315/api/block/0000000000000000000356d53aaf7292bcb701ca72231ff8a40a1821a1f8ad2b)”, host: “umbrel.local:8314”, referrer: “[http://umbrel.local:8314/](http://umbrel.local:8314/)” web\_1 | 10.21.0.7 - - [21/Mar/2024:20:16:32 +0000] “GET /api/block/0000000000000000000356d53aaf7292bcb701ca72231ff8a40a1821a1f8ad2b HTTP/1.1” 200 562988 “[http://umbrel.local:8314/](http://umbrel.local:8314/)” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “::ffff:192.168.1.25” web\_1 | 2024/03/21 20:23:02 [warn] 36#36: \*93 an upstream response is buffered to a temporary file /var/cache/nginx/proxy\_temp/1/03/0000000031 while reading upstream, client: 10.21.0.7, server: client, request: “GET /api/block/00000000000000000002a6a426c4324306c6116501bb217eaa7605d5ca6f5ad1 HTTP/1.1”, upstream: “[http://10.21.0.6:8315/api/block/00000000000000000002a6a426c4324306c6116501bb217eaa7605d5ca6f5ad1](http://10.21.0.6:8315/api/block/00000000000000000002a6a426c4324306c6116501bb217eaa7605d5ca6f5ad1)”, host: “umbrel.local:8314”, referrer: “[http://umbrel.local:8314/](http://umbrel.local:8314/)” web\_1 | 10.21.0.7 - - [21/Mar/2024:20:23:03 +0000] “GET /api/block/00000000000000000002a6a426c4324306c6116501bb217eaa7605d5ca6f5ad1 HTTP/1.1” 200 643149 “[http://umbrel.local:8314/](http://umbrel.local:8314/)” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “::ffff:192.168.1.25” web\_1 | 10.21.0.7 - - [21/Mar/2024:20:27:34 +0000] “GET /api/block/00000000000000000000d2e0af4ced4d33c7499caf6eac77826b439365d2f771 HTTP/1.1” 200 706832 “[http://umbrel.local:8314/](http://umbrel.local:8314/)” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “::ffff:192.168.1.25” web\_1 | 10.21.0.7 - - [21/Mar/2024:20:30:25 +0000] “GET /ws/txs HTTP/1.1” 101 50530878 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36” “-” electrs Attaching to electrs\_app\_1, electrs\_tor\_1, electrs\_app\_proxy\_1, electrs\_electrs\_1 app\_1 | \> umbrel-electrs@1.0.1 dev:backend app\_1 | \> npm run start -w umbrel-electrs-backend app\_1 | app\_1 | app\_1 | \> umbrel-electrs-backend@0.1.12 start app\_1 | \> node ./bin/www app\_1 | app\_1 | Sat, 09 Dec 2023 03:52:23 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9 app\_1 | Sat, 09 Dec 2023 03:52:23 GMT morgan deprecated default format: use combined format at app.js:28:9 app\_1 | Listening on port 3006 app\_proxy\_1 | yarn run v1.22.19 app\_proxy\_1 | $ node ./bin/www app\_proxy\_1 | [HPM] Proxy created: / → [http://10.21.22.4:3006](http://10.21.22.4:3006) app\_proxy\_1 | Waiting for 10.21.22.4:3006 to open… app\_proxy\_1 | Electrs is now ready… app\_proxy\_1 | Listening on port: 2102 electrs\_1 | 0: failed to open DB: /data/db/bitcoin electrs\_1 | 1: IO error: No space left on deviceWhile appending to file: /data/db/bitcoin/352772.sst: No space left on device electrs\_1 | Starting electrs 0.9.10 on aarch64 linux with Config { network: Bitcoin, db\_path: “/data/db/bitcoin”, daemon\_dir: “/data/.bitcoin”, daemon\_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon\_rpc\_addr: 10.21.21.8:8332, daemon\_p2p\_addr: 10.21.21.8:8333, electrum\_rpc\_addr: 0.0.0.0:50001, monitoring\_addr: 127.0.0.1:4224, wait\_duration: 10s, jsonrpc\_timeout: 15s, index\_batch\_size: 10, index\_lookup\_limit: None, reindex\_last\_blocks: 0, auto\_reindex: true, ignore\_mempool: false, sync\_once: false, disable\_electrum\_rpc: false, server\_banner: “Umbrel Electrs (0.9.10)”, signet\_magic: 3652501241, args: } electrs\_1 | [2024-04-02T11:56:22.426Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224 electrs\_1 | [2024-04-02T11:56:22.426Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001 electrs\_1 | Error: electrs failed electrs\_1 | electrs\_1 | Caused by: electrs\_1 | 0: failed to open DB: /data/db/bitcoin electrs\_1 | 1: IO error: No space left on deviceWhile appending to file: /data/db/bitcoin/352772.sst: No space left on device tor\_1 | Apr 11 18:43:05.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 11 18:43:05.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 11 18:50:24.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 11 18:50:24.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 11 19:00:39.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 11 19:00:39.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 11 19:28:33.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 11 19:28:33.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later tor\_1 | Apr 11 19:29:04.000 [warn] Error writing to “/tmp/.tor/state”: No space left on device tor\_1 | Apr 11 19:29:04.000 [warn] Unable to write state to file “/tmp/.tor/state”; will try again later mempool # Attaching to mempool\_app\_proxy\_1, mempool\_mariadb\_1, mempool\_api\_1, mempool\_web\_1 app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } app\_proxy\_1 | [HPM] Upgrading to WebSocket app\_proxy\_1 | [HPM] WebSocket error: Error: read ECONNRESET app\_proxy\_1 | at TCP.onStreamRead (node:internal/stream\_base\_commons:217:20) { app\_proxy\_1 | errno: -104, app\_proxy\_1 | code: ‘ECONNRESET’, app\_proxy\_1 | syscall: ‘read’ app\_proxy\_1 | } app\_proxy\_1 | [HPM] Client disconnected api\_1 | Apr 11 18:35:21 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:36:27 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:37:33 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:38:39 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:39:45 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:40:51 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:41:58 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:43:04 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:44:10 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. api\_1 | Apr 11 18:45:16 [94] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec. mariadb\_1 | 2023-12-09 3:52:05 0 [Note] Added new Master\_info ‘’ to hash table mariadb\_1 | 2023-12-09 3:52:05 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](http://mariadb.org) binary distribution mariadb\_1 | 2023-12-09 3:52:05 3 [Warning] Aborted connection 3 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication) mariadb\_1 | 2023-12-09 3:52:05 4 [Warning] Aborted connection 4 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.26’ (This connection closed normally without authentication) mariadb\_1 | 2023-12-09 3:52:07 0 [Note] InnoDB: Buffer pool(s) load completed at 231209 3:52:07 mariadb\_1 | 2024-03-25 1:53:52 6 [Warning] Aborted connection 6 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got timeout reading communication packets) mariadb\_1 | 2024-03-25 1:53:52 5 [Warning] Aborted connection 5 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got timeout reading communication packets) mariadb\_1 | 2024-03-30 11:54:22 7 [Warning] Aborted connection 7 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got timeout reading communication packets) mariadb\_1 | 2024-04-06 11:54:43 8 [Warning] Aborted connection 8 to db: ‘mempool’ user: ‘mempool’ host: ‘10.21.21.27’ (Got timeout reading communication packets) # ==== Result ==== The temperature of your Raspberry Pi is too high. We recommend either using a case that lowers the temperature of your Pi or a case with a builtin fan. umbrel@umbrel:~ $