Hi, As per the logs shared by you it looks like the node is unable to seal/propose a block. This can happen either if
- the validator contract has changed
- the node got dropped from list of validators.
Can you please try restarting both the validator Vms in your resource group? This will result in running some setup automatically and might help in resuming mining. Please restart the first VM, once that is up, wait for a few mins and then restart the next VM. This is to ensure there there are no inconsistencies in the blockchain resulting from concurrent restarts.
I did not configure to use log analytics, so I cannot collect the logs from OMS workspace.
I attached the parity log file (/var/log/parity/parity.log) which was created in the virtual machine's file system.
At line 3353, the message "Fallback to
BlockId::Latest" is written.
At line 3357, the message that transaction is received is written.
At line 3358, the message that transaction is stored to txPool is written.
At lIne 3369, the message that transaction is sent to peers is written.
After that, no block was created.
The date in the logs is different with the fragment of logs I wrote in my question,
but the phenomenon was same that when I sent a transaction,
it was stored to txPool but no block was created.
Thanks for sharing the additional details. We are looking into this issue and update you as earliest. Appreciate your time and patience.