getumbrel / umbrel

A beautiful home server OS for self-hosting with an app store. Buy a pre-built Umbrel Home with umbrelOS, or install on a Raspberry Pi or any x86 system.
https://umbrel.com
Other
7.55k stars 536 forks source link

Dashboard loading stuck on "Loading Bitcoin Core" #331

Closed xFvl closed 1 year ago

xFvl commented 3 years ago

Umbrel was working great for awhile, but now I'm getting:

Screen Shot 2020-12-08 at 14 49 32

Logging in and tailing /var/log/user.log shows:

Dec  8 22:47:02 umbrel manager[696]: ::ffff:10.11.0.2 - - [Tue, 08 Dec 2020 22:47:02 GMT] "GET /v1/system/update-status HTTP/1.0" 304 - "http://192.168.0.107/?redirect=%2Fsettings" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0"
Dec  8 22:47:02 umbrel manager[696]: 
Dec  8 22:47:02 umbrel manager[696]: umbrel-manager
Dec  8 22:47:02 umbrel electrs[696]: WARN - failed to connect daemon at 10.11.1.1:8332: No route to host (os error 113)
Dec  8 22:47:04 umbrel middleware[696]: ::ffff:10.11.0.2 - - [Tue, 08 Dec 2020 22:47:04 GMT] "GET /v1/bitcoind/info/status HTTP/1.0" 304 - "http://192.168.0.107/?redirect=%2Fsettings" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0"
Dec  8 22:47:04 umbrel middleware[696]: 
Dec  8 22:47:04 umbrel middleware[696]: umbrel-middleware
Dec  8 22:47:08 umbrel middleware[696]: ::ffff:10.11.0.2 - - [Tue, 08 Dec 2020 22:47:07 GMT] "GET /v1/bitcoind/info/status HTTP/1.0" 304 - "http://192.168.0.107/?redirect=%2Fsettings" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0"
Dec  8 22:47:08 umbrel middleware[696]: 
Dec  8 22:47:08 umbrel middleware[696]: umbrel-middleware
Dec  8 22:47:08 umbrel electrs[696]: WARN - failed to connect daemon at 10.11.1.1:8332: No route to host (os error 113)
Dec  8 22:47:11 umbrel middleware[696]: ::ffff:10.11.0.2 - - [Tue, 08 Dec 2020 22:47:11 GMT] "GET /v1/bitcoind/info/status HTTP/1.0" 304 - "http://192.168.0.107/?redirect=%2Fsettings" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:83.0) Gecko/20100101 Firefox/83.0"
Dec  8 22:47:11 umbrel middleware[696]: 
Dec  8 22:47:11 umbrel middleware[696]: umbrel-middleware

Also

umbrel@umbrel:~ $ ping 10.11.1.1
PING 10.11.1.1 (10.11.1.1) 56(84) bytes of data.
From 10.11.0.1 icmp_seq=1 Destination Host Unreachable
From 10.11.0.1 icmp_seq=2 Destination Host Unreachable

Also

umbrel@umbrel:~ $ netstat -lnt | grep LISTEN
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:9150          0.0.0.0:*               LISTEN     
tcp6       0      0 :::8080                 :::*                    LISTEN     
tcp6       0      0 :::80                   :::*                    LISTEN     
tcp6       0      0 :::50001                :::*                    LISTEN     
tcp6       0      0 :::22                   :::*                    LISTEN     
tcp6       0      0 :::10009                :::*                    LISTEN     
tcp6       0      0 :::9735                 :::*                    LISTEN

Restarting electrs or the raspi does nothing.

Any ideas?

Thanks!

mayankchhabra commented 3 years ago

@xFvl Could you please SSH in and paste a few logs from Bitcoin Core?

cd ~/umbrel

docker-compose logs --tail=50 bitcoin
xFvl commented 3 years ago

Interesting. Looks like there's disk corruption, or maybe an I/O issue since it's a new hdd (connection?).

Relevant excerpt:

bitcoin              | 2020-12-08T22:42:16Z ERROR: ReadBlockFromDisk: Errors in block header at FlatFilePos(nFile=43, nPos=117281137)
bitcoin              | 2020-12-08T22:42:16Z *** ThreadSync: Failed to read block 00000000000001a9ef984e37e3243b256904fbad1fad7ec47c8ed4e4af22deca from disk
bitcoin              | 2020-12-08T22:42:16Z Error: Error: A fatal internal error occurred, see debug.log for details
bitcoin              | Error: Error: A fatal internal error occurred, see debug.log for details

Full log tail:

$ docker-compose logs --tail=50 bitcoin
Attaching to bitcoin
bitcoin              | 2020-12-08T22:42:15Z Using obfuscation key for /data/.bitcoin/indexes/txindex: 0000000000000000
bitcoin              | 2020-12-08T22:42:15Z txindex thread start
bitcoin              | 2020-12-08T22:42:15Z Syncing txindex with block chain from height 222574
bitcoin              | 2020-12-08T22:42:15Z Opening LevelDB in /data/.bitcoin/indexes/blockfilter/basic/db
bitcoin              | 2020-12-08T22:42:15Z Opened LevelDB successfully
bitcoin              | 2020-12-08T22:42:15Z Using obfuscation key for /data/.bitcoin/indexes/blockfilter/basic/db: 0000000000000000
bitcoin              | 2020-12-08T22:42:15Z basic block filter index thread start
bitcoin              | 2020-12-08T22:42:15Z Syncing basic block filter index with block chain from height 217434
bitcoin              | 2020-12-08T22:42:15Z init message: Loading wallet...
bitcoin              | 2020-12-08T22:42:15Z BerkeleyEnvironment::Open: LogDir=/data/.bitcoin/database ErrorFile=/data/.bitcoin/db.log
bitcoin              | 2020-12-08T22:42:15Z [default wallet] Wallet File Version = 169900
bitcoin              | 2020-12-08T22:42:15Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
bitcoin              | 2020-12-08T22:42:15Z [default wallet] Wallet completed loading in             220ms
bitcoin              | 2020-12-08T22:42:15Z [default wallet] setKeyPool.size() = 2000
bitcoin              | 2020-12-08T22:42:15Z [default wallet] mapWallet.size() = 0
bitcoin              | 2020-12-08T22:42:15Z [default wallet] m_address_book.size() = 0
bitcoin              | 2020-12-08T22:42:15Z block tree size = 659880
bitcoin              | 2020-12-08T22:42:15Z nBestHeight = 659879
bitcoin              | 2020-12-08T22:42:15Z Bound to 10.11.1.1:8333
bitcoin              | 2020-12-08T22:42:15Z init message: Loading P2P addresses...
bitcoin              | 2020-12-08T22:42:15Z torcontrol thread start
bitcoin              | 2020-12-08T22:42:16Z ERROR: ReadBlockFromDisk: Errors in block header at FlatFilePos(nFile=43, nPos=117281137)
bitcoin              | 2020-12-08T22:42:16Z *** ThreadSync: Failed to read block 00000000000001a9ef984e37e3243b256904fbad1fad7ec47c8ed4e4af22deca from disk
bitcoin              | 2020-12-08T22:42:16Z Error: Error: A fatal internal error occurred, see debug.log for details
bitcoin              | Error: Error: A fatal internal error occurred, see debug.log for details
bitcoin              | 2020-12-08T22:42:16Z txindex thread exit
bitcoin              | 2020-12-08T22:42:16Z Loaded 65516 addresses from peers.dat  1436ms
bitcoin              | 2020-12-08T22:42:16Z init message: Starting network threads...
bitcoin              | 2020-12-08T22:42:16Z net thread start
bitcoin              | 2020-12-08T22:42:16Z dnsseed thread start
bitcoin              | 2020-12-08T22:42:16Z init message: Done loading
bitcoin              | 2020-12-08T22:42:16Z opencon thread start
bitcoin              | 2020-12-08T22:42:16Z msghand thread start
bitcoin              | 2020-12-08T22:42:16Z addcon thread start
bitcoin              | 2020-12-08T22:42:16Z tor: Thread interrupt
bitcoin              | 2020-12-08T22:42:16Z Shutdown: In progress...
bitcoin              | 2020-12-08T22:42:16Z dnsseed thread exit
bitcoin              | 2020-12-08T22:42:16Z torcontrol thread exit
bitcoin              | 2020-12-08T22:42:16Z opencon thread exit
bitcoin              | 2020-12-08T22:42:16Z addcon thread exit
bitcoin              | 2020-12-08T22:42:16Z basic block filter index thread exit
bitcoin              | 2020-12-08T22:42:16Z net thread exit
bitcoin              | 2020-12-08T22:42:16Z msghand thread exit
bitcoin              | 2020-12-08T22:42:45Z scheduler thread exit
bitcoin              | 2020-12-08T22:42:45Z FlushStateToDisk: write coins cache to disk (66 coins, 9kB) started
bitcoin              | 2020-12-08T22:42:45Z FlushStateToDisk: write coins cache to disk (66 coins, 9kB) completed (0.01s)
bitcoin              | 2020-12-08T22:42:45Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
bitcoin              | 2020-12-08T22:42:45Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
bitcoin              | 2020-12-08T22:42:45Z [default wallet] Releasing wallet
bitcoin              | 2020-12-08T22:42:45Z Shutdown: done

