# Stuck on new update?

**URL:** <https://community.umbrel.com/t/stuck-on-new-update/2354>\
**Category:** Support and Troubleshooting\
**Created:** [August 5, 2021, 4:48pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354 "2021-08-05T16:48:40Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![zcain79](https://avatars.discourse-cdn.com/v4/letter/z/3bc359/32.png) [@zcain79](https://community.umbrel.com/u/zcain79)\
**Post date:** [August 5, 2021, 4:48pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/1 "2021-08-05T16:48:40Z")

</div>

So i clicked on the new update and i’m stuck half way through i guess. The status bar has been on about 2/3’s for about 20-25 minutes now. Anyone know how long this should take and whether i should be worried or what i should do?

---

<div class="post-metadata">

**Author:** ![Rdodge3](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rdodge3](https://community.umbrel.com/u/Rdodge3)\
**Post date:** [August 5, 2021, 5:43pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/2 "2021-08-05T17:43:40Z")

</div>

Having some what similar issue, my update completed but now the node has said syncing for 30 minutes and I cant view my balances.

 ![umbrel](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/9410ed19e8e0c2933d215f1ba0caa8384d1164d7.jpeg)

Seeing this in the logs..

## bitcoin | 2021-08-05T17:40:34Z Verifying last 6 blocks at level 3 bitcoin | 2021-08-05T17:40:34Z [0%]…LevelDB read failure: Corruption: not an sstable (bad magic number) bitcoin | 2021-08-05T17:40:35Z Fatal LevelDB error: Corruption: not an sstable (bad magic number) bitcoin | 2021-08-05T17:40:35Z You can use -debug=leveldb to get more complete diagnostic messages bitcoin | 2021-08-05T17:40:35Z Fatal LevelDB error: Corruption: not an sstable (bad magic number) bitcoin | 2021-08-05T17:40:35Z : Error opening block database. bitcoin | Please restart with -reindex or -reindex-chainstate to recover. bitcoin | 2021-08-05T17:40:35Z Aborted block database rebuild. Exiting. bitcoin | 2021-08-05T17:40:35Z Shutdown: In progress… bitcoin | : Error opening block database. bitcoin | Please restart with -reindex or -reindex-chainstate to recover. . . . . LND logs

## Attaching to lnd lnd | 2021-08-05 17:37:43.828 [INF] LTND: Opening bbolt database, sync\_freelist=false, auto\_compact=false lnd | panic: freepages: failed to get all reachable pages (page 3846: multiple references) . . . . TOR logs

.tor | Aug 05 17:31:15.000 [warn] Guard frantz ($81F59E8936D0B2105182E4B8200AC07D9274961F) 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 200/401. Use counts are 162/162. 200 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.  
tor | Aug 05 17:31:27.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 252 buildtimes.

---

<div class="post-metadata">

**Author:** ![zcain79](https://avatars.discourse-cdn.com/v4/letter/z/3bc359/32.png) [@zcain79](https://community.umbrel.com/u/zcain79)\
**Post date:** [August 5, 2021, 6:27pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/3 "2021-08-05T18:27:25Z")

</div>

Mine finally finished. Took a while, but it was just me being impatient. My Umbrel is syncing fine. Maybe a little slow to respond at first. But that’s probably from catching up anything it missed during the update. I assume anyway.

---

<div class="post-metadata">

**Author:** ![recyclepanda](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@recyclepanda](https://community.umbrel.com/u/recyclepanda)\
**Post date:** [August 5, 2021, 10:42pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/4 "2021-08-05T22:42:22Z")

</div>

Also stuck here - although there might be some deeper issues since I’ve had some unclean docker shutdowns and whatnot, partially from making Umbrel a service on my VM.

If worse comes to worst, whats the best way to “reinstall”?

Taking a guess:

- Installing another copy of Umbrel in another location on the drive
- Use the start script to initialize umbrel
- Stopping Umbrel, and copying over bitcoin & lnd directories (to move over blockchain & lnd channels)
- ???

---

<div class="post-metadata">

**Author:** ![zcain79](https://avatars.discourse-cdn.com/v4/letter/z/3bc359/32.png) [@zcain79](https://community.umbrel.com/u/zcain79)\
**Post date:** [August 5, 2021, 11:22pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/5 "2021-08-05T23:22:22Z")

</div>

Mine took about an hour or so, give or take, to finish after hitting the point of ‘removing old containers’. I panicked too. lol Not sure how long you’re up to now, but i would say give it a bit.

---

<div class="post-metadata">

**Author:** ![recyclepanda](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@recyclepanda](https://community.umbrel.com/u/recyclepanda)\
**Post date:** [August 6, 2021, 3:22am UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/6 "2021-08-06T03:22:17Z")

</div>

Yep i’m stuck! I think i effed it up bad!

Tried stopping umbrel, and restarting after a few hours, but still stuck here.

Any advice on how to re-install?

![image](https://canada1.discourse-cdn.com/flex030/uploads/getumbrel/original/1X/519900faa319ce0fc08a2ef9b2e8835e749cf257.png)

---

<div class="post-metadata">

**Author:** ![Rdodge3](https://avatars.discourse-cdn.com/v4/letter/r/c89c15/32.png) [@Rdodge3](https://community.umbrel.com/u/Rdodge3)\
**Post date:** [August 6, 2021, 3:33am UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/7 "2021-08-06T03:33:51Z")

</div>

flash the microsd card and restore from your codes I suppose?

---

<div class="post-metadata">

**Author:** ![recyclepanda](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@recyclepanda](https://community.umbrel.com/u/recyclepanda)\
**Post date:** [August 6, 2021, 4:30am UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/8 "2021-08-06T04:30:36Z")

</div>

On a Debian Proxmox VM here, not a Rasperry Pi!

I’m not super familiar with the inner working of docker containers. Would it be OK to install umbrel in another directory, and then move the bitcoin/lnd directories in (making sure to never run both instances)

---

<div class="post-metadata">

**Author:** ![zcain79](https://avatars.discourse-cdn.com/v4/letter/z/3bc359/32.png) [@zcain79](https://community.umbrel.com/u/zcain79)\
**Post date:** [August 6, 2021, 4:07pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/9 "2021-08-06T16:07:04Z")

</div>

Not sure if this will point you in the right direction, but try Twitter. Tweet them or one of the devs. They almost had to walk me through something like this. Mine was just being slow and i was impatient though. They usually reach back out within a few hours or sooner.

---

<div class="post-metadata">

**Author:** ![recyclepanda](https://avatars.discourse-cdn.com/v4/letter/r/f07891/32.png) [@recyclepanda](https://community.umbrel.com/u/recyclepanda)\
**Post date:** [August 7, 2021, 6:30pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/10 "2021-08-07T18:30:42Z")

</div>

Okay, I managed to get my node back up and running, and upgraded to the new version 0.4.0. Here’s what I did:

1. First and foremost, I shutdown umbrel and backed up anything that i might need, incase something goes wrong.

> ./umbrel/scripts/stop

- my 24 word seed phrase
- /umbrel/lnd/data/chain/bitcoin/mainnet/channel.backup
- Since i’m using VM’s I took a snapshot of the VM at this moment so i can revert to it if needed.

1. installed Umbrel 0.4.0 in a new directory

> mkdir umbrel2  
> cd umbrel2  
> curl -L [https://github.com/getumbrel/umbrel/archive/v0.4.0.tar.gz](https://github.com/getumbrel/umbrel/archive/v0.4.0.tar.gz) | tar -xz --strip-components=1  
> sudo ./scripts/start

1. I went through the setup process, using my recovery seed, and initialized Umbrel to the point where i could see the dashboard

2. I stopped the new Umbrel install from terminal.

> sudo ./scripts/stop

1. I renamed the bitcoin/electrs/lnd directories & then copied the directories from the old installation to the new installation.

> mv bitcoin bitcoin-backup  
> mv electrs electrs-backup  
> mv lnd lnd-backup  
> mv ~/umbrel/bitcoin ~/umbrel2/bitcoin  
> mv ~/umbrel/electrs ~/umbrel2/electrs  
> mv ~/umbrel/lnd ~/umbrel2/lnd

1. I started umbrel back up and checked that everything looked OK.

> sudo ~/umbrel2/scripts/start

At this point, nearly everything is back to normal. The blockchain did not have to re-sync and all of my lightning channels have been migrated to the new install.

The only remaining problem is that I cannot install apps, apps seem to get stuck on “installing”. I could always just install these apps individually and manually, but I’d like to figure out what is still broken so that I can use Umbrel as intended.

Does anyone have any idea of what might be going on?

> **(Debug Logs)**
>
> # ===================== = Umbrel debug info =
> 
> ## Umbrel version
> 
> 0.4.0
> 
> ## Memory usage
> 
> ```
> total used free shared buff/cache available
> 
> ```
> 
> Mem: 5.8G 1.5G 175M 3.0M 4.2G 4.3G  
> Swap: 975M 77M 898M
> 
> total: 25.4%  
> bitcoin: 9.4%  
> lnd: 7.7%  
> electrs: 4.9%  
> system: 2.6%  
> tor: 0.8%
> 
> ## Memory monitor logs
> 
> Memory monitor is already running  
> 681 ? S 0:00 bash ./scripts/memory-monitor  
> 12398 pts/0 R+ 0:00 bash ./scripts/memory-monitor  
> Memory monitor is already running  
> 2021-08-06 15:24:48 Memory monitor running!  
> 2198 pts/0 S 0:00 bash ./scripts/memory-monitor  
> 2798 pts/0 R+ 0:00 bash ./scripts/memory-monitor  
> Memory monitor is already running  
> 2198 ? S 0:00 bash ./scripts/memory-monitor  
> Memory monitor is already running
> 
> ## Filesystem information
> 
> Filesystem Size Used Avail Use% Mounted on  
> /dev/mapper/Umbrel–vg-root 23G 1.3G 21G 6% /  
> /dev/mapper/Umbrel–vg-home 586G 499G 58G 90% /home
> 
> ## Karen logs
> 
> Creating lnd …  
> Creating nginx …  
> Creating nginx … done  
> Creating bitcoin …  
> Creating lnd … done  
> Creating bitcoin … done  
> Creating middleware …  
> Creating neutrino-switcher …  
> Creating neutrino-switcher … done  
> Creating middleware … done
> 
> Removing status server iptables entry…  
> Exiting iptables setup when not on Umbrel OS
> 
> Starting installed apps…
> 
> Umbrel is now accessible at  
> [http://Umbrel.local](http://Umbrel.local)  
> http://(scrubbed)  
> Skipping status update when not on Umbrel OS  
> == End Update Script 01-run.sh ==
> 
> == Begin Update Script 02-run.sh ==
> 
> # ======================================= =============== UPDATE ================
> 
> # ========= Stage: Post-update ==========
> 
> == End Update Script 02-run.sh ==
> 
> == Begin Update Script 03-run.sh ==
> 
> # ======================================= =============== UPDATE ================
> 
> # =========== Stage: Success ============
> 
> Removing backup  
> Successfully installed Umbrel v0.4.0  
> == End Update Script 03-run.sh ==
> 
> Deleting cloned repository  
> Removing lock
> 
> ## Docker containers
> 
> NAMES STATUS  
> middleware Up 20 hours  
> bitcoin Up 20 hours  
> lnd Up 18 hours  
> nginx Up 20 hours  
> manager Up 20 hours  
> electrs Up 20 hours  
> dashboard Up 20 hours  
> tor Up 20 hours
> 
> ## Bitcoin Core logs
> 
> Attaching to bitcoin  
> bitcoin | 2021-08-07T16:58:36Z Socks5() connect to 239.132.52.41:8333 failed: host unreachable  
> bitcoin | 2021-08-07T17:06:51Z New outbound peer connected: version: 70015, blocks=694663, peer=113 (full-relay)  
> bitcoin | 2021-08-07T17:07:32Z UpdateTip: new best=0000000000000000000e939f2d489d15d79534bbb6b133a8eca72886cc2cfaef height=694664 version=0x20000004 log2\_work=93.009628 tx=661001167 date=‘2021-08-07T17:07:11Z’ progress=1.000000 cache=80.2MiB(588165txo)  
> bitcoin | 2021-08-07T17:14:58Z New outbound peer connected: version: 70015, blocks=694656, peer=115 (full-relay)  
> bitcoin | 2021-08-07T17:16:01Z New outbound peer connected: version: 70015, blocks=694664, peer=116 (full-relay)  
> bitcoin | 2021-08-07T17:16:11Z New outbound peer connected: version: 70015, blocks=694664, peer=117 (full-relay)  
> bitcoin | 2021-08-07T17:18:53Z Socks5() connect to 237.167.100.164:8333 failed: host unreachable  
> bitcoin | 2021-08-07T17:21:24Z Pre-allocating up to position 0x1100000 in rev02679.dat  
> bitcoin | 2021-08-07T17:21:24Z UpdateTip: new best=00000000000000000003bf3334a7ab232fb261f1b1bd50b719a25f6665540dd0 height=694665 version=0x20000004 log2\_work=93.009637 tx=661003923 date=‘2021-08-07T17:21:19Z’ progress=1.000000 cache=80.8MiB(593482txo)  
> bitcoin | 2021-08-07T17:25:30Z Socks5() connect to 231.163.157.221:8333 failed: host unreachable  
> bitcoin | 2021-08-07T17:26:53Z Socks5() connect to 85.154.149.215:8333 failed: general failure  
> bitcoin | 2021-08-07T17:38:19Z Socks5() connect to 209.144.104.194:8333 failed: connection refused  
> bitcoin | 2021-08-07T17:44:26Z UpdateTip: new best=0000000000000000000c9fb19981e8563c5c1b8080ee1aa333467f4c6e8241bf height=694666 version=0x20006004 log2\_work=93.009646 tx=661007196 date=‘2021-08-07T17:44:00Z’ progress=1.000000 cache=82.1MiB(603730txo)  
> bitcoin | 2021-08-07T17:44:48Z Socks5() connect to 239.240.73.83:8333 failed: host unreachable  
> bitcoin | 2021-08-07T17:48:05Z UpdateTip: new best=0000000000000000000190d6dd9cc242052b8725757ee35c5280ecc05a278175 height=694667 version=0x20c00004 log2\_work=93.009655 tx=661008643 date=‘2021-08-07T17:47:58Z’ progress=1.000000 cache=82.3MiB(605817txo)  
> bitcoin | 2021-08-07T17:53:15Z UpdateTip: new best=000000000000000000010b4d21f33d5dfe3eb2c114f888ba57fc7f96d8e45672 height=694668 version=0x20e00004 log2\_work=93.009664 tx=661009665 date=‘2021-08-07T17:53:05Z’ progress=1.000000 cache=82.5MiB(607189txo)  
> bitcoin | 2021-08-07T17:57:04Z Socks5() connect to 61.211.213.92:8333 failed: general failure  
> bitcoin | 2021-08-07T17:58:08Z Socks5() connect to 254.19.235.52:8333 failed: host unreachable  
> bitcoin | 2021-08-07T17:58:34Z Socks5() connect to 200.188.136.72:8333 failed: connection refused  
> bitcoin | 2021-08-07T17:59:11Z Socks5() connect to 64.61.177.43:8333 failed: connection refused  
> bitcoin | 2021-08-07T18:08:25Z UpdateTip: new best=0000000000000000000425dcf19eaacacc28a2d1c3111c07597463dfd773fa35 height=694669 version=0x27ffe004 log2\_work=93.009673 tx=661011731 date=‘2021-08-07T18:08:15Z’ progress=1.000000 cache=83.4MiB(614404txo)  
> bitcoin | 2021-08-07T18:08:25Z Pre-allocating up to position 0x200000 in fltr00415.dat  
> bitcoin | 2021-08-07T18:10:28Z UpdateTip: new best=0000000000000000000ba61d43854a2460b219b5281db2c731ae03a4347eaf43 height=694670 version=0x20c00004 log2\_work=93.009682 tx=661012565 date=‘2021-08-07T18:10:19Z’ progress=1.000000 cache=83.2MiB(612883txo)  
> bitcoin | 2021-08-07T18:23:31Z UpdateTip: new best=00000000000000000004bc4ce151932873b9306355f107b113ce16e243dc8d59 height=694671 version=0x20000004 log2\_work=93.009691 tx=661015010 date=‘2021-08-07T18:23:28Z’ progress=1.000000 cache=83.8MiB(617598txo)  
> bitcoin | 2021-08-07T18:32:07Z Socks5() connect to 84.115.152.72:8333 failed: general failure  
> bitcoin | 2021-08-07T18:32:28Z Socks5() connect to 46.246.122.185:8333 failed: general failure  
> bitcoin | 2021-08-07T18:49:49Z Socks5() connect to 237.117.59.199:8333 failed: host unreachable  
> bitcoin | 2021-08-07T18:50:19Z Pre-allocating up to position 0x1200000 in rev02679.dat  
> bitcoin | 2021-08-07T18:50:19Z UpdateTip: new best=00000000000000000004a7fc08a27909295ab0dac6e9e1d282be82f5818f7880 height=694672 version=0x20800004 log2\_work=93.009700 tx=661017953 date=‘2021-08-07T18:49:47Z’ progress=1.000000 cache=84.9MiB(626764txo)  
> bitcoin | 2021-08-07T18:54:49Z UpdateTip: new best=00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc height=694673 version=0x3fffe004 log2\_work=93.009709 tx=661020243 date=‘2021-08-07T18:54:30Z’ progress=1.000000 cache=85.3MiB(630056txo)
> 
> ## LND logs
> 
> Attaching to lnd  
> lnd | 2021-08-07 18:50:20.131 [INF] UTXN: Attempting to graduate height=694672: num\_kids=0, num\_babies=0  
> lnd | 2021-08-07 18:50:20.132 [INF] NTFN: Block disconnected from main chain: height=694672, sha=00000000000000000004a7fc08a27909295ab0dac6e9e1d282be82f5818f7880  
> lnd | 2021-08-07 18:50:20.214 [INF] CRTR: Pruning channel graph using block 00000000000000000004a7fc08a27909295ab0dac6e9e1d282be82f5818f7880 (height=694672)  
> lnd | 2021-08-07 18:50:20.237 [INF] CRTR: Block 00000000000000000004a7fc08a27909295ab0dac6e9e1d282be82f5818f7880 (height=694672) closed 0 channels  
> lnd | 2021-08-07 18:50:20.418 [INF] NTFN: New block: height=694672, sha=00000000000000000004a7fc08a27909295ab0dac6e9e1d282be82f5818f7880  
> lnd | 2021-08-07 18:50:20.419 [INF] UTXN: Attempting to graduate height=694672: num\_kids=0, num\_babies=0  
> lnd | 2021-08-07 18:50:21.237 [INF] HSWC: ChannelLink(694042:1874:1): updating commit fee to 560 sat/kw sat/kw  
> lnd | 2021-08-07 18:50:34.256 [INF] CRTR: Processed channels=0 updates=118 nodes=4 in last 59.999783703s  
> lnd | 2021-08-07 18:50:56.684 [INF] DISC: Broadcasting 221 new announcements in 17 sub batches  
> lnd | 2021-08-07 18:51:00.382 [INF] DISC: GossipSyncer(03af20bea87280ba29c4a6c1dac20b577a3b2e137bf33235e08ee3c90c3747a997): applying new update horizon: start=2021-08-07 18:51:00 +0000 UTC, end=2157-09-14 01:19:15 +0000 UTC, backlog\_size=4  
> lnd | 2021-08-07 18:51:34.256 [INF] CRTR: Processed channels=3 updates=182 nodes=2 in last 59.999903622s  
> lnd | 2021-08-07 18:52:26.683 [INF] DISC: Broadcasting 264 new announcements in 18 sub batches  
> lnd | 2021-08-07 18:52:33.800 [INF] HSWC: ChannelLink(688456:1557:0): updating commit fee to 560 sat/kw sat/kw  
> lnd | 2021-08-07 18:52:34.256 [INF] CRTR: Processed channels=3 updates=164 nodes=12 in last 59.99993841s  
> lnd | 2021-08-07 18:53:06.891 [INF] HSWC: ChannelLink(687875:1600:0): updating commit fee to 560 sat/kw sat/kw  
> lnd | 2021-08-07 18:53:34.256 [INF] CRTR: Processed channels=0 updates=110 nodes=6 in last 59.999863279s  
> lnd | 2021-08-07 18:53:56.684 [INF] DISC: Broadcasting 196 new announcements in 18 sub batches  
> lnd | 2021-08-07 18:54:34.256 [INF] CRTR: Processed channels=0 updates=142 nodes=3 in last 59.999807138s  
> lnd | 2021-08-07 18:54:40.393 [INF] HSWC: ChannelLink(691064:546:0): updating commit fee to 560 sat/kw sat/kw  
> lnd | 2021-08-07 18:54:50.017 [INF] CRTR: Pruning channel graph using block 00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc (height=694673)  
> lnd | 2021-08-07 18:54:50.056 [INF] CHDB: Pruned unconnected node 020dbd19499b87f2ce722990f23ddd6039477a1bba7841fa41b8406c5dbef64117 from channel graph  
> lnd | 2021-08-07 18:54:50.056 [INF] CHDB: Pruned 1 unconnected nodes from the channel graph  
> lnd | 2021-08-07 18:54:50.065 [INF] CRTR: Block 00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc (height=694673) closed 14 channels  
> lnd | 2021-08-07 18:54:50.200 [INF] NTFN: New block: height=694673, sha=00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc  
> lnd | 2021-08-07 18:54:50.201 [INF] UTXN: Attempting to graduate height=694673: num\_kids=0, num\_babies=0  
> lnd | 2021-08-07 18:54:50.202 [INF] NTFN: Block disconnected from main chain: height=694673, sha=00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc  
> lnd | 2021-08-07 18:54:50.269 [INF] CRTR: Pruning channel graph using block 00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc (height=694673)  
> lnd | 2021-08-07 18:54:50.291 [INF] CRTR: Block 00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc (height=694673) closed 0 channels  
> lnd | 2021-08-07 18:54:50.423 [INF] NTFN: New block: height=694673, sha=00000000000000000008d76994fff7f2382a694859ef5343c64576767cffd4cc  
> lnd | 2021-08-07 18:54:50.423 [INF] UTXN: Attempting to graduate height=694673: num\_kids=0, num\_babies=0
> 
> ## Tor logs
> 
> # Attaching to tor tor | Aug 07 15:44:32.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query. tor | Aug 07 15:47:57.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. tor | Aug 07 15:49:37.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query. tor | Aug 07 15:52:57.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. tor | Aug 07 15:58:11.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:39:49.000 [notice] Heartbeat: Tor’s uptime is 18:00 hours, with 294 circuits open. I’ve sent 446.00 MB and received 605.79 MB. I’ve received 2519 connections on IPv4 and 0 on IPv6. I’ve made 42 connections with IPv4 and 0 with IPv6. tor | Aug 07 16:39:49.000 [notice] While bootstrapping, fetched this many bytes: 642539 (consensus network-status fetch); 13152 (authority cert fetch); 3175414 (microdescriptor fetch) tor | Aug 07 16:39:49.000 [notice] While not bootstrapping, fetched this many bytes: 572745 (consensus network-status fetch); 161952 (microdescriptor fetch) tor | Aug 07 16:39:49.000 [notice] Average packaged cell fullness: 54.919%. TLS write overhead: 2% tor | Aug 07 16:39:49.000 [notice] Our onion services received 0 v2 and 25 v3 INTRODUCE2 cells and attempted to launch 25 rendezvous circuits. tor | Aug 07 16:45:31.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:45:37.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:45:48.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:46:05.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:46:26.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:46:52.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:47:23.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:47:59.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:48:40.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:49:37.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 16:52:33.000 [notice] We tried for 15 seconds to connect to ‘[scrubbed]’ using exit $CB3D1DA3106EDF48558C8FA899870620E7942006~moneroserver [iKjq9R5X/tu3JVLzWeUKAgUvwUqyiyTVhcWxhOrIFdc] at 209.141.34.232. Retrying on a new circuit. tor | Aug 07 16:58:36.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:18:53.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:25:30.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:26:53.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:44:48.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:57:04.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 17:58:08.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 18:32:07.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up. tor | Aug 07 18:49:49.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
> 
> # ==== Result ====

---

<div class="post-metadata">

**Author:** ![zcain79](https://avatars.discourse-cdn.com/v4/letter/z/3bc359/32.png) [@zcain79](https://community.umbrel.com/u/zcain79)\
**Post date:** [August 7, 2021, 6:50pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/11 "2021-08-07T18:50:55Z")

</div>

Good info for anyone running Umbrel the same way. Maybe reach out to @mayankdotch on Twitter. He’s one of the Umbrel devs.

---

<div class="post-metadata">

**Author:** ![0xtr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/0xtr/32/62_2.png) [@0xtr](https://community.umbrel.com/u/0xtr)\
**Post date:** [August 7, 2021, 6:52pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/12 "2021-08-07T18:52:37Z")

</div>

I see that Karen complains about removing a network because it has active endpoints

`Removing network umbrel_main_network error while removing network: network umbrel_main_network id 066676858c36f2c072dd449afb6038f2544774a91271d77e1bab7f6c55699d9e has active endpoints`

---

<div class="post-metadata">

**Author:** ![0xtr](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.umbrel.com/0xtr/32/62_2.png) [@0xtr](https://community.umbrel.com/u/0xtr)\
**Post date:** [August 7, 2021, 7:11pm UTC](https://community.umbrel.com/t/stuck-on-new-update/2354/13 "2021-08-07T19:11:25Z")

</div>

I had to manually shut down Samourai docker containers so that the stop script could successfully shut down all docker containers and networks. When I rebooted the RPI the node was successfully upgraded
