Launching Gaia-8000

Validation11 posts2,442 views21 likesLast activity Aug 2018

zakiOP

Aug 2018 9

Gaia-8000 failed because we don’t have good integration tests for byzantine behavior yet.

Gaia-8001 is launching. Launching Gaia-8001

Here is the upgrade procedure.

cd $GOPATH/src/github.com/cosmos/cosmos-sdk
gaiad unsafe_reset_all
git fetch --tags
git checkout v0.24.0
rm Gopkg.lock
make get_vendor_deps  && make install

gaiad version

0.24.0-d5652d96

if you get following error on gaiad unsafe_reset_all

Error reading PrivValidator from /cosmos/.gaiad/config/priv_validator.json: json: cannot unmarshal object into Go value of type []uint8

Checkout v0.23.1 and make and start over

download the genesis file https://raw.githubusercontent.com/cosmos/testnets/master/gaia-8000/genesis.json

Copy it to $HOME/.gaiad/config/genesis.json

put the following seeds in $HOME/.gaiad/config/config.toml

seeds = "7c8b8fd03577cd4817f5be1f03d506f879df98d8@gaia-seed1.interblock.io:26656, a28737ff02391a6e00a1d3b79befd57e68e8264c@gaia-seed2.interblock.io:26656, 987ffd26640cd03d08ed7e53b24dfaa7956e612d@gaia-seed3.interblock.io:26656,837ab35ee80e6882da08ab6244ef27538e73aedd@gaia-seed4.interblock.io:26656"

gaiad start

kochacolaj

Aug 2018

with v0.23.1 do

gaiad unsafe_reset_all

if u get

grouped write of manifest, lock and vendor: failed to export github.com/zondax/ledger-goclient: fatal: failed to unpack tree object 4296ee5701e945f9b3a7dbe51f402e0b9be57259

then do

cd $GOPATH/src/github.com/cosmos/
rm -rf cosmos-sdk
git clone https://github.com/cosmos/cosmos-sdk
cd cosmos-sdk
git fetch --tags
git checkout v0.24.0
make get_tools && make get_vendor_deps && make install

zaki

Aug 2018

Easier fix.

Just rm Gopkg.lock in $GOPATH/go/src/github.com/cosmos/cosmos-sdk

katernoir

Aug 2018 1

Here are some peers to connect to:

[email protected]:26656, [email protected]:26656

Happy gaia-8000 everyone

jack

Aug 2018 1

Seeds:

seeds = "7c8b8fd03577cd4817f5be1f03d506f879df98d8@gaia-seed1.interblock.io:26656, a28737ff02391a6e00a1d3b79befd57e68e8264c@gaia-seed2.interblock.io:26656, 987ffd26640cd03d08ed7e53b24dfaa7956e612d@gaia-seed3.interblock.io:26656,837ab35ee80e6882da08ab6244ef27538e73aedd@gaia-seed4.interblock.io:26656"

melea-trust

Aug 2018 3

error building make get_vendor_deps

cd go/src/github.com/cosmos/cosmos-sdk

rm Gopkg.lock

rm -rf .vendor-new

make get_vendor_deps && make install

melea-trust

Aug 2018 2

steps for update, no errors

gaiad unsafe_reset_all

cd go/src/github.com/cosmos/cosmos-sdk

git fetch --tags

rm Gopkg.lock

rm -rf .vendor-new

git checkout v0.24.0

make get_vendor_deps
(if need again  = rm Gopkg.lock and  rm .vendor_new)

make install

cd

cd .gaiad/config

rm genesis.json

wget -c 'https://raw.githubusercontent.com/cosmos/testnets/master/gaia-8000/genesis.json'

gaiad start

joepindar

Aug 2018 2

Some people (including block3.community) are getting the error:

~/.gaiad/config$ gaiad unsafe_reset_all
Error reading PrivValidator from /cosmos/.gaiad/config/priv_validator.json: json: cannot unmarshal object into Go value of type []uint8

The workaround is to:

rollback to release v0.23.1
gaiad unsafe_reset_all
upgrade to release v0.24.0

zaki

Aug 2018 1

Thanks for posting all the troubleshooting info.

I will update the post on the top with it in bit.

melea-trust

Aug 2018 1

No need roolback
Just need restore priv_validator.json
Unsafe reset
And is ok.

But if you can restore the priv_validator key.
Then maybe need roll-back

And if you just unsafe reset before update.
All is ok

ping

Aug 2018 1

melea-trust:

But if you can restore the priv_validator key.

Yes, this is another way to fix this issue.

← Back to Discussions