Sandbox testnet fast-catchup remains at processing accounts [0/1000] 0%

TestNet
1

Trying to use the sandbox on windows with WSL2. Have tried in Ubuntu and also in Windows Terminal with ubuntu. Have the latest versions of sandbox, ubuntu, goal, everything.

When starting fast-catchup with catchpoint, will proceed to process all accounts, then verify all accounts, then download 1000 blocks.
Then the output is continuously as below, with incrementing block # and round etc:

#Last committed block: 19263493
Time since last block: 0.5s
Sync Time: 0.0s
Last consensus protocol: GitHub - algorandfoundation/specs at bc36005dbd776e6d1eaf0c560619bb183215645c
Next consensus protocol: GitHub - algorandfoundation/specs at bc36005dbd776e6d1eaf0c560619bb183215645c
Round for next consensus protocol: 19263494
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: testnet-v1.0
Processing accounts: : [ ] [0/1000] 0%

Can anyone help? Been trying to fix this for over a week. Thanks

1 Like
2

I’m wondering if it’s just a display issue.

Can you Ctrl-C it and then run

./sandbox status

[EDIT: it was written ./sandbox goal status before which was incorrect]

If you see

algod - goal node status
Last committed block: 19250677
Time since last block: 0.0s
Sync Time: 10.4s
Last consensus protocol: https://github.com/algorandfoundation/specs/tree/bc36005dbd776e6d1eaf0c560619bb183215645c
Next consensus protocol: https://github.com/algorandfoundation/specs/tree/bc36005dbd776e6d1eaf0c560619bb183215645c
Round for next consensus protocol: 19250678
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: testnet-v1.0
Genesis hash: SGO1GKSzyE7IEPItTxCByw9x8FmnrCDexi9/cOUJOiI=

indexer - health
Indexer disabled for this configuration.

with the last committed block matching the last round on testnet.algoexplorer.io, you are just hitting a display issue.

In that case, please open an issue with all the details in GitHub - algorand/sandbox: Algorand node sandbox and link it there.

1 Like
3

Its weird.

Error: unknown command “status” for “goal”.

No command for status in goal -h. A new problem haha

4

I think you are right though that it might be a display issue

5

Sorry made a typo. Fixed now, can you try it?
(./sandbox status)

6

The block numbers are matching

7

This sounds rather like what I was experiencing when I used the workaround I was given in this thread: Sandbox fails to complete initialization on testnet -- it doesn't even try to "fast-catchup." Can anybody help?

8

Hi James, thanks for your assistance. It seems like you had the same issue. In your most recent update - do you mean the docker “getting started” tutorial? thanks

*edit - I tried this - didn’t help. As you mentioned in your other post, I am just getting a repetitive update without the sync finishing and returning to a command prompt

edit “solution” - I’ve realised everything is working fine, sync is up to date with the latest block. However I need to ctrl+c to stop it and the display still says 0/1000 0%. Once I stop it, I can use sandbox and goal commands as expected.

9

Uh, no, the Algorand “Getting Started” Java class, on the “Your First Transaction” page for Java.

10

Try a few more times
I encountered the same problem, and I just “ctrl+c” and “./sandbox up testnet”, then it worked. After that, “./sandbox status” will show that the block is 25x xxxx, I think it’s connected to the testnet.

11

(post deleted by author)

12

How to solve this problem? My last committed block does not matching the last round on testnet.algoexplorer.io

Screenshot 2023-09-05 235543
Screenshot 2023-09-05 235543931Ă—507 93.3 KB

13

You have custom setup in your sandbox (you do not have indexer and you are on testnet). Try reseting everything and make sure you delete also the docker drives.

Perhaps its related to this algokit issue i had recently algokit localnet start - ledger does not have entry 1 · Issue #320 · algorandfoundation/algokit-cli · GitHub