Mainnet RPC Node errors

Fuel Network
1

Hello everyone, I have been trying to setup a Mainnet node but have issues with syncing. This is a new node and I have followed the docs by pointing to the ignition folder, $ fuelup show
Default host: x86_64-unknown-linux-gnu
fuelup home: /home/fuel-ger-01/.fuelup

Installed toolchains

latest-x86_64-unknown-linux-gnu (default)

active toolchain

latest-x86_64-unknown-linux-gnu (default)
forc : 0.66.2
- forc-client
- forc-deploy : 0.66.2
- forc-run : 0.66.2
- forc-crypto : 0.66.2
- forc-debug : 0.66.2
- forc-doc : 0.66.2
- forc-fmt : 0.66.2
- forc-lsp : 0.66.2
- forc-tx : 0.66.2
- forc-wallet : 0.11.0
fuel-core : 0.40.0
fuel-core-keygen : 0.40.0

fuels versions

forc : 0.66.9
forc-wallet : 0.66.9 The error I am getting is 2024-10-25T12:00:16.018177Z INFO new{name=fuel-mainnet-node}:initialize_loop{service=“Relayer”}: fuel_core_relayer::service::get_logs: 51: Downloading logs for block range: 20997235…=20997334
thread ‘tokio-runtime-worker’ panicked at /project/crates/services/src/service.rs:322:10:
The initialization of the service failed.: no record found for Query { name: Name(“_dnsaddr.mainnet.fuel.network.liquify.lan.”), query_type: TXT, query_class: IN, mdns_unicast_response: false }
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace This is shortly after trying to start fuel-core, I am using the same command as per docs with a p2p key and pointing to my own eth mainnet node. Thanks

2

Hi @bilal-liquify ,

It’s likely the case you are using the wrong dns settings.

You are likely using the incorrect dns address to connect. Your dnsaddr from the logs is empty.

It’s possible you are not using --bootstrap-nodes /dnsaddr/mainnet.fuel.network . Or something with your OS, and it unable to resolve the DNS (or it could be a VPN that is on and it alters DNS resolution).

1 Like
3

fuel-core run --enable-relayer --service-name fuel-mainnet-node --keypair xxxxxx --relayer http://our-eth-node --ip=0.0.0.0 --port 4000 --peering-port 30333 --db-path ~/.fuel-mainnet --snapshot /home/fuel-ger-01/chain-configuration/ignition --utxo-validation --poa-instant false --enable-p2p --bootstrap-nodes /dnsaddr/mainnet.fuel.network --sync-header-batch-size 100 --relayer-v2-listening-contracts=0xAEB0c00D0125A8a788956ade4f4F12Ead9f65DDf --relayer-da-deploy-height=20620434 --relayer-log-page-size=100 --sync-block-stream-buffer-size 30
So this is our run command, it does have the bootstrap nodes in there so I’m not certain why it causes an issue, The os is Ubuntu server 22 if that helps

4

Hi @bilal-liquify - it looks like there is an issue with DNS resolution on your server.

In the logs you posted, you’re using the correct bootstrap host (“mainnet.fuel.network”), however that is getting changed to a different host by your machine (seems to be using “mainnet.fuel.network.liquify.lan” instead).

This can happen for a number of reasons, but it’s likely related to a VPN configuration, or DNS hostname being set on the machine. I would recommend checking your network config and seeing if there are settings you can modify there.

The rest of the options you specified look correct.