Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • Anything happened before this error appears? migration, another issue with a collator... Commented Aug 4, 2023 at 7:44
  • Another idea to check is this previous SE: substrate.stackexchange.com/questions/6724/… it might be a transaction in the pool that is slowing it down Commented Aug 4, 2023 at 7:45
  • No transactions or migrations. No appearances of issues with other collators. I hit the issue again last night, and I can see 🎁 Prepared block for proposing at 1683906 13 times across two collators (logs on the third are harder to get). They keep trying and eventually it gets through. Always getting Pool status: PoolStatus { ready: 0, ready_bytes: 0, future: 0, future_bytes: 0 } so no tx failing as far as I can tell. All the collators appear happy from a load perspective as well. Commented Aug 4, 2023 at 12:30
  • Can you open an issue in Cumulus with all the details and link your issue here as well? Commented Aug 4, 2023 at 20:24
  • Issue submitted: github.com/paritytech/cumulus/issues/2976 Also added a more recent log of the setup in case it is helpful: gist.github.com/wilwade/aa1f4ea8dace5938aa8e7a430b780eb1 Commented Aug 7, 2023 at 12:36