# Error: electrs failed --- Please Help
**URL:** https://community.umbrel.com/t/error-electrs-failed-please-help/5772
**Category:** Support and Troubleshooting
**Created:** [January 16, 2022, 11:28am UTC](https://community.umbrel.com/t/error-electrs-failed-please-help/5772 "2022-01-16T11:28:15Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Pablo](https://community.umbrel.com/u/Pablo)
#### Post date: [January 16, 2022, 11:28am UTC](https://community.umbrel.com/t/error-electrs-failed-please-help/5772/1 "2022-01-16T11:28:15Z")
Hello,
After working fine for months, my Umbrel has started to act up.
Specifically electrs, which appears to be failing.
Any wallet that I have connected to my node is no longer working because of this.
If I restart my Umbrel it appears to fix the problem, but only for about a day or so and then the problem comes back.
Any insight into how to fix this is very much appreciated.
## electrs logs
Attaching to electrs
electrs | [2022-01-16T05:22:49.710Z INFO electrs::chain] loading 718917 headers, tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14
electrs | [2022-01-16T05:22:56.482Z INFO electrs::chain] chain updated: tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14, height=718917
electrs | [2022-01-16T05:22:57.320Z INFO electrs::daemon] waiting for 31 blocks to download (IBD)
electrs | [2022-01-16T05:23:13.919Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs | Error: electrs failed
electrs |
electrs | Caused by:
electrs | 0: bitcoind RPC polling failed
electrs | 1: daemon not available
electrs | 2: JSON-RPC error: transport error: Didn’t receive response data in time, timed out.
electrs | Starting electrs 0.9.1 on aarch64 linux with Config { network: Bitcoin, db\_path: “/data/db/bitcoin”, daemon\_dir: “/data/.bitcoin”, daemon\_auth: CookieFile("/data/.bitcoin/.cookie"), daemon\_rpc\_addr: V4(10.21.21.8:8332), daemon\_p2p\_addr: V4(10.21.21.8:8333), electrum\_rpc\_addr: V4(0.0.0.0:50001), monitoring\_addr: V4(127.0.0.1:4224), wait\_duration: 10s, jsonrpc\_timeout: 15s, index\_batch\_size: 10, index\_lookup\_limit: Some(200), reindex\_last\_blocks: 0, auto\_reindex: true, ignore\_mempool: false, sync\_once: false, disable\_electrum\_rpc: false, server\_banner: “Umbrel v0.4.10”, args: [] }
electrs | [2022-01-16T05:23:17.154Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs | [2022-01-16T05:23:17.327Z INFO electrs::db] “/data/db/bitcoin”: 135 SST files, 33.413071687 GB, 4.160915982 Grows
electrs | [2022-01-16T05:23:23.218Z INFO electrs::chain] loading 718917 headers, tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14
electrs | [2022-01-16T05:23:28.008Z INFO electrs::chain] chain updated: tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14, height=718917
electrs | [2022-01-16T05:24:05.150Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs | Error: electrs failed
electrs |
electrs | Caused by:
electrs | 0: bitcoind RPC polling failed
electrs | 1: daemon not available
electrs | 2: JSON-RPC error: transport error: Didn’t receive response data in time, timed out.
electrs | Starting electrs 0.9.1 on aarch64 linux with Config { network: Bitcoin, db\_path: “/data/db/bitcoin”, daemon\_dir: “/data/.bitcoin”, daemon\_auth: CookieFile("/data/.bitcoin/.cookie"), daemon\_rpc\_addr: V4(10.21.21.8:8332), daemon\_p2p\_addr: V4(10.21.21.8:8333), electrum\_rpc\_addr: V4(0.0.0.0:50001), monitoring\_addr: V4(127.0.0.1:4224), wait\_duration: 10s, jsonrpc\_timeout: 15s, index\_batch\_size: 10, index\_lookup\_limit: Some(200), reindex\_last\_blocks: 0, auto\_reindex: true, ignore\_mempool: false, sync\_once: false, disable\_electrum\_rpc: false, server\_banner: “Umbrel v0.4.10”, args: [] }
electrs | [2022-01-16T05:24:08.659Z INFO electrs::metrics::metrics\_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs | [2022-01-16T05:24:08.759Z INFO electrs::db] “/data/db/bitcoin”: 136 SST files, 33.413072491 GB, 4.160915983 Grows
electrs | [2022-01-16T05:24:14.700Z INFO electrs::chain] loading 718917 headers, tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14
electrs | [2022-01-16T05:24:20.852Z INFO electrs::chain] chain updated: tip=0000000000000000000a2db0c046c471919a711cbdfd74cd1cc998fd77617e14, height=718917
electrs | [2022-01-16T05:24:33.040Z INFO electrs::daemon] waiting for 0 blocks to download (IBD)
electrs | [2022-01-16T05:24:34.087Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs | [2022-01-16T05:59:42.878Z INFO electrs::db] closing DB at /data/db/bitcoin
---
### Author:  [@DarthCoin](https://community.umbrel.com/u/DarthCoin)
#### Post date: [January 17, 2022, 10:51am UTC](https://community.umbrel.com/t/error-electrs-failed-please-help/5772/2 "2022-01-17T10:51:17Z")
Maybe you should look into how to delete the old electrs database and create a new clean one.
Start here
> **[GitHub - romanz/electrs: An efficient re-implementation of Electrum Server in...](https://github.com/romanz/electrs)**
>
> An efficient re-implementation of Electrum Server in Rust - GitHub - romanz/electrs: An efficient re-implementation of Electrum Server in Rust
and an interesting case here
>
>
> https://github.com/romanz/electrs/blob/v0.9.0-rc1/RELEASE-NOTES.md
>
> v0.9.0-rc1… is out
>
> it comes with a database format change so will reindex for a few hours.
> Will need to see how long it takes in the RPi before it is usable again.
---
### Author:  [@Pablo](https://community.umbrel.com/u/Pablo)
#### Post date: [January 17, 2022, 12:07pm UTC](https://community.umbrel.com/t/error-electrs-failed-please-help/5772/3 "2022-01-17T12:07:46Z")
Thank you for the response.
Unfortunately I do not see the instructions for how to do this in those links.
Is there a simple explanation on how to do this with the Umbrel?
Really appreciate any insight.