Electrs is syncing every time i try to access txid or bitcoin address

[martinbarilik]

Hi, every time i try to access anything ( txid, bitcoin address, ... ) electrs is suddenly syncing and it is impossible to to anything in BTC RPC Explorer or Mempool as electrs is unresponsible during the time.

I feel like its cache or something is deleted automatically for some reason, i can't access old nor new transactions. The syncing takes seral minutes, therefore i am practially unable to use anything when i need it.

Any idea what may cause this behaviour ?

[martinbarilik]

UPDATE 1

to add, Electrs states it's sync 100 %. When i open mempool and fill in a bitcoin address, it's working ( for the first time ), but every time i fill in another ( different ) bitcoin address or txid, it suddenlly stoppes working and when i check electrs, it says it's syncing

same bug goes for btc rpc explorer and when it happens i can't use sparrow as well ( which is kinda obvious )

bitcoin core is 100 % synced

end of logs/status-monitor.log

du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408241.ldb': No such file or dir$
du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408242.ldb': No such file or dir$
du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408244.ldb': No such file or dir$
du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408238.ldb': No such file or dir$
du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408239.ldb': No such file or dir$
du: cannot access '/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin/indexes/txindex/408750.ldb': No such file or dir$

Any idea ?

[niko-underwood]

I am experiencing the same issue on my Umbrel node. Each time I try to query an address using Mempool, Electrs changes to “waiting for Bitcoin node to finish syncing”. Has anyone found what might be causing this to happen?

[jimbrend]

@niko-underwood & @martinbarilik do you all mind to share a recent debug log? You can paste a link from pastebin for easier review if you'd like. We can first check for any errors.

We can move on to reinstalling electrs with the command:

sudo ~/umbrel/scripts/app uninstall electrs

Then reinstall with command:

sudo ~/umbrel/scripts/app install electrs

It takes on average about 24 hours for electrs to finish syncing if the Bitcoin Node recently finished syncing to 100%

Let me know if when reinstalling either step outputs any errors and we can further troubleshoot

[niko-underwood]

@Jimsb - Here are the debug logs from Umbrel:

https://pastebin.com/HryZbEuF

Let me know if anything stands out here.

Thanks!

[jimbrend]

@niko-underwood The only thing sticking out to me right now from the logs is your uptime is 11 hours and I'm suspecting maybe Bitcoin Node fell out of sync when something occurred causing your Umbrel to reboot 11 hours from when you posted the log- many of the recent blocks have more data so I assume maybe it is falling out of sync.

Upon relaunching Bitcoin Node app it may say 100%, but can you confirm if it is ~784792/784792 not something like 784780/784792? It may show the latter while it looks like it's at 100% but still require to catch up- this has been happening a lot recently with power intemittent issues combined with large blocks.

If that's not the case let me know if you are still having the issue and we can further investigate, and can I confirm it is not a pruned now either? Having a pruned node would also cause an error trying to access older or certain txid's and we can scratch that off the list. If you have reindex=1 in your bitcon.conf we would also want to remove that, or else it will attempt to reindex the entire blockchain upon each reboot.

Having edited the umbrel-lnd.conf file directly could also cause issues, and deleting that file and recreating it on a reboot can also solve a lot of issues as umbrel-lnd.conf shouldn't be edited- let me know if you changed any other manual settings.

[niko-underwood]

Hey @Jimsb - Thanks for the response! I wanted to update this thread and let you know that I have not been able to replicate the issue since my initial post. Everything seems to be working just fine. I didn't change or update anything other than just a reboot of the system. We can probably close this issue. Thanks again.