Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Electrum-Server not starting: blocked with log entry: blockchain reorg #4

Open
swat69 opened this issue Apr 5, 2018 · 2 comments
Open

Comments

@swat69
Copy link
Contributor

swat69 commented Apr 5, 2018

After normal working the Electrum-Server stopped working with:
[04/04/2018-17:00:23] Reorg limit is 100 blocks.
[04/04/2018-17:00:23] Blockchain height 2007406
[04/04/2018-17:00:23] UTXO tree root hash: a9ffe3bc1b822be0c88a53cc6922a3cde4fb1f40898aa0ecf329146464ddaa76
[04/04/2018-17:00:23] Coins in database: 14792711798999996
[04/04/2018-17:00:23] TCP server started on 127.0.0.1:50001
[04/04/2018-17:00:23] SSL server started on 127.0.0.1:50002
[04/04/2018-17:00:26] blockchain reorg 2007406 5140ffae95cf7e982ef3af2050dd1132f9cc8450f2a717292818eff9a27dfcd5 f498d1b0b984422284bf94e051eff573939a52d86182d17b65ba496afec51ae3
^^
Server stopped working here

After the next 'Electrum-Server start':
[05/04/2018-22:23:43] Starting Electrum server on 127.0.0.1
[05/04/2018-22:23:43] Database version 3.
[05/04/2018-22:23:43] Pruning limit for spent outputs is 100.
[05/04/2018-22:23:43] Reorg limit is 100 blocks.
[05/04/2018-22:23:43] Blockchain height 2007406
[05/04/2018-22:23:43] UTXO tree root hash: a9ffe3bc1b822be0c88a53cc6922a3cde4fb1f40898aa0ecf329146464ddaa76
[05/04/2018-22:23:43] Coins in database: 14792711798999996
[05/04/2018-22:23:43] TCP server started on 127.0.0.1:50001
[05/04/2018-22:23:43] SSL server started on 127.0.0.1:50002
[05/04/2018-22:23:49] blockchain reorg 2007406 5140ffae95cf7e982ef3af2050dd1132f9cc8450f2a717292818eff9a27dfcd5 f498d1b0b984422284bf94e051eff573939a52d86182d17b65ba496afec51ae3
^^
at this point nothing is happening, the Electrum-Server is blocked again.
This happened a few dozen times during the last months.

Only solution as far as I know: Restore the electrumDB from a previous copy taken when Electrum-Server not running (offline backup).

@justinvforvendetta
Copy link
Member

strange, usually its fine after a reorg

@justinvforvendetta
Copy link
Member

the other weird thing is this never affects my tor electrum servers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants