UTC Stage 1 block verification failed

[aas312]

Before filing a new issue, please provide the following information.

I'm running:

• Parity version: 1.6.8,1.7.2
• Operating system: Ubuntu
• And installed: https://github.com/dstarcev/parity-poa-playground

I am running the https://github.com/dstarcev/parity-poa-playground. On member0 I get the error UTC Stage 1 block verification failed
I have checked time.is and my time is exact.
Block numbers on authority0, 1, and 2 are same
Block numbers on member0, 1 and 2 are same
But blocknumbers on member nodes are different than on authority nodes

---

[5chdn]

please report at https://github.com/dstarcev/parity-poa-playground

or follow our demo poa tutorial https://github.com/paritytech/parity/wiki/Demo-PoA-tutorial

[aas312]

I think this is related to the parity docker image and not with the parity-poa-playground.

[5chdn]

Please share the full logs please.

[aas312]

logs.txt

[aas312]

[aas312]

[aas312]

So I deleted the volumes which had the db data. After that it works.

[artjoma]

Parity 1.7.0 POA
Same problem :
2017-09-28 17:03:13 Starting Parity/v1.7.0-beta-5f2cabd-20170727/x86_64-linux-gnu/rustc1.18.0
2017-09-28 17:03:13 Keys path /home/ubuntu/parity/priv/keys/glpbank
2017-09-28 17:03:13 DB path /home/ubuntu/parity/....
2017-09-28 17:03:13 Path to dapps /home/ubuntu/parity/priv/dapps
2017-09-28 17:03:13 State DB configuration: fast
2017-09-28 17:03:13 Operating mode: active
2017-09-28 17:03:13 Configured for glpbank using AuthorityRound engine
2017-09-28 17:03:18 Public node URL: enode://d94b3eb14c1d559e129e031276e0b81d8e6ce31f0501bb10dd2805033e0e6451f0f26b7cd547d3bd3031846af774489ce0738a3679b2d01c5c5c9a33f4614cb9@x.x.x.x:30210
2017-09-28 17:03:21 Signal for transition within contract. New list: [00ea169ce7e0992960d3bde6f5d539c955316432, 0052fb1ca9659ada7db23796bae3041b5dbb9507]
2017-09-28 17:03:21 Applying validator set change signalled at block 6
2017-09-28 17:03:23 Syncing #4135 e3bf…19ab 414 blk/s 2 tx/s 0 Mgas/s 2977+ 0 Qed #7112 1/25 peers 1 MiB chain 2 MiB db 4 MiB queue 616 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-09-28 17:03:28 Syncing #14400 f778…d578 2053 blk/s 7 tx/s 20 Mgas/s 8332+ 0 Qed #22733 1/25 peers 4 MiB chain 5 MiB db 15 MiB queue 2 MiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-09-28 17:03:32 Stage 1 block verification failed for 6a96…e8af: Block(DifficultyOutOfBounds(OutOfBounds { min: None, max: Some(340282366920938463463374607431768211455), found: 340282366920938463463374607431768211456 }))
2017-09-28 17:03:33 Syncing #23904 02a5…e759 1900 blk/s 37 tx/s 79 Mgas/s 9378+ 0 Qed #25228 1/25 peers 6 MiB chain 10 MiB db 19 MiB queue 368 KiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-09-28 17:04:03 0/25 peers 3 MiB chain 17 MiB db 0 bytes queue 1 MiB sync RPC: 0 conn, 0 req/s, 0 µs
2017-09-28 17:04:33 0/25 peers 3 MiB chain 17 MiB db 0 bytes queue 1 MiB sync RPC: 0 conn, 1 req/s, 36 µs

[5chdn]

this happens if two validator nodes are using the same key to author blocks. duplicate of #5689

[jackieWhn]

@5chdn, i got this problem too. I use parity 1.7.8, two validator nodes, and each node has its own validator.

[jackieWhn]

@5chdn what do you mean the same key?

[5chdn]

please share how you run both nodes here