Skip to content

Collator with remote RPC stopped working after enacting v1.6.0 Kusama release #3059

@pmensik

Description

@pmensik

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

We are operating a handful of collators in the Kusama ecosystem - all of them experienced a halt in block production after the upgrade but eventually recovered and started producing blocks again. However, one of them (Moonriver) never actually did and I keep seeing these messages in the collator log (nothing suspicious other than this).

[Relaychain] Received finalized block via RPC: #21570139 (0x5e26…ba48 -> 0xf487…caf8)
[Relaychain] Received imported block via RPC: #21570142 (0x8450…a5b0 -> 0xcd69…63e0)
[Relaychain] Failed to handle incoming network message err=ImplicitViewFetchError(ProspectiveParachainsUnavailable)

So, in the end, the collator is working fine but cannot pass blocks to the relay.
This is our systemd config file

ExecStart=/usr/local/bin/moonriver \
  --name Polkadotters \
  --base-path '/var/lib/moonriver' \
  --telemetry-url 'wss://telemetry.polkadot.io/submit/ 0' \
  --collator \
  --state-pruning 256 \
  --blocks-pruning 256 \
  --port 31333 \
  --prometheus-port 9625 \
  --prometheus-external \
  --rpc-port 9923 \
  --trie-cache-size 0 \
  --db-cache 32000 \
  --chain moonriver \
#  --relay-chain-rpc-url ws://38.242.253.84:9944 \
#  --relay-chain-rpc-url ws://178.170.48.153:9944 \
  --relay-chain-rpc-url wss://rpc.dotters.network/kusama \

We have tried multiple RPCs (including public ones like IBP) but the message remains the same. Strange is that we have multiple collators depending on these remote RPCs but this is the only one that failed to recover after the upgrade.

Steps to reproduce

As far as I know, we are the only ones experiencing the problem so it might be hard to reproduce.

Metadata

Metadata

Assignees

No one assigned

    Labels

    I10-unconfirmedIssue might be valid, but it's not yet known.I2-bugThe node fails to follow expected behavior.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions