Apparently so. I’ve now created and funded another account (see my other thread about hooking this thing up to an existing account, so I’m not breeding accounts like gerbils), and got the exact same result.
Here is what I got when I launched sandbox today:
$ ./sandbox up testnet
Starting sandbox for: testnet
see sandbox.log for detailed progress, or use -v.
* started!
algod version
12885032963
3.2.3.stable [rel/stable] (commit #d2289a52)
go-algorand is licensed with AGPLv3.0
source code available at https://github.com/algorand/go-algorand
Indexer version
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "cmd/algorand-indexer/algorand-indexer": stat cmd/algorand-indexer/algorand-indexer: no such file or directory: unknown
and this is what showed up in Docker:
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"ALGOD_SHA\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"ALGOD_URL\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"ALGOD_BRANCH\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"NETWORK_BOOTSTRAP_URL\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"NETWORK_GENESIS_FILE\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"ALGOD_CHANNEL\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"INDEXER_DISABLED\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"INDEXER_URL\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"INDEXER_BRANCH\" variable is not set. Defaulting to a blank string."
time="2022-01-19T13:52:46-08:00" level=warning msg="The \"INDEXER_SHA\" variable is not set. Defaulting to a blank string."
algorand-sandbox-algod | Algorand node successfully started!
algorand-sandbox-algod | Algorand node successfully started!
algorand-sandbox-algod | Algorand node successfully started!
algorand-sandbox-postgres |
algorand-sandbox-postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization
algorand-sandbox-postgres |
algorand-sandbox-postgres | 2022-01-18 21:53:08.825 UTC [1] LOG: starting PostgreSQL 13.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
algorand-sandbox-postgres | 2022-01-18 21:53:08.825 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
algorand-sandbox-postgres | 2022-01-18 21:53:08.825 UTC [1] LOG: listening on IPv6 address "::", port 5432
algorand-sandbox-postgres | 2022-01-18 21:53:08.911 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
algorand-sandbox-postgres | 2022-01-18 21:53:08.996 UTC [13] LOG: database system was shut down at 2022-01-15 00:53:02 UTC
algorand-sandbox-postgres | 2022-01-18 21:53:09.636 UTC [1] LOG: database system is ready to accept connections
algorand-sandbox-postgres | 2022-01-18 22:45:23.034 UTC [71] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-18 23:15:24.536 UTC [101] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:07:26.795 UTC [153] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:13:27.741 UTC [159] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:14:27.261 UTC [17] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:14:38.248 UTC [160] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:16:27.375 UTC [162] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:38:28.564 UTC [17] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 00:38:39.326 UTC [184] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 01:00:29.578 UTC [206] LOG: using stale statistics instead of current ones because stats collector is not responding
algorand-sandbox-postgres | 2022-01-19 01:16:47.842 UTC [1] LOG: received fast shutdown request
algorand-sandbox-postgres | 2022-01-19 01:16:47.846 UTC [1] LOG: aborting any active transactions
algorand-sandbox-postgres | 2022-01-19 01:16:47.857 UTC [1] LOG: background worker "logical replication launcher" (PID 19) exited with exit code 1
algorand-sandbox-postgres | 2022-01-19 01:16:47.858 UTC [14] LOG: shutting down
algorand-sandbox-postgres |
algorand-sandbox-postgres | PostgreSQL Database directory appears to contain a database; Skipping initialization
algorand-sandbox-postgres |
algorand-sandbox-postgres | 2022-01-19 21:50:33.198 UTC [1] LOG: starting PostgreSQL 13.5 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20211027) 10.3.1 20211027, 64-bit
algorand-sandbox-postgres | 2022-01-19 21:50:33.198 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
algorand-sandbox-postgres | 2022-01-19 21:50:33.198 UTC [1] LOG: listening on IPv6 address "::", port 5432
algorand-sandbox-postgres | 2022-01-19 21:50:33.335 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
algorand-sandbox-postgres | 2022-01-19 21:50:33.419 UTC [13] LOG: database system shutdown was interrupted; last known up at 2022-01-19 01:16:47 UTC
algorand-sandbox-postgres | 2022-01-19 21:50:44.702 UTC [13] LOG: database system was not properly shut down; automatic recovery in progress
algorand-sandbox-postgres | 2022-01-19 21:50:44.763 UTC [13] LOG: redo starts at 0/15CFE50
algorand-sandbox-postgres | 2022-01-19 21:50:44.763 UTC [13] LOG: invalid record length at 0/15CFFB0: wanted 24, got 0
algorand-sandbox-postgres | 2022-01-19 21:50:44.763 UTC [13] LOG: redo done at 0/15CFF38
algorand-sandbox-postgres | 2022-01-19 21:50:45.259 UTC [1] LOG: database system is ready to accept connections
algorand-sandbox-indexer | Starting server at port 8980
algorand-sandbox-indexer | Response code (400)
algorand-sandbox-indexer | message (Indexer disabled for this configuration.)
algorand-sandbox-indexer | Starting server at port 8980
algorand-sandbox-indexer | Response code (400)
algorand-sandbox-indexer | message (Indexer disabled for this configuration.)
Does sandbox need to be reinitialized in some way? I remember seeing a lengthy catch-up process the first time I launched it, a few days ago, but not yesterday or today.
I started Docker first; then I launched Sandbox from a terminal session; then I launched VSCode, and then I started “Getting Started” (this time without the debugger, and this time without importing the newly-created account into my Wallet). Am I missing something?
UPDATE
I found the “Fast Catchup not working in Sandbox” thread on this forum, and saw a reference to “./sandbox goal version -v”; I tried it (once I realized “goal” was a subcommand of “sandbox,” and not a command in and of itself), and got
$ ./sandbox goal version -v
Version: [v1 v2]
GenesisID: testnet-v1.0
Build: 3.2.3.stable [rel/stable] (commit #d2289a52)
and then I found the “status” subcommand
$ ./sandbox status
algod - goal node status
Last committed block: 1025065
Time since last block: 0.0s
Sync Time: 2159.9s
Last consensus protocol: https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0
Next consensus protocol: https://github.com/algorandfoundation/specs/tree/5615adc36bad610c7f165fa2967f4ecfa75125f0
Round for next consensus protocol: 1025066
Next consensus protocol supported: true
Last Catchpoint:
Genesis ID: testnet-v1.0
Genesis hash: <REDACTED>
indexer - health
Indexer disabled for this configuration.
UPDATE
I tried “./sandbox reset” and “./sandbox clean” among other things, and then, after the latter, did a “./sandbox up -v testnet” and still “no joy.”
Then I looked at the video again: In the video, “indexer - health” is immediately followed by “Indexer disabled for this configuration” and then “Starting fast-catchup . . . .”; when I run it, I get (as above):
OCI runtime exec failed: exec failed: container_linux.go:380: starting container
process caused: exec: "cmd/algorand-indexer/algorand-indexer": stat cmd/algorand-indexer/algoran
d-indexer: no such file or directory: unknown
And yet, I distinctly recall seeing it behave like the video, the very first time I ran it.