Need more information on this behaviour of polygon edge v0.6.0

[shubham-edx]

After updating to v0.6.0 I am frequently seeing the
following logs. as this process is started no new blocks are minted.
any information on this would be helpful.

0|node1 | 2022-09-29T06:14:05.062Z [INFO] polygon.blockchain: block already inserted: block=170997 source=syncer
0|node1 | 2022-09-29T06:14:17.054Z [INFO] polygon.ibft.consensus: round timeout expired: round=0
0|node1 | 2022-09-29T06:14:17.055Z [INFO] polygon.ibft.consensus: round started: round=1
0|node1 | 2022-09-29T06:14:39.057Z [INFO] polygon.ibft.consensus: round timeout expired: round=1
0|node1 | 2022-09-29T06:14:39.059Z [INFO] polygon.ibft.consensus: round started: round=2
0|node1 | 2022-09-29T06:15:21.060Z [INFO] polygon.ibft.consensus: round timeout expired: round=2
0|node1 | 2022-09-29T06:15:21.062Z [INFO] polygon.ibft.consensus: round started: round=3
0|node1 | 2022-09-29T06:16:43.064Z [INFO] polygon.ibft.consensus: round timeout expired: round=3
0|node1 | 2022-09-29T06:16:43.067Z [INFO] polygon.ibft.consensus: round started: round=4
0|node1 | 2022-09-29T06:16:43.068Z [INFO] polygon.ibft.consensus: we are the proposer

[ivanbozic21]

Hi @shubham-edx,

Can you please try to restart each of your validators one more time and let us know if this behavior will continue?

[shubham-edx]

restarted it.
still the same behavior.
this time it went upto 10 rounds.

[shubham-edx]

One of the validator has these logs.

[laviniat1996]

Hi @shubham-edx ,

Is this PoA or PoS? How many validators and bootnodes did you start your setup with? Are you running this locally or on cloud? Also, did you notice that this happens when you try to do a certain action (like sending a tx), or randomly?

[shubham-edx]

@laviniat1996 ,
This POS network has 8 validators which are running on 4 separate AWS instances.
I am sending mock tx from one account to random accounts. roughly 1 tx every 1 minute.?
if this is due to tx-pool DDos is there any way to empty tx pool?

[laviniat1996]

@shubham-edx

It looks like you have 12 validators. Did you stake from other accounts? If you have staked tokens in the staking contract, but those addresses are not validators (so you don’t have a node running for them), the chain will not work properly.

[shubham-edx]

Yes, correct. out of 12 validators, only 8 validators are running remaining 4 validators are not functional. I was under impression that at least 4 validators are enough for consensus to meet and blocks to be produced. this is not the case?

[laviniat1996]

@shubham-edx When you did the setup, did you start the network with 12 validators? Or only 8?

[shubham-edx]

I started it with 4. The other 8 were added via staking contract. out of those 8 validators, 4 are not running.
(the network was created at v0.5 then it was upgraded to 5.1 then yesterday it was upgraded to 0.6)

[laviniat1996]

Did you start seeing these issue for the first time when upgrading to v0.6.0?

[shubham-edx]

Yes correct.

[laviniat1996]

@shubham-edx If so, please make sure you fork the chain, because BLS is not compatible with the old release. You can find how to do it here: https://wiki.polygon.technology/docs/edge/consensus/bls/#3-add-fork-setting .