SBP Block Creation Issues on Feb 8 and 9 (Beijing time)
I've some v1.2.2 nodes without problems and some stuck at 7436783.
I've some 1.2.3-alpha4 nodes without problems and some stuck at 7436783.
Don't think node version is the cause/solution of the problem.
fonzie last edited by
@Umcka As others have pointed out, it doesn't seem to be a version issue. Hopefully, a fix is released soon.
@fonzie Probably. But at most 1.2.2 version affected. I've gathered some online stats (for 515 nodes):
1.2.3 ~ 11 full nodes affected with bug
1.2.2 ~ 24 full nodes run without issues, sync is ok
1.2.2 ~ 38 full nodes have 743***** bug.
Statistics is not lying in general. You can calculate total percent for every version.
Approximate numbers, near 25~30 nodes are new.
fonzie last edited by
@Umcka Hmm. I am still not convinced its something to do with the version.
Anyway, let's wait for the official word on this.
use 1.2.3-alpha4 and have a try with bellow way
@MrFox No source code and only just a binary, sounds a bit dangerous.
@plasmo you are right, so you can just wait for the next release version
This post is deleted!
I've made some research. You can check changes on Vite github repo for more details.
Since Vite team added changes recover option to go-vite main branch I've decided just compile source code by myself. After applying changes with recover command 743***** bug was fixed.
You can compile by yourself using guide:
Make sure you have you have installed gcc
Run your compiled file with command like:
./gvite -config /etc/vite/node_config.json recover -del=7436000
Then start your main (officially released version).
I've used 1.2.2 and 1.2.3alpha4 for further sync. Both successfully synced. Hope it will help for all until official release.
Binary file by MrFox - is compiled gvite. But there no info about any out-Vite additional changes.
PS Node can stuck few times on 7436783. Simply re-apply recover command again and restart sync.
viteshan last edited by
next release version must wait until the end of the month.
and there is a temporary gvite to solve this problem.
gvite_hotfix_20190219 is compiled for https://github.com/vitelabs/go-vite/tree/hotfix-20190209-viteshan