Assuming I'd have to completely resync the chain if that's the case.

xFvl commented 3 years ago

Looks like I could try running it with the -reindex flag. Can I do that with the docker script?

AaronDewes commented 3 years ago

You can add reindex=1 to bitcoin/bitcoin.conf

Also please run this:

wget https://raw.githubusercontent.com/getumbrel/umbrel/7d76979514d9adefbefb8f6e898453b1f53a58d0/scripts/debug -O ~/umbrel/scripts/debug && chmod +x ~/umbrel/scripts/debug && ~/umbrel/scripts/debug --upload

If it says it can't find a problem automatically, share the link it outputs

xFvl commented 3 years ago

https://hastebin.com/zatufehoge

Added reindex=1 to bitcoin.conf and restarted; it's reindexing now.

AaronDewes commented 3 years ago

Thank you! I just wanted to make sure there's no bigger issue behind your problem, reindexing will probably fix it then

svanstaa commented 3 years ago

Did reindexing fix the issue? Having the same problem here.

aeonBTC commented 3 years ago

Some SSDs do not work properly w/ the Raspberry pi4 USB 3.0 ports. You can use the 2.0 port and it should fix the issue but it will slow down you I/O speeds.

Alternatively there is a work around here https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931

svanstaa commented 3 years ago

reindex=1 fixed the issue for me. Took about 3 days on the Raspi 4.

diemesleno commented 3 years ago

This problem is a constant on Linux (not raspbery pi) installation.

I complete 3 installation and always after complete the blocks sync was not possible to access the dashboard anymore.

There was not shutdown, nothing, just complete the sync and the problem started.

I even can't start to try the node.

louneskmt commented 3 years ago

Hey @diemesleno! Are you using the official power supply?

diemesleno commented 3 years ago

Hey @louneskmt ,

I'm not using Raspbery Pi as as said on my message.

I did the installation over Linux (Ubuntu 20.04) 3 times from scratch and all the time when the sync from blocks finish I cannot access the dashboard anymore.

louneskmt commented 3 years ago

Sorry I missed that part 😁

Have you ever tried to run the debug script? It may provide us more details on the issue.

To execute it from your Umbrel dir:

./scripts/debug --upload

You can send the resulting links here.

diemesleno commented 3 years ago

Yes, I tried 4 times and even shared with you guys on telegram group.

Here's the debug log again:

https://hastebin.com/funayiragu https://hastebin.com/xodinohohe

Looks that the problem is on LND because it's trying to connect with some IPs with no success.

diemesleno commented 3 years ago

The problem looks like: 2021/01/06 08:42:33 http: TLS handshake error from 117.212.110.28:57085: EOF lnd | 2021/01/06 08:52:09 http: TLS handshake error from 67.43.225.160:54462: EOF lnd | 2021/01/06 09:16:42 http: TLS handshake error from 222.186.136.150:57220: tls: first record does not look like a TLS handshake lnd | 2021/01/06 10:19:20 http: TLS handshake error from 89.248.165.52:58018: tls: first record does not look like a TLS handshake lnd | 2021/01/06 13:10:13 http: TLS handshake error from 141.98.10.149:64235: tls: first record does not look like a TLS handshake lnd | 2021/01/06 13:27:31 http: TLS handshake error from 192.241.217.91:46182: EOF lnd | 2021/01/06 14:20:23 http: TLS handshake error from 172.105.89.161:38029: tls: first record does not look like a TLS handshake

diemesleno commented 3 years ago

Looks that have problem with TOR too:

tor | Jan 06 18:42:49.000 [notice] Average packaged cell fullness: 34.526%. TLS write overhead: 3% tor | Jan 06 18:42:49.000 [notice] Our onion services received 0 v2 and 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits. tor | Jan 06 19:59:12.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 20:05:45.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 20:37:00.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:04:53.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:09:09.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:13:48.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:19:36.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:50:54.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:51:04.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. tor | Jan 06 21:53:27.000 [notice] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up.

misterdna commented 3 years ago

I complete 3 installation and always after complete the blocks sync was not possible to access the dashboard anymore.

Wow, I just had this happen today. Been keeping an eye on the initial sync progress, and it really seems like right after it reached 100%, attempts to login stall at "Loading Bitcoin Core... This can take a while, please don't turn off your Umbrel!"

Rebooted, same thing. I was so excited how well everything seemed to work while syncing, so this was an unexpected buzzkill. Maybe if I just leave it alone long enough?

FINAL EDIT: I was just impatient, it's up and running smoothly!

Tibobfd commented 3 years ago

Same issue, it crashed around 80% sync, I tried everything but I cant access the dashboard anymore.

My log are quite similar to yours : https://hastebin.com/aqozebaxax

osilloh commented 3 years ago

I was at 99.x % when I went to sleep 2 days later I have the. "Loading bitcoin core...please do not turn off Umbrel". It took 11 days to get to 99%, I should have rebooted, the first days it was about 30% done. My Raspiblitz's full sync'd in 3 days.

Here is my output:

