#Cannot restart a saved local quickstart

23 messages · Page 1 of 1 (latest)

echo nebula
#

When I run a local quickstart and use the -v flag to try and save the data (I don't like having to reboot all the contracts and accounts every time) I can't seem to get back into a workable state

stellar-core: Synced!; Publishing 6 queued checkpoints [527-567]: update-archives-0000020f:getting archives
supervisor: 2023-10-12 13:25:15,080 INFO spawned: 'history-archive' with pid 532
supervisor: 2023-10-12 13:25:15,092 INFO exited: history-archive (exit status 127; not expected)
supervisor: 2023-10-12 13:25:17,105 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-10-12 13:25:17,117 INFO spawned: 'soroban-rpc' with pid 541
supervisor: 2023-10-12 13:25:18,116 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
stellar-core: Synced!; Publishing 7 queued checkpoints [527-575]: update-archives-0000020f:getting archives
supervisor: 2023-10-12 13:25:23,136 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-10-12 13:25:23,149 INFO spawned: 'soroban-rpc' with pid 586
soroban rpc: waiting for ready state, 1 minutes...
supervisor: 2023-10-12 13:25:24,143 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-10-12 13:25:25,150 INFO spawned: 'history-archive' with pid 613
supervisor: 2023-10-12 13:25:25,157 INFO exited: history-archive (exit status 127; not expected)
supervisor: 2023-10-12 13:25:29,179 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-10-12 13:25:29,182 INFO spawned: 'soroban-rpc' with pid 637
stellar-core: Synced!; Publishing 8 queued checkpoints [527-583]: update-archives-0000020f:getting archives
supervisor: 2023-10-12 13:25:30,182 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-10-12 13:25:35,135 INFO exited: soroban-rpc (exit status 1; not expected)
supervisor: 2023-10-12 13:25:35,212 INFO spawned: 'soroban-rpc' with pid 677
supervisor: 2023-10-12 13:25:36,221 INFO spawned: 'history-archive' with pid 692
supervisor: 2023-10-12 13:25:36,221 INFO success: soroban-rpc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
supervisor: 2023-10-12 13:25:36,223 INFO exited: history-archive (exit status 127; not expected)
stellar-core: Synced!; Publishing 9 queued checkpoints [527-591]: update-archives-0000020f:getting archives
#

soroban-rpc and friendbot keep exiting

prime moon
#

Did you use the same path for persisting the data that you used previously maybe

echo nebula
#

I don't understand the question

prime moon
#

You give docker a path locally to store the data rught

#

And if that path was already used

#

In the past for an old version of quickstart

echo nebula
#

I run this

docker run --rm -it \
    -p "8000:8000" \
    -v "./opt/stellar:/opt/stellar" \
    --name stellar \
    stellar/quickstart:testing \
    --local \
    --enable-soroban-rpc

then at some point I kill it with docker stop stellar
then at some later point I re-run the above command. It starts fine with the -v "./opt/stellar:/opt/stellar" but then gets into a state of killing the rpc and friendbot

echo nebula
prime moon
#

Ok hmm. Check your /opt/stellar folder and check your configs? Its odd should just work but i can test it myself in a little bit?

echo nebula
#

It should just work
But it's not

mortal pivot
#

Sounds like a bug.

#

Can you open an issue?

prime moon
mortal pivot
#

Could you rerun it with --logs and share output?

prime moon
#

Sure i can but itll be a little bit i am out picking up my kids

echo nebula
#

fwiw I've noticed if I'm able to stop the container with Control + C I can restart the container later just fine. However when my output does this number (see screenshot) which it does a lot, Control + C doesn't register on my terminal. So I then use docker stop stellar which is when I enter the unrecoverable state.

mortal pivot
#

Are you running the container with -i or -it?

#

I think in docs we might include the t, but it is unnecessary and is what is causing the funky output above.

echo nebula
#

I'll try -i and see if it helps at all

prime moon
#

@echo nebula which OS are you on

#

look i had mine working today and then i noticed that i mapped the persistent directory to a non existent location... so i restarted it with a valid location and it no longer does anything