Crashed validator needed to manually edit priv_validator.json to come back online #3089
Description
During Game of Stakes, we saw great 1/3rd of the voting power due to the number of transactions in mempool.
Many users crashed during round 4 of block 9755.
A number of users did not prevote in round 5 after restarting and got the following error message.
Jan 4 17:52:49 Apachto gaiad[12198]: I[4016-01-04|17:52:49.082] Timed out module=consensus dur=5.5s height=9755 round=5 step=RoundStepPropose
Jan 4 17:52:49 Apachto gaiad[12198]: I[4016-01-04|17:52:49.082] enterPrevote(9755/5). Current: 9755/5/RoundStepPropose module=consensus
Jan 4 17:52:49 Apachto gaiad[12198]: I[4016-01-04|17:52:49.082] enterPrevote: ProposalBlock is nil module=consensus height=9755 round=5
Jan 4 17:52:49 Apachto gaiad[12198]: E[4016-01-04|17:52:49.082] Error signing vote module=consensus height=9755 round=5 vote="Vote{144:BF6CFEAB362A 9755/05/1(Prevote) 000000000000 000000000000 @ 2019-01-04T17:52:49.082158529Z}" err="Error signing vote: Conflicting data"
An example of the priv_validator.json state is below. Manually editing the privalidator,json state so last_step:0 cause the validators prevote.