umbrel@umbrel:~/umbrel $ cd ~/umbrel umbrel@umbrel:~/umbrel $ docker-compose logs --tail=50 bitcoin Attaching to bitcoin bitcoin | 2021-03-12T06:56:55Z Rolling forward 00000000000000000008c7f4607ae9865237545defbb665021ac5ee435768312 (672592) bitcoin | 2021-03-12T06:57:35Z Rolling forward 0000000000000000000abeaafc15ade63c24b76a80aac8fb92e61b32181edc5b (672593) bitcoin | 2021-03-12T06:58:09Z Rolling forward 000000000000000000011fe4a7d96da5f05046c599eb7ec94aa754ca5ef17602 (672594) bitcoin | 2021-03-12T06:58:45Z Rolling forward 00000000000000000004b599969f9f25e393520d41afeab2ca97c5509c1e8a81 (672595) bitcoin | 2021-03-12T06:59:18Z Rolling forward 0000000000000000000c3d174a57d8020c6cac2973ec643b59a225597a03b6e4 (672596) bitcoin | 2021-03-12T06:59:36Z Rolling forward 00000000000000000005419b8d637ce906c2575220528a2c9bd33db047b317e4 (672597) bitcoin | 2021-03-12T07:00:03Z Rolling forward 0000000000000000000acd35409e51432d49020441ce98805f71c864dea3a64f (672598) bitcoin | 2021-03-12T07:00:42Z Rolling forward 00000000000000000001675e5a932064c24c3f89684fc12942011652ca3c3cb2 (672599) bitcoin | 2021-03-12T07:01:13Z Rolling forward 0000000000000000000c0f7aa9b5b424a703420c6fef12cc4066b78a59fdcc41 (672600) bitcoin | 2021-03-12T07:01:50Z Rolling forward 000000000000000000066b82d69714ed696d5c8b7b981f6bf211c0e93e8db74f (672601) bitcoin | 2021-03-12T07:02:22Z Rolling forward 0000000000000000000bc25af7f2ae80a11b1da0e160cbb1618a826e6617837b (672602) bitcoin | 2021-03-12T07:02:56Z Rolling forward 0000000000000000000510bf460a2d08fc74168d21e543c77bf16d2a8d3f3a5f (672603) bitcoin | 2021-03-12T07:03:27Z Rolling forward 00000000000000000009fc6fc05568fd26dff654a5187f378e91cf3c00d450c4 (672604) bitcoin | 2021-03-12T07:03:58Z Rolling forward 000000000000000000041d07b340e0f5c87ad9668d342ed28cddd1d26f53fba3 (672605) bitcoin | 2021-03-12T07:04:24Z Rolling forward 000000000000000000093de7dea2f70e92c3c2c33d87c433b8a0c9c6f0e05f03 (672606) bitcoin | 2021-03-12T07:04:57Z Rolling forward 000000000000000000036dc59ab17d265a1f63858f054fc73a636f687aa05024 (672607) bitcoin | 2021-03-12T07:05:31Z Rolling forward 0000000000000000000b6152c18d9aba0096055e73545cfd9f79297f0cbba2a3 (672608) bitcoin | 2021-03-12T07:06:05Z Rolling forward 00000000000000000001894da84fd07be42d500b5d436ca9aad1ceb0ae3d556a (672609) bitcoin | 2021-03-12T07:06:15Z Rolling forward 0000000000000000000b73dd790b8738cb855ae26f10f31ff326013e6fd97fcf (672610) bitcoin | 2021-03-12T07:06:22Z Rolling forward 00000000000000000001a4a6d0aaac7c98c3354b22a1aacf838de2a770c603e9 (672611) bitcoin | 2021-03-12T07:06:50Z Rolling forward 00000000000000000002d9265ddd74ee403d0b1bb99a3eebf71542a30b0c6975 (672612) bitcoin | 2021-03-12T07:07:35Z Rolling forward 00000000000000000001109f21068a7cbfa81929df0a2e3b20135aea38acabe4 (672613) bitcoin | 2021-03-12T07:08:03Z Rolling forward 00000000000000000003cadb5c49ef2e9725958e969e763ca5d71b4fed57c74c (672614) bitcoin | 2021-03-12T07:08:27Z Rolling forward 00000000000000000003b857a639ed2186f4869cb119e6647cd89bc13f644877 (672615) bitcoin | 2021-03-12T07:09:00Z Rolling forward 000000000000000000020e10ae41be2c48f8f4b7261c3a2eb94c638131b4628d (672616) bitcoin | 2021-03-12T07:09:42Z Rolling forward 0000000000000000000caec38ccf27b3509011b242d097c6f89795b8a3279b10 (672617) bitcoin | 2021-03-12T07:09:57Z Rolling forward 0000000000000000000cd85170f8b4fd8c76abe3bc7c6833a019359e381c3331 (672618) bitcoin | 2021-03-12T07:10:23Z Rolling forward 000000000000000000085fbda53cc799771bba0eb51b368dbfd8852cc7823deb (672619) bitcoin | 2021-03-12T07:10:58Z Rolling forward 0000000000000000000875c17a7c2b0c3d847b594a6a69c62b4c657fbe1fa9a0 (672620) bitcoin | 2021-03-12T07:11:31Z Rolling forward 0000000000000000000313415e1795f2c0d556f51c99833cbb2ad77a15cf6f22 (672621) bitcoin | 2021-03-12T07:12:01Z Rolling forward 00000000000000000006e520328e400922c592eecb6d8a5b694ae48343f374c9 (672622) bitcoin | 2021-03-12T07:12:36Z Rolling forward 000000000000000000061ea3743780830006473371e92bc155d4ad13cc313f1c (672623) bitcoin | 2021-03-12T07:13:01Z Rolling forward 000000000000000000001cb38be788bd188b64b798e0e6f64e1633d13f4e36af (672624) bitcoin | 2021-03-12T07:13:28Z Rolling forward 000000000000000000074c17a1a9489be1da847843c7d33ab068058196c76cf9 (672625) bitcoin | 2021-03-12T07:13:56Z Rolling forward 0000000000000000000686ddc536f20cdb22970db1c078dd96c18009c8fb2195 (672626) bitcoin | 2021-03-12T07:14:21Z Rolling forward 000000000000000000019b02bf5e3d908678fa5c277e43bf5f73a0dd7cf7be4d (672627) bitcoin | 2021-03-12T07:14:53Z Rolling forward 000000000000000000019bf8daa12b7a632268a6e4c6d6789b6df40963b36ba2 (672628) bitcoin | 2021-03-12T07:15:16Z Rolling forward 00000000000000000009b4ded48228dfea62cad10e451e8b81bc7e61c1f0e86b (672629) bitcoin | 2021-03-12T07:15:35Z Rolling forward 00000000000000000007f8368ce6bc076ff80f79890af6d409fe94a1194726fe (672630) bitcoin | 2021-03-12T07:15:57Z Rolling forward 00000000000000000008471fc8fc18fe7775ee8de1806a6eff0ac9dc4e320625 (672631) bitcoin | 2021-03-12T07:16:36Z Rolling forward 0000000000000000000ae3e233762d7f665e39b7848111d33d5d1d671052262c (672632) bitcoin | 2021-03-12T07:17:02Z Rolling forward 00000000000000000003c427a2ee893d82218cb771cdb911ccf92747f26fe6e4 (672633) bitcoin | 2021-03-12T07:17:34Z Rolling forward 000000000000000000025c2e95ca558ba3e8413b1964f3919b8f7a876f562d90 (672634) bitcoin | 2021-03-12T07:17:59Z Rolling forward 00000000000000000005c2067563a2e610840d989b3eb4032ceb1e3a6b394143 (672635) bitcoin | 2021-03-12T07:18:28Z Rolling forward 0000000000000000000b3c9374188bd4727d110cd0979f79eeed9917b58b70a3 (672636) bitcoin | 2021-03-12T07:18:58Z Rolling forward 0000000000000000000a36ec461de39c3d0f85fee9095da9577dcce51fa5c880 (672637) bitcoin | 2021-03-12T07:19:31Z Rolling forward 000000000000000000053048d81ae9a89af66624907f838e23a05812ae694ea5 (672638) bitcoin | 2021-03-12T07:19:55Z Rolling forward 0000000000000000000b7e1b1f8e106ebcf05ece82ee76cc03e0c4b6300aece2 (672639) bitcoin | 2021-03-12T07:20:22Z Rolling forward 000000000000000000010e4714ae58d3582739e98d8f9b0bb7db5621d52884bf (672640) bitcoin | 2021-03-12T07:20:43Z Rolling forward 00000000000000000005827a6e427d0eecb000d85c727fbd84d2034b28bcefb3 (672641) umbrel@umbrel:~/umbrel $

