Node Error: resource of type `BlockHeight` was not found at the: crates/fuel-core/src/database.rs:132

General
1

Hi guys! i got this error runnin testnet node. i updated chain-configuration folder and use nightly toolchain. can you help me?

telegram-cloud-photo-size-2-5341437426746384950-y
telegram-cloud-photo-size-2-5341437426746384950-y1280Ă—158 45.7 KB

my toolchain

Default host: x86_64-unknown-linux-gnu
fuelup home: /home/ubuntu/.fuelup

Installed toolchains
--------------------
latest-x86_64-unknown-linux-gnu
nightly-x86_64-unknown-linux-gnu (default)

active toolchain
----------------
nightly-x86_64-unknown-linux-gnu (default)
  forc : 0.63.1+nightly.20240820.169f91ae0a
    - forc-client
      - forc-deploy : 0.63.1+nightly.20240820.169f91ae0a
      - forc-run : 0.63.1+nightly.20240820.169f91ae0a
    - forc-crypto : 0.63.1+nightly.20240820.169f91ae0a
    - forc-debug : 0.63.1+nightly.20240820.169f91ae0a
    - forc-doc : 0.63.1+nightly.20240820.169f91ae0a
    - forc-fmt : 0.63.1+nightly.20240820.169f91ae0a
    - forc-lsp : 0.63.1+nightly.20240820.169f91ae0a
    - forc-tx : 0.63.1+nightly.20240820.169f91ae0a
    - forc-wallet : 0.9.0+nightly.20240820.29d9b25c2c
  fuel-core : 0.33.0+nightly.20240820.b1f2bf445a
  fuel-core-keygen : not found
2

Just to confirm, you are using these chain config, right?

3

yes, i updated chain-configuration folder to the latest version

4

same error here… deleting the database doesn’t work either

image
image2074Ă—294 39.3 KB

5

Thanks for confirming. Will make sure the team look into it

6

Team has identified the issue and it will be fixed in fuel-core v0.34.0

7

fuel-core v0.34.0 has been released. follow the below steps to upgrade

8

hey Nazeeh, …we seem to have a new node error, several users experience this

ERROR new{name=fuel-sepolia-testnet-node}:initialize_loop{service=“P2P”}: fuel_core_p2p::peer_report: 165: Dial failure: peer id Some(PeerId("16Uiu2HAmNTu95nHqidgAS9LumPfJHmpnGJz9m1NGo5haLMXaz1zm")) with error `Failed to negotiate transport protocol(s): [(/ip4/127.0.0.1/tcp/30333/p2p/16Uiu2HAmNTu95nHqidgAS9LumPfJHmpnGJz9m1NGo5haLMXaz1zm

9

Usually, this error means using an incorrect snapshot that is not compatible with the testnet. Can you try using ignition-test folder for the snapshot?

10

hey thanks for the update, what puzzles me is that everything was fine until it reached a certain block, I’ll take a look at it.