Gaia-8001 Hotfix

There was an issue with the v0.24.1 release where the wal (write ahead log) was not being rotated properly which lead to runaway disk usage. We have a fix on the v0.24.2-rc0 tag that will fix the issue with just an instance restart. To upgrade:

$ cd $GOPATH/src/github.com/cosmos/cosmos-sdk

# if there are changes locally (gopkg.lock commonly) you should stash them
$ git stash 
$ git fetch
$ git checkout v0.24.2-rc0
$ make install
$ gaiad version
0.24.2-0bf061b

Note: Running with systemctl I was unable to get the service to shut down with a systemctl stop. I had to stop the service then kill -9 the gaiad process that was running. After that I was able to bring the service back up with systemctl start gaiad

It looks like this fix might not have gotten to the underlying issue, but the wal can be cleared by instance restart: https://github.com/tendermint/tendermint/issues/2259#issuecomment-415191032

Follow the github issue for updates.

Expected behavior is for the wal file to grow ~1GB on v0.24.2 and then stabilize

yes, the hotfix is working well in a new install

jack:

0.24.2-0bf061b

should be
0.24.2-0bf061b7 right?

For me is only working in a new clean install in a validator node. after the update and made some test, in other nodes, I can’t have this working good. don’t follow the steps for now imo don’t help. maybe try a new clean install steps for the hotfix work For Update the Hotfix upgrade ``` Stop gaiad cd go/src/github.com/cosmos/cosmos-sdk git fetch --tags git checkout v0.24.2-rc0 make get_vendor_deps make install start gaiad ``` then for the cs.wal problem need … du -h ~/.gaiad/ 24G /home/cosmosvlondon/.gaiad/data/cs.wal 429M /home/cosmosvlondon/.gaiad/data/blockstore.db ``` Stop gaiad cd .gaiad/data rm -r cs.wal/* ``` du -h ~/.gaiad/ 4,0K /home/cosmosvlondon/.gaiad/data/cs.wal 429M /home/cosmosvlondon/.gaiad/data/blockstore.db ``` cd ../ ~/.gaiad$ cp -r data/ $HOME gaiad unsafe_reset_all Gaiad start ``` Wait for sync some blocks almost 11 or 1 ``` Stop gaiad sudo rm -r data/* cd cp -r data/* .gaiad/data rm -rf data (or not) Start gaiad ``` have to sync since last block you backup and no cs.wal problems. Like du -h ~/.gaiad/ 11M /home/cosmosvlondon/.gaiad/data/cs.wal 436M /home/cosmosvlondon/.gaiad/data/blockstore.db ``` gaiacli status…

Excerpt (1199 of 2571 characters). Read the whole post on the forum ↗

Yes its the same.that is for ubuntu

30G	/root/.gaiad/data/cs.wal
31G	/root/.gaiad/data
31G	/root/.gaiad
[root@cosmos-us ~]# gaiad version
0.24.2-0bf061b

runs on Centos 7.2. This bug is not fixed .