question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Electrum Service Failed

See original GitHub issue

Hi there, im having an issue to get the electrum service to run properly. LN and BTC are both running fine.

I get the following code:

*** LAST 20 ElectRS LOGS *** sudo journalctl -u electrs -b --no-pager -n20 – Journal begins at Sat 2022-11-05 06:47:31 GMT, ends at Sat 2022-11-05 20:17:40 GMT. – Nov 05 20:16:42 raspberrypi systemd[1]: electrs.service: Consumed 8.208s CPU time. Nov 05 20:16:42 raspberrypi systemd[1]: Started Electrs. Nov 05 20:16:42 raspberrypi electrs[973427]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_path: “/mnt/hdd/app-storage/electrs/db/bitcoin”, daemon_dir: “/home/electrs/.bitcoin”, daemon_auth: UserPass(“raspibolt”, “<sensitive>”), daemon_rpc_addr: 127.0.0.1:8332, daemon_p2p_addr: 127.0.0.1:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, disable_electrum_rpc: false, server_banner: “Welcome to electrs v0.9.7 - the Electrum Rust Server on your RaspiBlitz”, args: [] } Nov 05 20:16:42 raspberrypi electrs[973427]: [2022-11-05T20:16:42.479Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224 Nov 05 20:16:42 raspberrypi electrs[973427]: [2022-11-05T20:16:42.479Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001 Nov 05 20:16:42 raspberrypi electrs[973427]: [2022-11-05T20:16:42.636Z INFO electrs::db] “/mnt/hdd/app-storage/electrs/db/bitcoin”: 1953 SST files, 56.666234871 GB, 4.696112756 Grows Nov 05 20:16:46 raspberrypi electrs[973427]: [2022-11-05T20:16:46.604Z INFO electrs::chain] loading 761240 headers, tip=000000000000000000022fa13b5abb217c073ed005a73834cb886470af426678 Nov 05 20:16:50 raspberrypi electrs[973427]: [2022-11-05T20:16:50.412Z INFO electrs::chain] chain updated: tip=000000000000000000022fa13b5abb217c073ed005a73834cb886470af426678, height=761240 Nov 05 20:16:50 raspberrypi electrs[973427]: [2022-11-05T20:16:50.455Z INFO electrs::index] indexing 635 blocks: [761241…761875] Nov 05 20:16:50 raspberrypi electrs[973427]: thread ‘p2p_loop’ panicked at ‘invalid message: OversizedVectorAllocation { requested: 12000072, max: 4000000 }’, src/p2p.rs:250:70 Nov 05 20:16:50 raspberrypi electrs[973427]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Nov 05 20:16:50 raspberrypi electrs[973427]: [2022-11-05T20:16:50.647Z INFO electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin Nov 05 20:16:50 raspberrypi electrs[973427]: Error: electrs failed Nov 05 20:16:50 raspberrypi electrs[973427]: Caused by: Nov 05 20:16:50 raspberrypi electrs[973427]: 0: sync failed Nov 05 20:16:50 raspberrypi electrs[973427]: 1: failed to get block 000000000000000000070742427fa10ec3c66d006160155a704d9f56d090a3ea Nov 05 20:16:50 raspberrypi electrs[973427]: 2: receiving on an empty and disconnected channel Nov 05 20:16:50 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE Nov 05 20:16:50 raspberrypi systemd[1]: electrs.service: Failed with result ‘exit-code’. Nov 05 20:16:50 raspberrypi systemd[1]: electrs.service: Consumed 8.190s CPU time.

*** ElectRS Status ***

STATUS ELECTRS SERVICE

configured=1 serviceInstalled=1 serviceRunning=0 serviceRunning=0 tipSynced=0 initialSynced=0 electrumResponding=0 infoSync=‘Not running - check: sudo journalctl -u electrs’

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
istiecommented, Nov 8, 2022

Small update Needed to update LND to 0.15.4-beta as well to get it working again. This was also suggested by @vv01f in #3406 Now it’s all is working fine again.

I suppose you get the same result with the new image (1.8.0c) from @rootzoll which he prepared very quickly. Thanks again for all the hard work and support, I really appreciate it.

0reactions
mattias232commented, Nov 10, 2022

thanks for your help guys - i’ve followed advise here and all is now working

Read more comments on GitHub >

github_iconTop Results From Across the Web

[urgent] Update LND and electrs due to a critical bug as soon ...
Electrum Server Status shows this error in logs: Nov 01 07:11:46 mynoder systemd[1]: electrs.service: Failed with result 'exit-code'.
Read more >
My Electrum Wallet is not Connecting
To connect directly to the Electrum server, try using port 50001. This will avoid the proxy that verifies the certificates. First, find your...
Read more >
All The Reasons You've Failed To Connect Electrum to Your ...
All The Reasons You've Failed To Connect Electrum to Your Node Via Tor · Step 1: Run a node, run a node, run...
Read more >
Electrum RS Not working? : r/raspiblitz - Reddit
I am running RaspiBlitz v 1.8.0b with the lnd 0.15.2 update. This morning I noticed that my lightning node was not running properly....
Read more >
electrs.service: Failed with result 'signal' - myNode
I'm having trouble with my Electrum Server reporting an error and failing to start. Electrs reports an error " Failed with result 'signal' ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found