This is a bug.
Nothing changed on that front, 10.0.0 happens to perform a schema upgrade the same way we've done it before.
I opened https://github.com/stellar/stellar-core/issues/1791 with a workaround that should get you back in business.
If you could add some details to that issue with details that could help pinpoint the root cause, it would be great. ...
I think I have a better idea of how the stack works, and when it's safe to bring down the node without losing data.
If you're running CATCHUP_COMPLETE=true like me, core will first download the ledger files, then transaction files and then move on to the next checkpoint.
It looks something like this:
"state" : "Catching up",
"status" : [ "Catching up:...
It's better to stop the container using standard docker stop command, like docker stop stellar_quickstart.
Make sure that your docker container is running in persistent mode, otherwise you will lose current state (the database and all history) when the container is stopped.
The recommended way to switch between networks is to not reuse directories and/or archives (unless you can guarantee that you can delete all data). This particular error ... does not match previous NETWORK_PASSPHRASE ... will be cleared after running newdb as that command drops all tables in the database.
As for your later question, there is no vetting ...
I ended up scratching everything, recloning, and starting over from the installation guide. I believe my issue was in the configuration file. I tried several edits and reruns and honestly I'm not too sure what change fixed it.
Below is the config I used for a working LIVE instance.
My testnet version is identical except the history urls and ...
It looks like your Postgres server is either not installed or mis-configured. Can you connect to it from the command line?
You need to configure it to allow local connections. See https://www.postgresql.org/docs/9.1/auth-pg-hba-conf.html for more info.
There are multiple ways of installing stellar-core and stellar-horizon, Docker images, Apt packages (apt-get install), compile from source.
If you have access to a Ubuntu machine running 16.04 you can follow the instructions available https://github.com/stellar/packages/blob/master/README.md, the stellar-quickstart may be of interest to you for a Testnet ...
Ran into this issue today. I was able to check what the DATABASE_URL value that cmd horizon db migrate up expected by looking at horizon.env within the stellar/quickstart docker container. I then ran the command export DATABASE_URL=postgres://stellar:mypass@localhost/horizon && horizon db migrate up and migration was successful. Seems the env vars in ...
Question answered by bartekn at https://github.com/stellar/go/issues/461
Horizon requires Postgres >= 9.3. It's possible that other parts of
the system won't work as expected, even if you manage to pass horizon
db init command.