AaronDewes commented 3 years ago

I was at 99.x % when I went to sleep 2 days later I have the. "Loading bitcoin core...please do not turn off Umbrel". It took 11 days to get to 99%, I should have rebooted, the first days it was about 30% done. My Raspiblitz's full sync'd in 3 days.

Here is my output:

umbrel@umbrel:~/umbrel $ cd ~/umbrel umbrel@umbrel:~/umbrel $ docker-compose logs --tail=50 bitcoin Attaching to bitcoin bitcoin | 2021-03-12T06:56:55Z Rolling forward 00000000000000000008c7f4607ae9865237545defbb665021ac5ee435768312 (672592) bitcoin | 2021-03-12T06:57:35Z Rolling forward 0000000000000000000abeaafc15ade63c24b76a80aac8fb92e61b32181edc5b (672593) bitcoin | 2021-03-12T06:58:09Z Rolling forward 000000000000000000011fe4a7d96da5f05046c599eb7ec94aa754ca5ef17602 (672594) bitcoin | 2021-03-12T06:58:45Z Rolling forward 00000000000000000004b599969f9f25e393520d41afeab2ca97c5509c1e8a81 (672595) bitcoin | 2021-03-12T06:59:18Z Rolling forward 0000000000000000000c3d174a57d8020c6cac2973ec643b59a225597a03b6e4 (672596) bitcoin | 2021-03-12T06:59:36Z Rolling forward 00000000000000000005419b8d637ce906c2575220528a2c9bd33db047b317e4 (672597) bitcoin | 2021-03-12T07:00:03Z Rolling forward 0000000000000000000acd35409e51432d49020441ce98805f71c864dea3a64f (672598) bitcoin | 2021-03-12T07:00:42Z Rolling forward 00000000000000000001675e5a932064c24c3f89684fc12942011652ca3c3cb2 (672599) bitcoin | 2021-03-12T07:01:13Z Rolling forward 0000000000000000000c0f7aa9b5b424a703420c6fef12cc4066b78a59fdcc41 (672600) bitcoin | 2021-03-12T07:01:50Z Rolling forward 000000000000000000066b82d69714ed696d5c8b7b981f6bf211c0e93e8db74f (672601) bitcoin | 2021-03-12T07:02:22Z Rolling forward 0000000000000000000bc25af7f2ae80a11b1da0e160cbb1618a826e6617837b (672602) bitcoin | 2021-03-12T07:02:56Z Rolling forward 0000000000000000000510bf460a2d08fc74168d21e543c77bf16d2a8d3f3a5f (672603) bitcoin | 2021-03-12T07:03:27Z Rolling forward 00000000000000000009fc6fc05568fd26dff654a5187f378e91cf3c00d450c4 (672604) bitcoin | 2021-03-12T07:03:58Z Rolling forward 000000000000000000041d07b340e0f5c87ad9668d342ed28cddd1d26f53fba3 (672605) bitcoin | 2021-03-12T07:04:24Z Rolling forward 000000000000000000093de7dea2f70e92c3c2c33d87c433b8a0c9c6f0e05f03 (672606) bitcoin | 2021-03-12T07:04:57Z Rolling forward 000000000000000000036dc59ab17d265a1f63858f054fc73a636f687aa05024 (672607) bitcoin | 2021-03-12T07:05:31Z Rolling forward 0000000000000000000b6152c18d9aba0096055e73545cfd9f79297f0cbba2a3 (672608) bitcoin | 2021-03-12T07:06:05Z Rolling forward 00000000000000000001894da84fd07be42d500b5d436ca9aad1ceb0ae3d556a (672609) bitcoin | 2021-03-12T07:06:15Z Rolling forward 0000000000000000000b73dd790b8738cb855ae26f10f31ff326013e6fd97fcf (672610) bitcoin | 2021-03-12T07:06:22Z Rolling forward 00000000000000000001a4a6d0aaac7c98c3354b22a1aacf838de2a770c603e9 (672611) bitcoin | 2021-03-12T07:06:50Z Rolling forward 00000000000000000002d9265ddd74ee403d0b1bb99a3eebf71542a30b0c6975 (672612) bitcoin | 2021-03-12T07:07:35Z Rolling forward 00000000000000000001109f21068a7cbfa81929df0a2e3b20135aea38acabe4 (672613) bitcoin | 2021-03-12T07:08:03Z Rolling forward 00000000000000000003cadb5c49ef2e9725958e969e763ca5d71b4fed57c74c (672614) bitcoin | 2021-03-12T07:08:27Z Rolling forward 00000000000000000003b857a639ed2186f4869cb119e6647cd89bc13f644877 (672615) bitcoin | 2021-03-12T07:09:00Z Rolling forward 000000000000000000020e10ae41be2c48f8f4b7261c3a2eb94c638131b4628d (672616) bitcoin | 2021-03-12T07:09:42Z Rolling forward 0000000000000000000caec38ccf27b3509011b242d097c6f89795b8a3279b10 (672617) bitcoin | 2021-03-12T07:09:57Z Rolling forward 0000000000000000000cd85170f8b4fd8c76abe3bc7c6833a019359e381c3331 (672618) bitcoin | 2021-03-12T07:10:23Z Rolling forward 000000000000000000085fbda53cc799771bba0eb51b368dbfd8852cc7823deb (672619) bitcoin | 2021-03-12T07:10:58Z Rolling forward 0000000000000000000875c17a7c2b0c3d847b594a6a69c62b4c657fbe1fa9a0 (672620) bitcoin | 2021-03-12T07:11:31Z Rolling forward 0000000000000000000313415e1795f2c0d556f51c99833cbb2ad77a15cf6f22 (672621) bitcoin | 2021-03-12T07:12:01Z Rolling forward 00000000000000000006e520328e400922c592eecb6d8a5b694ae48343f374c9 (672622) bitcoin | 2021-03-12T07:12:36Z Rolling forward 000000000000000000061ea3743780830006473371e92bc155d4ad13cc313f1c (672623) bitcoin | 2021-03-12T07:13:01Z Rolling forward 000000000000000000001cb38be788bd188b64b798e0e6f64e1633d13f4e36af (672624) bitcoin | 2021-03-12T07:13:28Z Rolling forward 000000000000000000074c17a1a9489be1da847843c7d33ab068058196c76cf9 (672625) bitcoin | 2021-03-12T07:13:56Z Rolling forward 0000000000000000000686ddc536f20cdb22970db1c078dd96c18009c8fb2195 (672626) bitcoin | 2021-03-12T07:14:21Z Rolling forward 000000000000000000019b02bf5e3d908678fa5c277e43bf5f73a0dd7cf7be4d (672627) bitcoin | 2021-03-12T07:14:53Z Rolling forward 000000000000000000019bf8daa12b7a632268a6e4c6d6789b6df40963b36ba2 (672628) bitcoin | 2021-03-12T07:15:16Z Rolling forward 00000000000000000009b4ded48228dfea62cad10e451e8b81bc7e61c1f0e86b (672629) bitcoin | 2021-03-12T07:15:35Z Rolling forward 00000000000000000007f8368ce6bc076ff80f79890af6d409fe94a1194726fe (672630) bitcoin | 2021-03-12T07:15:57Z Rolling forward 00000000000000000008471fc8fc18fe7775ee8de1806a6eff0ac9dc4e320625 (672631) bitcoin | 2021-03-12T07:16:36Z Rolling forward 0000000000000000000ae3e233762d7f665e39b7848111d33d5d1d671052262c (672632) bitcoin | 2021-03-12T07:17:02Z Rolling forward 00000000000000000003c427a2ee893d82218cb771cdb911ccf92747f26fe6e4 (672633) bitcoin | 2021-03-12T07:17:34Z Rolling forward 000000000000000000025c2e95ca558ba3e8413b1964f3919b8f7a876f562d90 (672634) bitcoin | 2021-03-12T07:17:59Z Rolling forward 00000000000000000005c2067563a2e610840d989b3eb4032ceb1e3a6b394143 (672635) bitcoin | 2021-03-12T07:18:28Z Rolling forward 0000000000000000000b3c9374188bd4727d110cd0979f79eeed9917b58b70a3 (672636) bitcoin | 2021-03-12T07:18:58Z Rolling forward 0000000000000000000a36ec461de39c3d0f85fee9095da9577dcce51fa5c880 (672637) bitcoin | 2021-03-12T07:19:31Z Rolling forward 000000000000000000053048d81ae9a89af66624907f838e23a05812ae694ea5 (672638) bitcoin | 2021-03-12T07:19:55Z Rolling forward 0000000000000000000b7e1b1f8e106ebcf05ece82ee76cc03e0c4b6300aece2 (672639) bitcoin | 2021-03-12T07:20:22Z Rolling forward 000000000000000000010e4714ae58d3582739e98d8f9b0bb7db5621d52884bf (672640) bitcoin | 2021-03-12T07:20:43Z Rolling forward 00000000000000000005827a6e427d0eecb000d85c727fbd84d2034b28bcefb3 (672641) umbrel@umbrel:~/umbrel $

