# Noeud Bitcoin Bloque sur "Starting"

**URL:** <https://community.umbrel.com/t/noeud-bitcoin-bloque-sur-starting/11652>\
**Category:** General Discussion\
**Created:** [February 27, 2023, 8:07pm UTC](https://community.umbrel.com/t/noeud-bitcoin-bloque-sur-starting/11652 "2023-02-27T20:07:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sancho](https://avatars.discourse-cdn.com/v4/letter/s/5daacb/32.png) [@sancho](https://community.umbrel.com/u/sancho)\
**Post date:** [February 27, 2023, 8:07pm UTC](https://community.umbrel.com/t/noeud-bitcoin-bloque-sur-starting/11652/1 "2023-02-27T20:07:05Z")

</div>

Bonjour

Mon Noeud Bitcoin reste en “Starting” , j’ai relancé Umbrel plusieurs fois mais rien n’y fait .  
Voici les logs

bitcoin

Attaching to bitcoin\_server\_1, bitcoin\_tor\_1, bitcoin\_i2pd\_daemon\_1, bitcoin\_tor\_server\_1, bitcoin\_bitcoind\_1, bitcoin\_app\_proxy\_1  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
app\_proxy\_1 | Validating token: 985553732b66 …  
bitcoind\_1 | 2023-02-27T19:47:30Z \* Using 46.7 MiB for basic block filter index database  
bitcoind\_1 | 2023-02-27T19:47:30Z \* Using 8.0 MiB for chain state database  
bitcoind\_1 | 2023-02-27T19:47:30Z \* Using 318.9 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)  
bitcoind\_1 | 2023-02-27T19:47:30Z init message: Loading block index…  
bitcoind\_1 | 2023-02-27T19:47:30Z Assuming ancestors of block 00000000000000000009c97098b5295f7e5f183ac811fb5d1534040adb93cabd have valid signatures.  
bitcoind\_1 | 2023-02-27T19:47:30Z Setting nMinimumChainWork=00000000000000000000000000000000000000003404ba0801921119f903495e  
bitcoind\_1 | 2023-02-27T19:47:30Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)  
bitcoind\_1 | 2023-02-27T19:47:30Z Opening LevelDB in /data/.bitcoin/blocks/index  
bitcoind\_1 | 2023-02-27T19:47:30Z Opened LevelDB successfully  
bitcoind\_1 | 2023-02-27T19:47:30Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000  
tor\_1 | Feb 27 19:42:50.000 [notice] Bootstrapped 62% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Feb 27 19:42:51.000 [notice] Bootstrapped 67% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Feb 27 19:42:52.000 [notice] Bootstrapped 73% (loading\_descriptors): Loading relay descriptors  
tor\_1 | Feb 27 19:42:53.000 [notice] Bootstrapped 75% (enough\_dirinfo): Loaded enough directory info to build circuits  
tor\_1 | Feb 27 19:42:53.000 [notice] Bootstrapped 80% (ap\_conn): Connecting to a relay to build circuits  
tor\_1 | Feb 27 19:42:55.000 [notice] Bootstrapped 85% (ap\_conn\_done): Connected to a relay to build circuits  
tor\_1 | Feb 27 19:42:55.000 [notice] Bootstrapped 89% (ap\_handshake): Finishing handshake with a relay to build circuits  
tor\_1 | Feb 27 19:42:56.000 [notice] Bootstrapped 90% (ap\_handshake\_done): Handshake finished with a relay to build circuits  
tor\_1 | Feb 27 19:42:56.000 [notice] Bootstrapped 95% (circuit\_create): Establishing a Tor circuit  
tor\_1 | Feb 27 19:42:57.000 [notice] Bootstrapped 100% (done): Done  
i2pd\_daemon\_1 | 19:42:15@465/none - i2pd v2.44.0 (0.9.56) starting…  
i2pd\_daemon\_1 | 19:42:27@70/error - Tunnels: Can’t select next hop for EAa~LCWmn1QZOa-nQbyazDn8QupqzIVbOoTfhx~brAY=  
i2pd\_daemon\_1 | 19:42:27@70/error - Tunnels: Can’t create inbound tunnel, no peers available  
i2pd\_daemon\_1 | 19:42:27@70/error - Tunnels: Can’t select next hop for EAa~LCWmn1QZOa-nQbyazDn8QupqzIVbOoTfhx~brAY=  
i2pd\_daemon\_1 | 19:42:27@70/error - Tunnels: Can’t create inbound tunnel, no peers available  
i2pd\_daemon\_1 | 19:42:52@910/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message  
i2pd\_daemon\_1 | 19:45:27@907/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.18 - - [Mon, 27 Feb 2023 19:47:37 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36”  
server\_1 |  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.18 - - [Mon, 27 Feb 2023 19:47:39 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36”  
server\_1 |  
server\_1 | umbrel-middleware  
server\_1 | ::ffff:10.21.0.18 - - [Mon, 27 Feb 2023 19:47:41 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10\_15\_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36”  
server\_1 |  
server\_1 | umbrel-middleware

Auriez vous une idée ?
