Open pseudozach opened 2 months ago
ping @CharlieC3 @obycode @kantai
interesting issue that i haven't seen before
this was from a node that was at chain tip, and this happened on a restart.
@pseudozach can you copy/paste your current chainstate dir? (ls -alh
is probably fine
this was from a node that was at chain tip, and this happened on a restart. @pseudozach can you copy/paste your current chainstate dir? (
ls -alh
is probably fine
sure
zach@lnswap-1:~/stacks-blockchain-docker/persistent-data/testnet/stacks-blockchain/xenon/chainstate$ ls -alh
total 9.7M
drwxr-sr-x 5 root zach 4.0K Apr 8 01:48 .
drwxr-sr-x 4 root zach 4.0K Apr 8 01:48 ..
drwxr-sr-x 59329 root zach 1020K Apr 8 01:48 blocks
drwxr-sr-x 2 root zach 4.0K Apr 8 01:48 estimates
-rw-r--r-- 1 root zach 8.6M Apr 8 01:48 mempool.sqlite
-rw-r--r-- 1 root zach 12K Mar 25 17:01 tx_tracking.sqlite
drwxr-sr-x 3 root zach 4.0K Apr 8 01:48 vm
Can you run ls -lah
on the xenon/burnchain
directory as well?
this may have been a config issue with the working_dir
key, but let's leave it open in case it comes up again.
i've asked @pseudozach to collect logs in the case it stalls again. currently the node is working as expected.
I have a testnet node that had stalled at height
153329
so I restarted it and now it's failing with below error and starts to sync from scratch.There was nothing changed on the file system so it can't be any permission or DB issue.
cc @wileyj
I definitely have data so not sure why it's somehow inaccessible, here's the folder contents as requested by jw
update - it's same behavior after restoring chainstate from hiro archives and also same with both
2.5.0.0.0-rc1
andnext
image