That's normal then, just wait

osilloh commented 3 years ago

I was at 99.x % when I went to sleep 2 days later I have the. "Loading bitcoin core...please do not turn off Umbrel". It took 11 days to get to 99%, I should have rebooted, the first days it was about 30% done. My Raspiblitz's full sync'd in 3 days. Here is my output: umbrel@umbrel:~/umbrel $ cd ~/umbrel umbrel@umbrel:~/umbrel $ docker-compose logs --tail=50 bitcoin Attaching to bitcoin bitcoin | 2021-03-12T06:56:55Z Rolling forward 00000000000000000008c7f4607ae9865237545defbb665021ac5ee435768312 (672592) bitcoin | 2021-03-12T06:57:35Z Rolling forward 0000000000000000000abeaafc15ade63c24b76a80aac8fb92e61b32181edc5b (672593) bitcoin | 2021-03-12T06:58:09Z Rolling forward 000000000000000000011fe4a7d96da5f05046c599eb7ec94aa754ca5ef17602 (672594) bitcoin | 2021-03-12T06:58:45Z Rolling forward 00000000000000000004b599969f9f25e393520d41afeab2ca97c5509c1e8a81 (672595) bitcoin | 2021-03-12T06:59:18Z Rolling forward 0000000000000000000c3d174a57d8020c6cac2973ec643b59a225597a03b6e4 (672596) bitcoin | 2021-03-12T06:59:36Z Rolling forward 00000000000000000005419b8d637ce906c2575220528a2c9bd33db047b317e4 (672597) bitcoin | 2021-03-12T07:00:03Z Rolling forward 0000000000000000000acd35409e51432d49020441ce98805f71c864dea3a64f (672598) bitcoin | 2021-03-12T07:00:42Z Rolling forward 00000000000000000001675e5a932064c24c3f89684fc12942011652ca3c3cb2 (672599) bitcoin | 2021-03-12T07:01:13Z Rolling forward 0000000000000000000c0f7aa9b5b424a703420c6fef12cc4066b78a59fdcc41 (672600) bitcoin | 2021-03-12T07:01:50Z Rolling forward 000000000000000000066b82d69714ed696d5c8b7b981f6bf211c0e93e8db74f (672601) bitcoin | 2021-03-12T07:02:22Z Rolling forward 0000000000000000000bc25af7f2ae80a11b1da0e160cbb1618a826e6617837b (672602) bitcoin | 2021-03-12T07:02:56Z Rolling forward 0000000000000000000510bf460a2d08fc74168d21e543c77bf16d2a8d3f3a5f (672603) bitcoin | 2021-03-12T07:03:27Z Rolling forward 00000000000000000009fc6fc05568fd26dff654a5187f378e91cf3c00d450c4 (672604) bitcoin | 2021-03-12T07:03:58Z Rolling forward 000000000000000000041d07b340e0f5c87ad9668d342ed28cddd1d26f53fba3 (672605) bitcoin | 2021-03-12T07:04:24Z Rolling forward 000000000000000000093de7dea2f70e92c3c2c33d87c433b8a0c9c6f0e05f03 (672606) bitcoin | 2021-03-12T07:04:57Z Rolling forward 000000000000000000036dc59ab17d265a1f63858f054fc73a636f687aa05024 (672607) bitcoin | 2021-03-12T07:05:31Z Rolling forward 0000000000000000000b6152c18d9aba0096055e73545cfd9f79297f0cbba2a3 (672608) bitcoin | 2021-03-12T07:06:05Z Rolling forward 00000000000000000001894da84fd07be42d500b5d436ca9aad1ceb0ae3d556a (672609) bitcoin | 2021-03-12T07:06:15Z Rolling forward 0000000000000000000b73dd790b8738cb855ae26f10f31ff326013e6fd97fcf (672610) bitcoin | 2021-03-12T07:06:22Z Rolling forward 00000000000000000001a4a6d0aaac7c98c3354b22a1aacf838de2a770c603e9 (672611) bitcoin | 2021-03-12T07:06:50Z Rolling forward 00000000000000000002d9265ddd74ee403d0b1bb99a3eebf71542a30b0c6975 (672612) bitcoin | 2021-03-12T07:07:35Z Rolling forward 00000000000000000001109f21068a7cbfa81929df0a2e3b20135aea38acabe4 (672613) bitcoin | 2021-03-12T07:08:03Z Rolling forward 00000000000000000003cadb5c49ef2e9725958e969e763ca5d71b4fed57c74c (672614) bitcoin | 2021-03-12T07:08:27Z Rolling forward 00000000000000000003b857a639ed2186f4869cb119e6647cd89bc13f644877 (672615) bitcoin | 2021-03-12T07:09:00Z Rolling forward 000000000000000000020e10ae41be2c48f8f4b7261c3a2eb94c638131b4628d (672616) bitcoin | 2021-03-12T07:09:42Z Rolling forward 0000000000000000000caec38ccf27b3509011b242d097c6f89795b8a3279b10 (672617) bitcoin | 2021-03-12T07:09:57Z Rolling forward 0000000000000000000cd85170f8b4fd8c76abe3bc7c6833a019359e381c3331 (672618) bitcoin | 2021-03-12T07:10:23Z Rolling forward 000000000000000000085fbda53cc799771bba0eb51b368dbfd8852cc7823deb (672619) bitcoin | 2021-03-12T07:10:58Z Rolling forward 0000000000000000000875c17a7c2b0c3d847b594a6a69c62b4c657fbe1fa9a0 (672620) bitcoin | 2021-03-12T07:11:31Z Rolling forward 0000000000000000000313415e1795f2c0d556f51c99833cbb2ad77a15cf6f22 (672621) bitcoin | 2021-03-12T07:12:01Z Rolling forward 00000000000000000006e520328e400922c592eecb6d8a5b694ae48343f374c9 (672622) bitcoin | 2021-03-12T07:12:36Z Rolling forward 000000000000000000061ea3743780830006473371e92bc155d4ad13cc313f1c (672623) bitcoin | 2021-03-12T07:13:01Z Rolling forward 000000000000000000001cb38be788bd188b64b798e0e6f64e1633d13f4e36af (672624) bitcoin | 2021-03-12T07:13:28Z Rolling forward 000000000000000000074c17a1a9489be1da847843c7d33ab068058196c76cf9 (672625) bitcoin | 2021-03-12T07:13:56Z Rolling forward 0000000000000000000686ddc536f20cdb22970db1c078dd96c18009c8fb2195 (672626) bitcoin | 2021-03-12T07:14:21Z Rolling forward 000000000000000000019b02bf5e3d908678fa5c277e43bf5f73a0dd7cf7be4d (672627) bitcoin | 2021-03-12T07:14:53Z Rolling forward 000000000000000000019bf8daa12b7a632268a6e4c6d6789b6df40963b36ba2 (672628) bitcoin | 2021-03-12T07:15:16Z Rolling forward 00000000000000000009b4ded48228dfea62cad10e451e8b81bc7e61c1f0e86b (672629) bitcoin | 2021-03-12T07:15:35Z Rolling forward 00000000000000000007f8368ce6bc076ff80f79890af6d409fe94a1194726fe (672630) bitcoin | 2021-03-12T07:15:57Z Rolling forward 00000000000000000008471fc8fc18fe7775ee8de1806a6eff0ac9dc4e320625 (672631) bitcoin | 2021-03-12T07:16:36Z Rolling forward 0000000000000000000ae3e233762d7f665e39b7848111d33d5d1d671052262c (672632) bitcoin | 2021-03-12T07:17:02Z Rolling forward 00000000000000000003c427a2ee893d82218cb771cdb911ccf92747f26fe6e4 (672633) bitcoin | 2021-03-12T07:17:34Z Rolling forward 000000000000000000025c2e95ca558ba3e8413b1964f3919b8f7a876f562d90 (672634) bitcoin | 2021-03-12T07:17:59Z Rolling forward 00000000000000000005c2067563a2e610840d989b3eb4032ceb1e3a6b394143 (672635) bitcoin | 2021-03-12T07:18:28Z Rolling forward 0000000000000000000b3c9374188bd4727d110cd0979f79eeed9917b58b70a3 (672636) bitcoin | 2021-03-12T07:18:58Z Rolling forward 0000000000000000000a36ec461de39c3d0f85fee9095da9577dcce51fa5c880 (672637) bitcoin | 2021-03-12T07:19:31Z Rolling forward 000000000000000000053048d81ae9a89af66624907f838e23a05812ae694ea5 (672638) bitcoin | 2021-03-12T07:19:55Z Rolling forward 0000000000000000000b7e1b1f8e106ebcf05ece82ee76cc03e0c4b6300aece2 (672639) bitcoin | 2021-03-12T07:20:22Z Rolling forward 000000000000000000010e4714ae58d3582739e98d8f9b0bb7db5621d52884bf (672640) bitcoin | 2021-03-12T07:20:43Z Rolling forward 00000000000000000005827a6e427d0eecb000d85c727fbd84d2034b28bcefb3 (672641) umbrel@umbrel:~/umbrel $

