No block created at Ethereum on Azure

asked 2020-08-24T00:59:46.263+00:00
Aoki Nobuaki 61 Reputation points

I set up Parity blockchain network using Ethereum on Azure template sold at market place.
It had worked well before, but suddenly had stopped to create blocks.
For example, when I deployed a contract, no block number was not issued.

There is a warning message (Fallback to `BlockId::Latest) in the log file of Parity.

2020-08-06 08:19:54 UTC IO Worker #1 INFO import 2/25 peers 504 KiB chain 169 MiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 35 μs
2020-08-06 08:20:24 UTC IO Worker #1 INFO import 2/25 peers 972 KiB chain 169 MiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 0 req/s, 35 μs
2020-08-06 08:20:53 UTC jsonrpc-eventloop-0 WARN parity_rpc::v1::impls::eth Fallback to BlockId::Latest
2020-08-06 08:20:59 UTC IO Worker #1 INFO import 2/25 peers 75 KiB chain 169 MiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 21 req/s, 21 μs
2020-08-06 08:21:29 UTC IO Worker #2 INFO import 2/25 peers 75 KiB chain 169 MiB db 0 bytes queue 10 KiB sync RPC: 0 conn, 5 req/s, 34 μs

Please help me to fix this issue.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
23,668 questions
{count} votes

Accepted answer
  1. answered 2020-08-26T17:54:22.337+00:00
    Shrc-MSFT 226 Reputation points

    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

    1. the validator contract has changed
    2. 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.


0 additional answers

Sort by: Most helpful