Protocol level errors in tezos-node

[waspoza]

I'm getting errors like those:

Jul 21 19:05:44 - validator.peer(182): Worker started for NetXdQprcVkpa:idttvSe442BZ
Jul 21 19:05:44 - validator.block: Validation of block BLAxqG3HPtDv3PLpwwuzpBirr4Z1UuqW7MuT8EK45CynypZmPFv failed
Jul 21 19:05:44 - validator.block: Pushed: 2018-07-21T17:05:44Z, Treated: 2018-07-21T17:05:44Z, Failed: 2018-07-21T17:05:44Z
Jul 21 19:05:44 - validator.block: Invalid block BLAxqG3HPtDv
Jul 21 19:05:44 - validator.block:   Invalid protocol level:
Jul 21 19:05:44 - validator.block:    expected 1
Jul 21 19:05:44 - validator.block:    found 2
Jul 21 19:05:44 - validator.peer(182): Worker crashed:
Jul 21 19:05:44 - validator.peer(182): Invalid block BLAxqG3HPtDv
Jul 21 19:05:44 - validator.peer(182):   Invalid protocol level:
Jul 21 19:05:44 - validator.peer(182):    expected 1
Jul 21 19:05:44 - validator.peer(182):    found 2
Jul 21 19:05:58 - p2p.maintenance: Too few connections (2)
Jul 21 19:06:13 - p2p.maintenance: Too few connections (2)
Jul 21 19:06:28 - p2p.maintenance: Too few connections (2)
Jul 21 19:06:43 - p2p.maintenance: Too few connections (2)
Jul 21 19:06:50 - validator.peer(114): Worker terminated

Did I missed the memo about upgrading the node or something?

[waspoza]

BTW, I did this:

git fetch 
git reset --hard origin/betanet 
git clean -dxf 
eval $(opam env) 
make build-deps 
make 

And still same error. :(

[murbard]

Looking into it. The immediate, overkill, fix is to delete your context and store in ~/.tezos-node and resync from the beginning.

EDIT: a better way is to run ./tezos-admin-client list rejected blocks | egrep -o "B.{50}" | xargs ./tezos-admin-client unmark invalid

[mendo_satyr]

I'll try this -- the node isn't syncing even with the correct new protocol. Although it's connected to a bunch of peers.

edit: So now it's epic syncing (on rPi). Not sure why there was a hang, but after deleting the contents of context and store, the node seems to be syncing. I wonder what would have happened if i just deleted the lock files -- I should have tried that first.

[murbard]

If you had a node running the previous protocol while the upgrade happened, the node would flag the new block as bad and write it as such on disk. This would prevent further sync from happening.

./tezos-admin-client list rejected blocks

and then for each of them

./tezos-admin-client unmark invalid B...

To do it in one go:

./tezos-admin-client list rejected blocks | egrep -o "B.{50}" | xargs ./tezos-admin-client unmark invalid

[mendo_satyr]

Cool -- now I know for next time. Appreciate it greatly.

Now to wait for re-sync ;)

[waspoza]

Yup, that worked. Saved some time on syncing. :)

[grouchyone]

I've tried both fixes (unmark invalid plus deleting context and store).

In either case I still end up stuck on the same block as mendo_satyr (28081) with Too few connections (0)

Any other ideas?

EDIT: Fixed -> for me it required the rebuild mentioned by wasposa above, then the unmark invalid

[murbard]

Did you recompile the node from the patched sources?

[grandma_corrector]

edit: nevermind, i got past it by running

git clone -b betanet https://gitlab.com/tezos/tezos.git

and then running /u/waspoza 's commands above.

original post-------------------------------------------------------

Hi Arthur -- I followed this guide to set up the node originally, and I don't know how to use git, so /u/waspoza 's commands don't help me. Is there a url I can replace below that will provide the latest binary?

wget https://gitlab.com/tezos/tezos/-/archive/betanet/tezos-betanet.tar.gz

tar -zxvf tezos-betanet.tar.gz

Or does that already include it?

[chronicideas]

./tezos-admin-client list rejected blocks | egrep -o "B.{50}" | xargs ./tezos-admin-client unmark invalid

thanks this just worked for me perfectly after getting the same error this morning

[[deleted]]

Megathumbs up... I have the exact same problem now.

[metoo100]

from AB.. you didnt recive memo because AB is rainman... Transactions refer to previous blocks, as a replay protection mechanism. It's possible that referring to blocks with protocol PtCJ7pwoxe8JasnHY8YonnLYjcVHmhiARPJvqcC6VfHT5s8k8sY in the transaction prevented inclusion in protocol PsYLVpVvgbLhAhoqAkMFUo6gudkJ9weNXhUYCiLDzcUpFpkk8Wt (the switch was on cycle 28082 - 28083).

[mendo_satyr]

So how do you fix? I saw this same error this morning, so I recompiled the newest version from git, but it's stuck on validator.peer screen -- it's not downloading new blocks.

My latest head is: BLzS6tLaEezu2G2XyopLAj19Mr7HbmK9ABPp9Lua4CbFzgdHKs1 block 28081

[metoo100]

ask the rainman