That's normal then, just wait

ok, thank you! If the purple progress bar moved, it would be easier to tell if it wasn't hung. Ran the above commands again, I can see the blocks are incrementing. It is almost caught up to the current block!

bitcoin | 2021-03-12T17:58:01Z Rolling forward 00000000000000000008ea90611d21b8751659fc25c68dcf1f13f13ce193468b (674117) bitcoin | 2021-03-12T17:58:33Z Rolling forward 00000000000000000004c2af247b0fafaa0c7c0edcbf309d061335d90baee946 (674118) bitcoin | 2021-03-12T17:58:54Z Rolling forward 00000000000000000002a7fcbc875e2bbec71fa6d47e140c0bab92061b9e24f1 (674119) bitcoin | 2021-03-12T17:59:18Z Rolling forward 00000000000000000004bd32911e11d9774d53b79cfa3ac26944254c9798c70a (674120)

ch1ru commented 3 years ago

I am getting the same problem. Can I ask what the username and password format is for ssh and I'll send the log? I'm trying to login with username: umbrel and my umbrel password but incorrect login. Thanks

ch1ru commented 3 years ago

Ok I logged into my umbrel and checked the log file. I added the reindex option and the Bitcoin daemon is syncing fine with no error messages. However it still displays the loading bitcoin core page. Did the problem seem to resolve after the fully synced?

zohlandt commented 3 years ago

I have noticed this also could be a problem with how the Ubuntu disk sizing is implemented.

Just to try, (maybe this is not the way, but it worked for me) to install Umbrel on Centos 7. During the installation i gave full space to /root and installed umbrel on /umbrel.

Here is how to install Umbrel in Centos (bear in mind I am not a linux engineer, so if things could have bene done otherwise, then you know, this worked for me)

Umbrel | bitcoin & Lightning Node | VM CentOS 7 Install | #1 Umbrel beta 0.3.5

!!!!When installing CentOS make sure you have allocated all space to /root!!! (minimum ~1 TB) or install umbrel to /home

SSH mkdir umbrel cd umbrel $ yum update -y $ yum install -y wget

$ yum install -y yum-utils

INSTALL DOCKER

$ yum check-update

$ yum-config-manager \ --add-repo \ https://download.docker.com/linux/centos/docker-ce.repo

$ yum install -y docker-ce docker-ce-cli containerd.io

$ systemctl start docker $ systemctl enable /usr/lib/systemd/system/docker.service $ docker run hello-world

INSTALL PYTHON 3

$ yum update -y $ yum install -y python3

INSTALL DOCKER COMPOSE

$ curl -L "https://github.com/docker/compose/releases/download/1.28.5/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose $ chmod +x /usr/local/bin/docker-compose

INSTALL FSWATCH

$ yum groupinstall "Development Tools" -y $ wget https://github.com/emcrisostomo/fswatch/releases/download/1.9.3/fswatch-1.9.3.tar.gz $ tar xzf fswatch-1.9.3.tar.gz $ cd fswatch-1.9.3/ $ ./configure $ make $ make install $ ldconfig $ fswatch --version cd ..

