Hallo Forum. Ich habe mir ein Umbrel aufgesetzt und folgendes Problem:
Nach ein paar Tagen synchronisiert Mempool nicht mehr und bleibt auf dem Stand (wie auf dem Foto) vor 2 Wochen stehen.
Die Bitcoin Node selber synchronisiert problemlos weiter und ist auf aktuellem Stand. Wenn ich Umbrel neu starte synchronisiert auch dem Mempool wieder für ein paar Tage, bis es dann wieder stehen bleibt.
Hat jemand Rat?
Vielleicht hängt sich deine Datenbank auf. Oder der RAM ist ausgereizt / zu langsam. Vielleicht verliert auch die SSD kurzzeitig die Verbindung und dann reden die Komponenten nicht mehr miteinander. Bei einem Softwarepaket hat man immer das Problem, dass man auf den Maintainer angewiesen ist für Updates und eine Analyse von Fehlern ist schwieriger.
Es sieht nicht nach der aktuellsten Version von Mempool Space aus.
Ob das Problem damit zusammenhängt, kann ich nicht sagen.
Ohne in die Logs zu schauen, ist es wildes Rätselraten.
Der Screenshot ist von vor zwei Wochen? Der Stand dort ist auf jeden Fall von vor ca. 200 Tagen.
Meine Idee ist, dass sich dein Electrs/Fulcrum verabschiedet hat.
Ich meine, darauf greift Mempool Space zurück.
Das hättest du aber auch gemerkt, wenn du mit einer Wallet Software auf diese Dienste zurückgegriffen hättest. Das Wallet würde dir immer einen alten Stand anzeigen.
Die Screenshots sind aktuell von Heute.
Electrs ist per Webinterface erreichbar:
Hier das Logfile:
=====================
= Umbrel debug info =
Umbrel version
0.5.4
Memory usage
total used free shared buff/cache available
Mem: 4,1G 2,8G 122M 602K 1,4G 1,3G
Swap: 2,5G 1,8G 645M
total: 69.2%
mempool: 18.4%
electrs: 10.8%
bitcoin: 24%
system: 16%
Memory monitor logs
2024-05-04 11:51:54 Memory monitor running!
2024-05-04 11:52:13 Memory monitor running!
2024-05-04 11:52:30 Memory monitor running!
2024-05-04 11:52:48 Memory monitor running!
2024-05-04 11:55:46 Memory monitor running!
2024-05-06 07:22:38 Memory monitor running!
2024-05-06 07:27:28 Memory monitor running!
2024-05-06 07:33:28 Memory monitor running!
2024-05-15 07:49:42 Memory monitor running!
2024-05-20 21:34:48 Memory monitor running!
Filesystem information
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/ubuntu–vg-ubuntu–lv 12G 11G 434M 97% /
/dev/sdb 1,8T 730G 1011G 42% /home
Karen logs
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:04 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:05 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:06 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:07 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:08 --:–:-- 0
100 3325 100 146 100 3179 16 348 0:00:09 0:00:09 --:–:-- 749
100 3325 100 146 100 3179 15 348 0:00:09 0:00:09 --:–:-- 967
{„message“:„Successfully uploaded backup 1718345046876.tar.gz.pgp for backup ID 1bfbe27290bf52753fb44575ab1b28ef5f33d233b1fdf149ec00090e46d729ef“}
====== Backup success =======
Got signal: backup
karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
2304 bytes (2,3 kB, 2,2 KiB) copied, 0,000201201 s, 11,5 MB/s
Creating encrypted tarball…
backup/
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:04 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:05 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:06 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:07 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:08 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:09 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:10 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:11 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:12 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:13 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:14 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:15 --:–:-- 0
100 2976 100 146 100 2830 8 162 0:00:18 0:00:17 0:00:01 543
100 2976 100 146 100 2830 8 162 0:00:18 0:00:17 0:00:01 664
{„message“:„Successfully uploaded backup 1718379270326.tar.gz.pgp for backup ID 1bfbe27290bf52753fb44575ab1b28ef5f33d233b1fdf149ec00090e46d729ef“}
====== Backup success =======
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: backup
karen is getting triggered!
Deriving keys…
Creating backup…
Adding random padding…
1+0 records in
1+0 records out
5595 bytes (5,6 kB, 5,5 KiB) copied, 0,000218817 s, 25,6 MB/s
Creating encrypted tarball…
backup/
backup/.padding
Uploading backup…
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:03 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:05 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:06 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:07 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:08 --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- 0:00:08 --:–:-- 0
100 6260 100 146 100 6114 15 636 0:00:09 0:00:09 --:–:-- 1357
100 6260 100 146 100 6114 15 636 0:00:09 0:00:09 --:–:-- 1734
{„message“:„Successfully uploaded backup 1718396243478.tar.gz.pgp for backup ID 1bfbe27290bf52753fb44575ab1b28ef5f33d233b1fdf149ec00090e46d729ef“}
====== Backup success =======
Got signal: debug
karen is getting triggered!
Docker containers
NAMES STATUS
bitcoin_server_1 Up 3 weeks
electrs_app_1 Up 3 weeks
mempool_mariadb_1 Up 3 weeks
mempool_tor_server_1 Up 3 weeks
mempool_app_proxy_1 Up 3 weeks
mempool_web_1 Up 3 weeks
electrs_electrs_1 Up 3 weeks
bitcoin_tor_server_1 Up 3 weeks
bitcoin_bitcoind_1 Up 3 weeks
mempool_api_1 Up 3 weeks
bitcoin_i2pd_daemon_1 Up 2 weeks
bitcoin_tor_1 Up 3 weeks
electrs_app_proxy_1 Up 3 weeks
bitcoin_app_proxy_1 Up 3 weeks
electrs_tor_server_1 Up 3 weeks
electrs_tor_1 Up 3 weeks
nginx Up 3 weeks
auth Up 3 weeks
manager Up 3 weeks
dashboard Up 3 weeks
tor_proxy Up 3 weeks
tor_server Up 3 weeks
Umbrel logs
Attaching to manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:09 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:10 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:11 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:12 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:12 GMT] „GET /v1/system/update-status HTTP/1.0“ 200 91 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:13 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:13 GMT] „GET /v1/account/token?token=95fe2507d2737eb125f820ec5a481c1bda642b46bc12961247d8490bf6878120 HTTP/1.1“ 200 16 „-“ „app-proxy/0.0.1“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:13 GMT] „GET /v1/account/token?token=95fe2507d2737eb125f820ec5a481c1bda642b46bc12961247d8490bf6878120 HTTP/1.1“ 200 16 „-“ „app-proxy/0.0.1“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:13 GMT] „GET /v1/account/token?token=95fe2507d2737eb125f820ec5a481c1bda642b46bc12961247d8490bf6878120 HTTP/1.1“ 200 16 „-“ „app-proxy/0.0.1“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Fri, 14 Jun 2024 20:45:14 GMT] „GET /v1/system/debug-result HTTP/1.0“ 200 23 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
manager |
manager | umbrel-manager
Tor Proxy logs
Attaching to tor_proxy
tor_proxy | Jun 14 03:35:50.000 [notice] Heartbeat: Tor’s uptime is 24 days 6:00 hours, with 2 circuits open. I’ve sent 25.88 MB and received 73.61 MB. I’ve received 99 connections on IPv4 and 0 on IPv6. I’ve made 616 connections with IPv4 and 0 with IPv6.
tor_proxy | Jun 14 03:35:50.000 [notice] While bootstrapping, fetched this many bytes: 627867 (consensus network-status fetch); 14101 (authority cert fetch); 10864601 (microdescriptor fetch)
tor_proxy | Jun 14 03:35:50.000 [notice] While not bootstrapping, fetched this many bytes: 15806170 (consensus network-status fetch); 361587 (authority cert fetch); 21287539 (microdescriptor fetch)
tor_proxy | Jun 14 09:35:50.000 [notice] Heartbeat: Tor’s uptime is 24 days 12:00 hours, with 0 circuits open. I’ve sent 26.44 MB and received 76.09 MB. I’ve received 100 connections on IPv4 and 0 on IPv6. I’ve made 624 connections with IPv4 and 0 with IPv6.
tor_proxy | Jun 14 09:35:50.000 [notice] While bootstrapping, fetched this many bytes: 627867 (consensus network-status fetch); 14101 (authority cert fetch); 10864601 (microdescriptor fetch)
tor_proxy | Jun 14 09:35:50.000 [notice] While not bootstrapping, fetched this many bytes: 17722882 (consensus network-status fetch); 361587 (authority cert fetch); 21307478 (microdescriptor fetch)
tor_proxy | Jun 14 15:35:50.000 [notice] Heartbeat: Tor’s uptime is 24 days 18:00 hours, with 5 circuits open. I’ve sent 26.49 MB and received 76.31 MB. I’ve received 101 connections on IPv4 and 0 on IPv6. I’ve made 632 connections with IPv4 and 0 with IPv6.
tor_proxy | Jun 14 15:35:50.000 [notice] While bootstrapping, fetched this many bytes: 627867 (consensus network-status fetch); 14101 (authority cert fetch); 10864601 (microdescriptor fetch)
tor_proxy | Jun 14 15:35:50.000 [notice] While not bootstrapping, fetched this many bytes: 17777375 (consensus network-status fetch); 361587 (authority cert fetch); 21411498 (microdescriptor fetch)
tor_proxy | Jun 14 15:35:50.000 [notice] Average packaged cell fullness: 79.957%. TLS write overhead: 5%
App logs
bitcoin
Attaching to bitcoin_server_1, bitcoin_tor_server_1, bitcoin_bitcoind_1, bitcoin_i2pd_daemon_1, bitcoin_tor_1, bitcoin_app_proxy_1
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:14 GMT] „GET /v1/bitcoind/info/stats HTTP/1.1“ 200 127 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:18 GMT] „GET /v1/bitcoind/info/connections HTTP/1.1“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Fri, 14 Jun 2024 20:45:18 GMT] „GET /v1/bitcoind/info/stats HTTP/1.1“ 200 127 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
server_1 |
server_1 | umbrel-middleware
bitcoind_1 | 2024-06-14T20:23:56Z UpdateTip: new best=00000000000000000000427956b425f1e4970e8841b10a4c3e99fcc86c4aadef height=847939 version=0x20000000 log2_work=94.984223 tx=1024150662 date=‚2024-06-14T20:23:44Z‘ progress=1.000000 cache=101.1MiB(823771txo)
bitcoind_1 | 2024-06-14T20:34:01Z Saw new header hash=000000000000000000032dbb86a6f2523d8dbe09e4110fa545b2f7d14e716926 height=847940
bitcoind_1 | 2024-06-14T20:34:06Z UpdateTip: new best=000000000000000000032dbb86a6f2523d8dbe09e4110fa545b2f7d14e716926 height=847940 version=0x2a2de000 log2_work=94.984236 tx=1024155569 date=‚2024-06-14T20:33:26Z‘ progress=1.000000 cache=101.7MiB(828340txo)
bitcoind_1 | 2024-06-14T20:35:40Z Saw new header hash=0000000000000000000276d884722249e7fd552a9e4428327072bc9a29e5a882 height=847941
bitcoind_1 | 2024-06-14T20:35:40Z Saw new cmpctblock header hash=0000000000000000000276d884722249e7fd552a9e4428327072bc9a29e5a882 peer=239177
bitcoind_1 | 2024-06-14T20:35:45Z UpdateTip: new best=0000000000000000000276d884722249e7fd552a9e4428327072bc9a29e5a882 height=847941 version=0x22000000 log2_work=94.984249 tx=1024161911 date=‚2024-06-14T20:35:14Z‘ progress=1.000000 cache=102.0MiB(830494txo)
bitcoind_1 | 2024-06-14T20:35:46Z BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
bitcoind_1 | 2024-06-14T20:39:27Z Saw new header hash=00000000000000000000542e74d22d730367c0afe4ef0cf6f8e6a9e8f5b7022d height=847942
bitcoind_1 | 2024-06-14T20:39:27Z Saw new cmpctblock header hash=00000000000000000000542e74d22d730367c0afe4ef0cf6f8e6a9e8f5b7022d peer=239256
bitcoind_1 | 2024-06-14T20:39:31Z UpdateTip: new best=00000000000000000000542e74d22d730367c0afe4ef0cf6f8e6a9e8f5b7022d height=847942 version=0x24c4e000 log2_work=94.984263 tx=1024166788 date=‚2024-06-14T20:39:23Z‘ progress=1.000000 cache=102.3MiB(833726txo)
tor_1 | Jun 14 18:45:13.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 7153/7179). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 14 18:45:13.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 7153/7179). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 14 18:45:14.000 [notice] We now have enough directory information to build circuits.
tor_1 | Jun 14 18:49:45.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
i2pd_daemon_1 | 20:36:00@248/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:37:41@260/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 20:40:31@558/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:40:31@558/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:40:31@558/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:40:31@558/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:40:31@558/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
i2pd_daemon_1 | 20:41:39@686/error - Tunnel: Tunnel with id 586682520 already exists
i2pd_daemon_1 | 20:41:51@686/error - Tunnel: Tunnel with id 2104550298 already exists
i2pd_daemon_1 | 20:42:55@305/error - NetDb: YdGWrhxwc8aSnSYoq6hF61YogAl1F9RRoZPyhKiNIrU= destination requested, but no tunnels found
electrs
Attaching to electrs_app_1, electrs_electrs_1, electrs_app_proxy_1, electrs_tor_server_1, electrs_tor_1
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_proxy_1 | Validating token: 95fe2507d273 …
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.3 - - [Fri, 14 Jun 2024 20:44:59 GMT] „GET /v1/electrs/syncPercent HTTP/1.1“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
app_1 |
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.3 - - [Fri, 14 Jun 2024 20:45:09 GMT] „GET /v1/electrs/syncPercent HTTP/1.1“ 200 3 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
app_1 |
app_1 | umbrel-middleware
app_1 | ::ffff:10.21.0.3 - - [Fri, 14 Jun 2024 20:45:19 GMT] „GET /v1/electrs/syncPercent HTTP/1.1“ 200 3 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0“
app_1 |
app_1 | umbrel-middleware
electrs_1 | [2024-06-14T20:11:58.560Z INFO electrs::index] indexing 1 blocks: [847938…847938]
electrs_1 | [2024-06-14T20:11:59.314Z INFO electrs::chain] chain updated: tip=000000000000000000005cbb2503464289dbae42bde91a22406252c5d6d8824a, height=847938
electrs_1 | [2024-06-14T20:23:56.231Z INFO electrs::index] indexing 1 blocks: [847939…847939]
electrs_1 | [2024-06-14T20:24:03.108Z INFO electrs::chain] chain updated: tip=00000000000000000000427956b425f1e4970e8841b10a4c3e99fcc86c4aadef, height=847939
electrs_1 | [2024-06-14T20:34:07.248Z INFO electrs::index] indexing 1 blocks: [847940…847940]
electrs_1 | [2024-06-14T20:34:08.182Z INFO electrs::chain] chain updated: tip=000000000000000000032dbb86a6f2523d8dbe09e4110fa545b2f7d14e716926, height=847940
electrs_1 | [2024-06-14T20:35:57.404Z INFO electrs::index] indexing 1 blocks: [847941…847941]
electrs_1 | [2024-06-14T20:35:57.854Z INFO electrs::chain] chain updated: tip=0000000000000000000276d884722249e7fd552a9e4428327072bc9a29e5a882, height=847941
electrs_1 | [2024-06-14T20:39:31.575Z INFO electrs::index] indexing 1 blocks: [847942…847942]
electrs_1 | [2024-06-14T20:39:33.676Z INFO electrs::chain] chain updated: tip=00000000000000000000542e74d22d730367c0afe4ef0cf6f8e6a9e8f5b7022d, height=847942
tor_1 | Jun 14 09:37:13.000 [notice] While not bootstrapping, fetched this many bytes: 5861701 (consensus network-status fetch); 5052 (authority cert fetch); 21505364 (microdescriptor fetch)
tor_1 | Jun 14 15:37:13.000 [notice] Heartbeat: Tor’s uptime is 24 days 18:00 hours, with 9 circuits open. I’ve sent 313.19 MB and received 343.46 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 108 connections with IPv4 and 0 with IPv6.
tor_1 | Jun 14 15:37:13.000 [notice] While bootstrapping, fetched this many bytes: 627867 (consensus network-status fetch); 14101 (authority cert fetch); 10863008 (microdescriptor fetch)
tor_1 | Jun 14 15:37:13.000 [notice] While not bootstrapping, fetched this many bytes: 5891717 (consensus network-status fetch); 5052 (authority cert fetch); 21517621 (microdescriptor fetch)
tor_1 | Jun 14 15:52:28.000 [notice] No circuits are opened. Relaxed timeout for circuit 26243 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 109197ms. However, it appears the circuit has timed out anyway.
tor_1 | Jun 14 17:15:54.000 [notice] No circuits are opened. Relaxed timeout for circuit 26283 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 108899ms. However, it appears the circuit has timed out anyway.
tor_1 | Jun 14 18:25:09.000 [notice] No circuits are opened. Relaxed timeout for circuit 26284 (a Hidden service: Uploading HS descriptor 4-hop circuit in state doing handshakes with channel state open) to 84604ms. However, it appears the circuit has timed out anyway. [1 similar message(s) suppressed in last 4200 seconds]
tor_1 | Jun 14 20:06:37.000 [warn] Received http status code 404 („Not found“) from server 135.181.63.118:9100 while fetching „/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97“.
mempool
Attaching to mempool_mariadb_1, mempool_tor_server_1, mempool_app_proxy_1, mempool_web_1, mempool_api_1
app_proxy_1 | [HPM] Client disconnected
app_proxy_1 | [HPM] Upgrading to WebSocket
app_proxy_1 | [HPM] Client disconnected
app_proxy_1 | [HPM] WebSocket error: Error: read EHOSTUNREACH
app_proxy_1 | at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
app_proxy_1 | errno: -113,
app_proxy_1 | code: ‚EHOSTUNREACH‘,
app_proxy_1 | syscall: ‚read‘
app_proxy_1 | }
app_proxy_1 | [HPM] Upgrading to WebSocket
api_1 | May 24 23:18:33 [118] INFO: Core index ‚basic block filter index‘ is synced. Best block height is 844986
api_1 | May 24 23:18:44 [118] INFO: Latest BTC fiat averaged price: {„time“:1715760000,„USD“:68715,„EUR“:64406,„GBP“:58823,„CAD“:94116,„CHF“:62930,„AUD“:103790,„JPY“:10787970}
api_1 | May 24 23:19:37 [118] INFO: Some blocks are not indexed, skipping missing blocks during chain validation
api_1 | May 25 00:20:01 [118] INFO: Core index ‚txindex‘ is synced. Best block height is 844990
api_1 | May 25 00:20:02 [118] INFO: Core index ‚basic block filter index‘ is synced. Best block height is 844990
api_1 | May 25 00:20:10 [118] INFO: Latest BTC fiat averaged price: {„time“:1715760000,„USD“:68613,„EUR“:64300,„GBP“:58752,„CAD“:93860,„CHF“:62861,„AUD“:103661,„JPY“:10769847}
api_1 | May 25 00:20:48 [118] INFO: Some blocks are not indexed, skipping missing blocks during chain validation
api_1 | May 25 00:20:58 [118] INFO: [Mining] Daily network hashrate indexing completed: indexed 1 days
api_1 | May 25 00:45:13 [118] ERR: Cannot fetch tx 2072eb4c12039ac754e7e2946e3f9306406c2d099a9bd5264e2aa499ec903758. Reason: ETIMEDOUT
api_1 | May 25 00:46:13 [118] ERR: Cannot fetch tx e05470e5d6ac6ceec16fca01b82b2ef41d2eaee4143eed10daa86b8623ec2c30. Reason: ETIMEDOUT
web_1 | /var/www/mempool/browser/resources
mariadb_1 | 2024-05-20 21:38:13 0 [Note] Plugin ‚FEEDBACK‘ is disabled.
mariadb_1 | 2024-05-20 21:38:13 0 [Note] InnoDB: Buffer pool(s) load completed at 240520 21:38:13
mariadb_1 | 2024-05-20 21:38:13 0 [Note] Server socket created on IP: ‚::‘.
mariadb_1 | 2024-05-20 21:38:14 0 [Warning] ‚proxies_priv‘ entry ‚@% root@0473e9df1cff‘ ignored in --skip-name-resolve mode.
mariadb_1 | 2024-05-20 21:38:14 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2024-05-20 21:38:14 0 [Note] Added new Master_info ‚‘ to hash table
mariadb_1 | 2024-05-20 21:38:14 0 [Note] mysqld: ready for connections.
mariadb_1 | Version: ‚10.5.12-MariaDB-1:10.5.12+maria~focal‘ socket: ‚/run/mysqld/mysqld.sock‘ port: 3306 mariadb.org binary distribution
mariadb_1 | 2024-05-20 21:38:14 3 [Warning] Aborted connection 3 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.27‘ (This connection closed normally without authentication)
mariadb_1 | 2024-05-20 21:38:25 4 [Warning] Aborted connection 4 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.26‘ (This connection closed normally without authentication)
==== Result ====
==== END =====
Ich finde Docker zwar grundsätzlich cool, aber hatte bisher mehr Probleme als Nutzen damit. Ich habe nichts Dramatisches gesehen vermute einfach immer noch, dass es an der Verbindung zwischen Electrs und Mempool Space liegt.
Besonders auffällig ist die „Uraltversion“ von Umbrel. Je länger eine Software nicht geupdated wird, desto mehr komische Dinge können und werden passieren 
Ich hatte dasselbe Problem und Electrum sowie Mempool deswegen wieder gelöscht. Mein Tipp war auch meine veraltete Hardware (RAM und Prozessor liefen am Anschlag). Sollte dies nur das Symptom und nicht die Ursache sein, wäre eine Lösung super.
Das gleiche hatte ich auch bei einer meiner Raspipblitze auf VM.
Leistung ist bei mir also kein Thema.
Bei v1.09 hängt Mempool nach einer Zeit immer.
Bei v1.10 läuft es wieder.
Vermutlich gibt es in der älteren Version einen bug.
1 „Gefällt mir“
Das macht Hoffnung. Dann fiebere ich dem Update entgegen