Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
2 tasks done
pmensik opened this issue Jan 25, 2024 · 5 comments
Closed
2 tasks done
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@pmensik
Copy link
Contributor

pmensik commented Jan 25, 2024

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.

@pmensik pmensik added I10-unconfirmed Issue might be valid, but it's not yet known. I2-bug The node fails to follow expected behavior. labels Jan 25, 2024
@bkchr
Copy link
Member

bkchr commented Jan 25, 2024

What polkadot version are you using currently? I think you are just running a too old version.

@pmensik
Copy link
Contributor Author

pmensik commented Jan 25, 2024

@bkchr All our RPCs are up to date (1.6), I believe the public ones like IBP as well. Like I said, the strange thing is that it works with all other collators so it might be something Moonriver-specific.

@bkchr
Copy link
Member

bkchr commented Jan 25, 2024

I'm talking about the Moonriver nodes. They are using an outdated polkadot version, leading to this issue.

This is the pr that fixed the underlying issue here. The moonriver node needs to include this fix. It was included in Polkadot 1.4.0.

CC @crystalin

@pmensik
Copy link
Contributor Author

pmensik commented Jan 25, 2024

@bkchr Thanks a lot, now it's clear!

@bkchr bkchr closed this as completed Jan 25, 2024
@bkchr
Copy link
Member

bkchr commented Jan 25, 2024

Given that this is an issue in a downstream project, I'm going to close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

No branches or pull requests

2 participants