INSALL RSYNC & CURL yum install -y rsync curl

INSTALL JQ yum install epel-release -y yum update -y yum install jq -y jq -Version

DOWNLOAD UMBREL

curl -L https://github.com/getumbrel/umbrel/archive/v0.3.7.tar.gz | tar -xz --strip-components=1

reboot now

START UMBREL

./scripts/start

ADD TO CRON TO AUTOSTART

crontab -e add "@reboot /root/umbrel/scripts/start"

DOCKER INSTALL

$ yum install \ apt-transport-https \ ca-certificates \ curl \ gnupg-agent \ software-properties-common

$ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add #-

$ sudo apt-key fingerprint 0EBFCD88

$ sudo add-apt-repository \ "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable"

$ sudo apt-get update

$ sudo apt-get install docker-ce docker-ce-cli containerd.io

$ sudo -s

OLD $ sudo curl -L https://github.com/docker/compose/releases/download/1.21.2/docker-compose-`uname -s-uname -m` > /usr/local/bin/docker-compose

$ sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose $ exit $ sudo chmod +x /usr/local/bin/docker-compose

Umbrel 0.2.11

$ sudo apt-get install fswatch jq rsync curl

$ mkdir umbrel

$ cd umbrel

OLD $ curl -L https://github.com/getumbrel/umbrel/archive/v0.2.3.tar.gz | tar -xz --strip-components=1

$ curl -L https://github.com/getumbrel/umbrel/archive/v0.3.7.tar.gz | tar -xz --strip-components=1

RUNNING UMBREL: Make sure to be in the umbrel folder (cd umbrel)

To use Umbrel on mainnet, run:

$ sudo ./scripts/start

For testnet, run:

$ sudo NETWORK=testnet ./scripts/start

For regtest, run:

$ sudo NETWORK=regtest ./scripts/start

To Stop umbrel

$ sudo ./scripts/stop

efecini commented 3 years ago

I complete 3 installation and always after complete the blocks sync was not possible to access the dashboard anymore.

Wow, I just had this happen today. Been keeping an eye on the initial sync progress, and it really seems like right after it reached 100%, attempts to login stall at "Loading Bitcoin Core... This can take a while, please don't turn off your Umbrel!"

Rebooted, same thing. I was so excited how well everything seemed to work while syncing, so this was an unexpected buzzkill. Maybe if I just leave it alone long enough?

FINAL EDIT: I was just impatient, it's up and running smoothly!

Hey, So this screen goes eventually right? Should I wait for it to sync then is it gonna work? Thanks

Ekran Resmi 2021-03-18 18 29 34
Ruppsn commented 3 years ago

I complete 3 installation and always after complete the blocks sync was not possible to access the dashboard anymore.

Wow, I just had this happen today. Been keeping an eye on the initial sync progress, and it really seems like right after it reached 100%, attempts to login stall at "Loading Bitcoin Core... This can take a while, please don't turn off your Umbrel!" Rebooted, same thing. I was so excited how well everything seemed to work while syncing, so this was an unexpected buzzkill. Maybe if I just leave it alone long enough? FINAL EDIT: I was just impatient, it's up and running smoothly!

Hey, So this screen goes eventually right? Should I wait for it to sync then is it gonna work? Thanks

Ekran Resmi 2021-03-18 18 29 34

For everyone else: If you see this. Just wait. Wait many hours!

At docker you can see whats going on with watch docker logs --tail=20 bitcoin

Just indexing some things. This can take a while.

lukechilds commented 3 years ago

Thanks @Ruppsn!

Yes that's correct, you really do just need to wait.

We're working on an update that will allow you to access the dashboard while this is happening so it can complete in the background.

OqpdbqpO commented 3 years ago

Thanks @Ruppsn!

Yes that's correct, you really do just need to wait.

We're working on an update that will allow you to access the dashboard while this is happening so it can complete in the background.

It is possible to access the dashboard while it is synching yet it is not possible to access the dashboard immediately after the synch. That is confusing. It feels like a step backwards. I was thinking that something went wrong. That's why I am here reading.

I just waited many hours like suggested by @Ruppsn and others in this thread. I was able to access the dashboard eventually.

SnapFyre commented 3 years ago

Running: watch docker logs --tail=20 bitcoin

Gave the following results (is "Disk space too low" correct? my SSD is 1TB and bitcoin core only about 5% complete):

Every 2.0s: docker logs --tail=20 bitcoin umbrel: Wed Apr 14 12:52:29 2021 2021-04-14T11:03:22Z net thread exit 2021-04-14T11:03:22Z torcontrol thread exit 2021-04-14T11:03:22Z Shutdown: In progress... 2021-04-14T11:03:23Z msghand thread exit 2021-04-14T11:03:52Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started 2021-04-14T11:03:52Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.02s) 2021-04-14T11:03:52Z scheduler thread exit 2021-04-14T11:03:52Z Writing 0 unbroadcast transactions to disk. 2021-04-14T11:03:52Z Dumped mempool: 0.003023s to copy, 0.012255s to dump Error: Disk space is too low! 2021-04-14T11:03:53Z FlushStateToDisk: write coins cache to disk (5521741 coins, 785176kB) started 2021-04-14T11:03:53Z Disk space is too low! 2021-04-14T11:03:53Z Error: Disk space is too low! 2021-04-14T11:03:53Z FlushStateToDisk: write coins cache to disk (5521741 coins, 785176kB) completed (0.00s) 2021-04-14T11:03:53Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!) 2021-04-14T11:03:53Z Disk space is too low! 2021-04-14T11:03:53Z Error: Disk space is too low! 2021-04-14T11:03:53Z ForceFlushStateToDisk: failed to flush state (Disk space is too low!) Error: Disk space is too low! 2021-04-14T11:03:59Z Shutdown: done

Ruppsn commented 3 years ago

What is the Output of

docker inspect --format {{.Mounts}} bitcoin

Is this the PATH to your Disk?

lukechilds commented 3 years ago

@SnapFyre are you able to run:

df -h

and paste the output here?

Did you SSH in and manually run the start script? Maybe your SSD isn't mounted and your syncing to the SD card?

SnapFyre commented 3 years ago

docker inspect --format {{.Mounts}} bitcoin

@Ruppsn

output: umbrel@umbrel:~ $ docker inspect --format {{.Mounts}} bitcoin [{bind /home/umbrel/umbrel/bitcoin /data/.bitcoin rw true rprivate}]

I'm sorry, I don't know how to check the path.

SnapFyre commented 3 years ago

@lukechilds

output:

umbrel@umbrel:~ $ df -h Filesystem Size Used Avail Use% Mounted on /dev/root 15G 14G 39M 100% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs 1.9G 191M 1.7G 11% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mmcblk0p1 253M 30M 223M 12% /boot tmpfs 380M 0 380M 0% /run/user/1000 overlay 15G 14G 39M 100% /var/lib/docker/overlay2/cb5f93cb66cd37382d189cab18350f233019fb3f236c81db2d9f8567d381db8c/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/3a6f5e631abaf52117461e75d5d3282c8365f2bdaedd7f02058fe3bdf8dea454/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/898e8534d3b10b8b04d26106ac6394926c419c38102da0f0b835557190992c57/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/d94556edefb32fb182a0d5a931c7842c0c55d2a6c5bde0076c8e6ca355bf661e/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/4538f59e7a5e6c8dfcfc748f35b30a2fbdc71b0bb29c1b665ac49a18f809e8ca/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/59f74a4de154fe76583eb8957641e91a12af385d31180069c91186e48da8c6d9/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/619e4fa3a385ddfe7e69fff23ea49dc61cfcaa2fdbf29b4877802a8ef17db7b7/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/8d65c53cc038a21e122e53b5e11a031dc113ae4b4e1de6f82f35d4bb550960b7/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/a187436dae289db59d0cf434f4c6be5c922efed042de28d58c0cdad00a992d6c/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/23a7fe6447caef60108a171419b7a67da61aa96492e467deddcaed4bfc762de0/merged overlay 15G 14G 39M 100% /var/lib/docker/overlay2/de3caa378db2a5b761f2bf6f19f142d020d9ae897e197a63855fff6360f1bf14/merged

