Hi there
I have the following error in logs:
Failed to import range of blocks. 324257…XXXXXXX
I can connect to the node with my wallet and I can see the node is sending requests to Alchemy but it is not syncing
Hi @niicta ,
Can you provide the results of fuelup show first, we will need to see your versions before we can properly help you.
Are you still experiencing the issue after a node restart?
Hi @nick
I’ve made a full reinstallation and now the issue is gone, but when I’m connecting to my node with fuel wallet it still shows zero balance
Default host: x86_64-unknown-linux-gnu
fuelup home: /root/.fuelup
installed toolchains
--------------------
latest-x86_64-unknown-linux-gnu (default)
active toolchain
----------------
latest-x86_64-unknown-linux-gnu (default)
forc : 0.60.0
- forc-client
- forc-deploy : 0.60.0
- forc-run : 0.60.0
- forc-crypto : 0.60.0
- forc-debug : 0.60.0
- forc-doc : 0.60.0
- forc-explore : 0.28.1
- forc-fmt : 0.60.0
- forc-lsp : 0.60.0
- forc-tx : 0.60.0
- forc-wallet : 0.7.1
fuel-core : 0.26.0
fuel-core-keygen : 0.26.0
fuels versions
--------------
forc : 0.62.0
forc-wallet : 0.62.0
most latest logs look like this
2024-06-18T00:27:15.662519Z INFO new{name=fuel-sepolia-testnet-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 38: Downloading logs for block range: 6130089..=6130120
2024-06-18T00:33:40.765348Z INFO new{name=fuel-sepolia-testnet-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 38: Downloading logs for block range: 6130121..=6130151
2024-06-18T00:40:05.866822Z INFO new{name=fuel-sepolia-testnet-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 38: Downloading logs for block range: 6130152..=6130182
2024-06-18T00:46:30.933633Z INFO new{name=fuel-sepolia-testnet-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 38: Downloading logs for block range: 6130183..=6130211
2024-06-18T00:53:06.107071Z INFO new{name=fuel-sepolia-testnet-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 38: Downloading logs for block range: 6130212..=6130242
While installing, I was following this guide Running a Testnet Node | Fuel Docs
The node still downloads logs really slow and I believe this is not the way it’s gonna happen. Is there a solution for that?
You faced Handle incorrect shutdown of the off-chain GraphQL worker · Issue #1584 · FuelLabs/fuel-core · GitHub, and it caused the desynchronization of the OffChain and OnChain databases. You have only one solution if you need off-chain data - start synchronization from scratch, sorry=(
It will be fixed in the next two weeks, but for now, you have only one solution.
You are stuck at magic height 324257 =D It is the height where we got the first deposit event from L1.
We are using Infura by default, and it seems that Infura and Alchemy return different results. We are investigating the reason why. Meanwhile, I would suggest to you restart the node with the next modifications:
- Upgrade to
fuel-core 0.30.0. - Prune relayer database like
rm -Rf {/path/to/db/folder}/relayer. - Try to use alchemy
v3(if you are usingv2).
If the above doesn’t help you pass the magic height, then I would suggest you to prune relayer DB again and use Infura for now=(
thanks, but as I mentioned node already passed 324257 and now downloads logs for 6139724 at the moment
and each download takes about 5-10 minutes
The 6139724 is the height of L1. The 324257 is the height of Fuel—L2. L2 synchronization doesn’t work. You see only synchronized blocks from L1 right now, and they have the speed of L1 finalization.
thank you!
May you also say what is the right format for --keypair option? I’m using only “secret” part of my key here, is it right?
i’m asking because when I use full generated json i receive error: unexpected argument ‘secret:*****’ found
I’m using --keypair b53a1789b26a13cfbeb984be3b9f2fdf1b274aa200b5498dc2ce8a6f8c21a143. But you also can use it path to the file like --keypair /path/to/file. Also it is possible to use KEYPAIR env variable.
1 Like
I’ve made a full reinstallation again (changed to https://sepolia.infura.io/v3/api_key) and here what I see in the logs now
- too many files - I solved it by rebooting the machine, but not sure files should remain open by the node
- what is the height 2949961 now ?
fuelup home: /root/.fuelup
installed toolchains
latest-x86_64-unknown-linux-gnu (default)
active toolchain
latest-x86_64-unknown-linux-gnu (default)
forc : 0.60.0
- forc-client
- forc-deploy : 0.60.0
- forc-run : 0.60.0
- forc-crypto : 0.60.0
- forc-debug : 0.60.0
- forc-doc : 0.60.0
- forc-explore : 0.28.1
- forc-fmt : 0.60.0
- forc-lsp : 0.60.0
- forc-tx : 0.60.0
- forc-wallet : 0.7.1
fuel-core : 0.26.0
fuel-core-keygen : 0.26.0
fuels versions
forc : 0.62.0
forc-wallet : 0.62.0
So V3 fixed the main issue. The 2949961 is the height of the L2=) You already synced 2M blocks.
Regarding “Many opened files”: ulimit - Too many open files - Ask Ubuntu
For performance reasons, Rocksdb opens a lot of files. You need to increase your limit(for now). But from our side maybe we will not open many fields in the future if user’s limit is low to avoid this error=)
0.26如何升级到0.30？为什么官方提供的脚本不会拉最新代码，我用的0.26版本高度同步正常，但是查不到余额，需要怎么处理呢
haha, now it stuck on the similar l1 range, doesn’t it?
and it still shows zero balances on my wallet so it is not synched again
Could you attach the full log file, please?=)
Meanwhile, if your --relayer-log-page-size is more than 200, I would suggest to decrease it to 200=)
Stop working after few hours - #9 by xgreenx contains information how to upgrade the fuel-core.
As I mentioned in the previous comments, the off chain database(which is used to get users balances) is out of sync because of Handle incorrect shutdown of the off-chain GraphQL worker · Issue #1584 · FuelLabs/fuel-core · GitHub. You need to reset the database and sync again from scratch=( Unit issue is fixed
我清除了所有数据，只保留了密钥串，之后重新部署还是一样的问题