-
Notifications
You must be signed in to change notification settings - Fork 789
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
Api called for an unknown Block: Header was not found in the database #670
Comments
@tdimitrov you are working on this or? |
Yes, this is the fix: paritytech/polkadot#7013 I've described details about the problem in paritytech/polkadot#7009 |
Just noticed that this happens during sync. On our test network it occurred when scraping dispute votes from the runtime. @anignatev could you please confirm if this happens during sync or while the node is operating? |
@tdimitrov As you can see from the log above, the node was in the operating status. |
Our nodes also keep falling out of sync and it happens atleast twice a day. We had same issue with v0.9.40 but downgrading to v0.9.39-1 resolved it. Now its back with v0.9.41 upgrade. Below are some logs - ubuntu@kusama-1: |
Unfortunately, the error is hapend on version 0.9.39-1: Configuration and hardware is the same as in my first post, logs:
|
This problem is addressed by paritytech/polkadot#6993 and paritytech/polkadot#7013 They will be included in the next release. |
Still happens on Kusama as of 0.9.43 @tdimitrov |
Seems to happen only in dispute-distribution. What could be the reason is that we are out of sync and just cannot find the block. I would expect a not found error or something not a "not supported" in that case. We are using the relay parent of the disputed block to fetch the session info. If session info was not yet cached (session boundary) this would fail, if we had that block not yet imported. If this is the reason the warning is harmless as the sender will just retry until we have seen the block in question or have fetched the session info by other means. We should then make the error correct (block is missing) and demote to debug. Session change around the time of the incident just confirmed by @slumber . |
* Move tests to one file. * Progress on test refactor * Fixed tests * Finish test cleanup. * Tests refactor
Bumps [actions/setup-node](/~https://github.com/actions/setup-node) from 1 to 3. - [Release notes](/~https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v1...v3) --- updated-dependencies: - dependency-name: actions/setup-node dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
After updating from v0.9.40 to v0.9.41, A bug has been detected that causes the node to fail and disable validation.
Role of the node: validator.
Startup type: run compiled binary
Version: v0.9.41
OS: FreeBSD 13.1-RELEASE-p3
Kernel: 13.1-RELEASE-p3
MemTotal: 64 GB
SwapTotal: 64 GB
CPU Type: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
CPU Threads: 12
Command-line options:
Logs (repeated many times):
The text was updated successfully, but these errors were encountered: