Error: No such file or directory (os error 2)

General
1

I encounter this error when trying to run the node. chainConfig.json is in the directory Im trying to start from.

fuel-core run
–service-name {MY_SERVICE_NAME}
–keypair {MY_P2P_SECRET}
–relayer {MY_ETH_RPC_ENDPOINT}
–ip 0.0.0.0 --port 4000 --peering-port 30333
–db-path ~/.fuel_beta5
–chain ./chainConfig.json
–utxo-validation --poa-instant false --enable-p2p
–min-gas-price 1 --max-block-size 18874368 --max-transmit-size 18874368
–reserved-nodes /dns4/p2p-beta-5.fuel.network/tcp/30333/p2p/16Uiu2HAmSMqLSibvGCvg8EFLrpnmrXw1GZ2ADX3U2c9ttQSvFtZX,/dns4/p2p-beta-5.fuel.network/tcp/30334/p2p/16Uiu2HAmVUHZ3Yimoh4fBbFqAb3AC4QR1cyo8bUF4qyi8eiUjpVP
–sync-header-batch-size 100
–enable-relayer
–relayer-v2-listening-contracts 0x557c5cE22F877d975C2cB13D0a961a182d740fD5
–relayer-da-deploy-height 4867877
–relayer-log-page-size 2000

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.49.3
- forc-client
- forc-deploy : 0.49.3
- forc-run : 0.49.3
- forc-crypto : 0.49.3
- forc-doc : 0.49.3
- forc-explore : 0.28.1
- forc-fmt : 0.49.3
- forc-lsp : 0.49.3
- forc-tx : 0.49.3
- forc-wallet : 0.4.3
fuel-core : 0.22.1
fuel-core-keygen : 0.22.1

fuels versions

forc : 0.54.0
forc-wallet : 0.54.0

Topic discussion checklist

  • Run $ fuelup show and add the output below
  • Detailed steps to recreate issue
  • Link full scope of the codebase pertaining to your issue
  • Any other relevant information
2

Hey there @lmc! I don’t see the error you posted. :thinking:

Could you reply with what you see in the console please?

1 Like
3

Hi,

it’s this: Error: No such file or directory (os error 2)

1 Like
4

Hi @lmc
can you share the results of which fuel-core

1 Like
5

Hi,
this is what I get:

15eda997db7861c9447f5c3eff26333b20180475d94443a10c6), Address(0xc36be0e14d3eaf5d8d233e0f4a40b3b4e48427d25f84c460d2b03b242a38479e [bech32: fuel1cd47pc2d86h4mrfr8c855s9nknjggf7jt7zvgcxjkqajg23cg70qnxg0hd]), Balance(10000000)
2024-03-17T11:25:34.936954Z INFO fuel_core::cli::run::relayer: 63: Relayer service disabled
2024-03-17T11:25:34.936993Z INFO fuel_core::cli::run::p2p: 237: P2P service disabled
2024-03-17T11:25:34.937029Z INFO fuel_core::cli::run: 264: Block production mode: Instant
2024-03-17T11:25:34.937095Z WARN fuel_core::cli::run: 273: Fuel Core is using an insecure test key for consensus. Public key: 73dc6cc8cc0041e4924954b35a71a22ccb520664c522198a6d31dc6c945347bb854a39382d296ec64c70d7cea1db75601595e29729f3fbdc7ee9dae66705beb4
2024-03-17T11:25:34.937168Z WARN fuel_core::cli::run: 294: The coinbase recipient ContractId is not set!
2024-03-17T11:25:34.937208Z INFO fuel_core::cli::run: 358: Fuel Core version v0.22.1
2024-03-17T11:25:34.937260Z INFO fuel_core::service: 95: Opening database “/root/.fuel/db” with cache size “1073741824”
2024-03-17T11:25:35.438202Z WARN new{name=fuel-core}: fuel_core::service::config: 122: The utxo_validation should be true with disabled debug
2024-03-17T11:25:35.438272Z WARN new{name=fuel-core}: fuel_core::service::config: 133: The utxo_validation of TxPool was inconsistent
2024-03-17T11:25:35.438295Z WARN new{name=fuel-core}: fuel_core::service::config: 137: The utxo_validation of BlockProducer was inconsistent
2024-03-17T11:25:35.438309Z INFO new{name=fuel-core}: fuel_core::service: 189: Initializing database
2024-03-17T11:25:35.448773Z INFO new{name=fuel-core}:_commit_result{block_id=b1807ca9f2eec7e459b866ecf69b68679fc6b205a9a85c16bd4943d1bfc6fb2a height=0 tx_status=}: fuel_core_importer::importer: 264: Committed block 0xb1807ca9f2eec7e459b866ecf69b68679fc6b205a9a85c16bd4943d1bfc6fb2a
2024-03-17T11:25:35.448872Z INFO new{name=fuel-core}: fuel_core::service: 194: Initializing sub services
2024-03-17T11:25:35.467508Z INFO new{name=fuel-core}: fuel_core::graphql_api::service: 216: Binding GraphQL provider to 127.0.0.1:4000
2024-03-17T11:25:35.467911Z INFO new{name=fuel-core}:initialize_loop{service=“SyncTask”}: fuel_core_services::service: 298: The service SyncTask is shut down
2024-03-17T11:25:35.468008Z INFO new{name=fuel-core}:initialize_loop{service=“ImportTask”}: fuel_core_services::service: 298: The service ImportTask is shut down
2024-03-17T11:25:35.467995Z INFO new{name=fuel-core}:initialize_loop{service=“FuelService”}: fuel_core_services::service: 330: Starting FuelService service
2024-03-17T11:25:35.468082Z INFO new{name=fuel-core}:initialize_loop{service=“GraphQL”}: fuel_core_services::service: 330: Starting GraphQL service
2024-03-17T11:25:35.471064Z INFO new{name=fuel-core}:initialize_loop{service=“TxPool”}: fuel_core_services::service: 330: Starting TxPool service
2024-03-17T11:25:35.471279Z INFO new{name=fuel-core}:initialize_loop{service=“PoA”}: fuel_core_services::service: 330: Starting PoA service
2024-03-17T11:25:35.471339Z INFO new{name=fuel-core}:initialize_loop{service=“PoASyncTask”}: fuel_core_services::service: 330: Starting PoASyncTask service

6

are you not getting this error anymore ? it’s not clear what you need assistance with

7

yes, the initial error still persists.

8

can you send a screen shot of the error ?

9

Hi,
here is a screenshot

image
image834×250 23.1 KB

Thanks for bearing with me!

1 Like
10

Hi,
is there any hint for this?

11

Did you configure a chainConfig file?

12

Hello, I am having the same error and yes I configured a chainConfig file

13

Yes, configured the file under the right name as well.