Yes, I manually run the script as I could not connect via umbrel.local nor it's IP address.

Ruppsn commented 3 years ago

On a RaspberryPi i don´t believe that home is on your SSD.

Your output of dh -h doesn´t show a device with 1TB.

So your data is on SD Card.

SnapFyre commented 3 years ago

Ah, thank you..... how do I resolve this? Also how 'should' it have happened (why did I have to start it manually)?

lukechilds commented 3 years ago

I can see from the output here:

/dev/root 15G 14G 39M 100% /

Your SD card is full, it looks like Umbrel is running on your SD card, not your SSD.

If there is a problem with your SSD, Umbrel OS will not start Umbrel to prevent this. If you SSH in and manually start it, that can cause issues.

Apologies, I know this is a little unclear. Once we've implemented this https://github.com/getumbrel/umbrel/issues/632 we'll detect issues like this and instead of doing nothing, it will show a web page at umbrel.local explaining what went wrong and how you can resolve it.

For now you can check what went wrong manually by running:

journalctl -u umbrel-startup.service

I would expect the last few lines of the logs to print some sort of error related to your external storage.

SnapFyre commented 3 years ago

Thank you both once again.

output:

umbrel@umbrel:~ $ journalctl -u umbrel-startup.service -- Logs begin at Wed 2021-04-14 09:57:10 UTC, end at Wed 2021-04-14 13:31:07 UTC. -- Apr 14 12:37:45 umbrel systemd[1]: Dependency failed for Umbrel Startup Service. Apr 14 12:37:45 umbrel systemd[1]: umbrel-startup.service: Job umbrel-startup.service/start failed with result 'dependen...skipping... -- Logs begin at Wed 2021-04-14 09:57:10 UTC, end at Wed 2021-04-14 13:31:07 UTC. -- Apr 14 12:37:45 umbrel systemd[1]: Dependency failed for Umbrel Startup Service. Apr 14 12:37:45 umbrel systemd[1]: umbrel-startup.service: Job umbrel-startup.service/start failed with result 'dependen~

lukechilds commented 3 years ago

My apologies that was the wrong command, that's the Umbrel service not the external storage service. Can you run this:

journalctl -u umbrel-external-storage.service
SnapFyre commented 3 years ago

Ah, yes:

umbrel@umbrel:~ $ journalctl -u umbrel-external-storage.service -- Logs begin at Wed 2021-04-14 09:57:10 UTC, end at Wed 2021-04-14 13:37:44 UTC. -- Apr 14 12:36:03 umbrel systemd[1]: Starting External Storage Mounter... Apr 14 12:36:03 umbrel external storage mounter[12392]: Running external storage mount script... Apr 14 12:36:03 umbrel external storage mounter[12392]: No block devices found Apr 14 12:36:03 umbrel external storage mounter[12392]: Waiting for 5 seconds before checking again... and it goes on...... Waiting for 5 seconds before checking again...

The SSD is new. Should I format it and try again? Also should I clear the SD card and re-flash umbrel?

SnapFyre commented 3 years ago

I should have mentioned I'm using an Orico case/caddy with an 'internal' SSD.

lukechilds commented 3 years ago

The SSD is new. Should I format it and try again?

Umbrel should format it, but yes definitely worth a try.

Also should I clear the SD card and re-flash umbrel?

Yes, you'll need to do that to reclaim the space since it's currently full with blockchain data.

I should have mentioned I'm using an Orico case/caddy with an 'internal' SSD.

Are you using the officially recommended hardware on our website? The Pi can be quite sensitive to different hardware, we've tested the recommended hardware extensively.

Also, could be worth checking the SSD is definitely inserted into the enclosure properly and plugged into the connected.

Plugging into your PC and formatted would be a good test, just to see if your PC can detect it.

SnapFyre commented 3 years ago

Are you using the officially recommended hardware on our website? The Pi can be quite sensitive to different hardware, we've tested the recommended hardware extensively.

Not the exact same one, no. I have an older Orico case: https://www.amazon.co.uk/Orico-External-Enclosure-Support-Windows-Red/dp/B07VV9QW99/ref=sr_1_2?dchild=1&keywords=orico+case+red&qid=1618408167&sr=8-2

Plugging into your PC and formatted would be a good test, just to see if your PC can detect it.

Ok, I'll try that and report back. Anyway using ssh to shut it down or should I just pull the power out?

lukechilds commented 3 years ago

Great, keep us posted!

To shutdown you can run:

sudo poweroff
SnapFyre commented 3 years ago

Ok, so I re-flashed.... And now I feel like a tool because I had 2 cases of the same colour one of which had an old 500GB HDD in it, so of course I had plugged in the wrong one. I have connected the proper SSD and it worked first time using umbrel/local, blockchain now syncing. I feel like I have wasted your time but I have learned so much so thank you!

So, I came back an hour later and now umbrel/local no longer works - explorer saying "refused to connect" I tried to ssh in with umbrel@umbrel.local but moneyprintergobrrr nor my password is working despite multiple attempts. I have tried (myusername)@umbrel.local with both default password and my own set password. I keep getting permission denied. My password contains a special character, could this be a problem?

Thanks again for your time.

Ruppsn commented 3 years ago

Was exactly the same when i installed and synced the first time. Bitcoin doesnt seem to allow connections if the chain is still incomplete.

I waited till 100% (and some hours after that cuz my logs showed me some indexing and this took some time).

Just wait till 100%

I watched the progress with

docker-compose logs -f --tail=50 bitcoin

Your should see some progress although umbrell UI is not working (for now)

SnapFyre commented 3 years ago

Thanks. I will wait then. The only problem is that I can't view progress as I can't access using ssh due to the the password not working.

lukechilds commented 3 years ago

You can SSH with:

ssh umbrel@umbrel.local

The password should be either moneyprintergobrrr or the password you set in the dashboard. Do neither of those work?

SnapFyre commented 3 years ago

Non of them work. Last night I had no response at all from http://umbrel.local so I removed the ethernet cable, waited for a few seconds and cycled the power on the Pi. Now http://umbrel.local shows the loading screen and stops on "Loading Bitcoin Core... " but I still get permission denied when trying to SSH in with either password.

lukechilds commented 3 years ago

Ok, you're likely hitting this bug https://github.com/getumbrel/umbrel-manager/pull/87 which has been fixed, but not yet released.

Can you log out of the dashboard, then log back in again. Then you should be able to SSH in with your dashboard password.

SnapFyre commented 3 years ago

Ok good to know, thanks. I can't access the dashboard as it's stuck on the loading screen.

Update: Beta version has fixed this. Thanks for all your hard work.