Installation issues

Topic discussion checklist

  • Run $ fuelup show and add the output below
    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.1
- forc-client
- forc-deploy : 0.49.1
- forc-run : 0.49.1
- forc-crypto : 0.49.1
- forc-doc : 0.49.1
- forc-explore : 0.28.1
- forc-fmt : 0.49.1
- forc-lsp : 0.49.1
- forc-tx : 0.49.1
- forc-wallet : 0.4.2
fuel-core : 0.22.0
fuel-core-keygen : 0.22.0

fuels versions

forc : 0.54.0
forc-wallet : 0.54.0

  • Detailed steps to recreate the issue

I am trying to run this part

*fuel-core run *
*–service-name {ANY_SERVICE_NAME} *
*–keypair {P2P_SECRET} *
*–relayer {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 ]

but am getting this feedback

2024-02-16T00:36:56.162679Z WARN fuel_core::cli::run: 273: Fuel Core is using an insecure test key for consensus. Public key: 73dc6cc8cc0041e4924954b35a71a22ccb520664c522198a6d31dc6c945347bb854a39382d296ec64c70d7cea1db75601595e29729f3fbdc7ee9dae66705beb4
2024-02-16T00:36:56.162686Z WARN fuel_core::cli::run: 294: The coinbase recipient ContractId is not set!
2024-02-16T00:36:56.162693Z INFO fuel_core::cli::run: 358: Fuel Core version v0.22.0
2024-02-16T00:36:56.162700Z INFO fuel_core::service: 95: Opening database “/root/.fuel/db” with cache size “1073741824”
2024-02-16T00:36:56.226284Z WARN new{name=fuel-core}: fuel_core::service::config: 122: The utxo_validation should be true with disabled debug
2024-02-16T00:36:56.226403Z WARN new{name=fuel-core}: fuel_core::service::config: 133: The utxo_validation of TxPool was inconsistent
2024-02-16T00:36:56.226417Z WARN new{name=fuel-core}: fuel_core::service::config: 137: The utxo_validation of BlockProducer was inconsistent
2024-02-16T00:36:56.226429Z INFO new{name=fuel-core}: fuel_core::service: 189: Initializing database
2024-02-16T00:36:56.228132Z INFO new{name=fuel-core}: fuel_core::service: 194: Initializing sub services
2024-02-16T00:36:56.238581Z INFO new{name=fuel-core}: fuel_core::graphql_api::service: 216: Binding GraphQL provider to 127.0.0.1:4000
2024-02-16T00:36:56.239449Z INFO new{name=fuel-core}:initialize_loop{service=“SyncTask”}: fuel_core_services::service: 298: The service SyncTask is shut down
2024-02-16T00:36:56.239526Z INFO new{name=fuel-core}:initialize_loop{service=“ImportTask”}: fuel_core_services::service: 298: The service ImportTask is shut down
2024-02-16T00:36:56.239621Z INFO new{name=fuel-core}:initialize_loop{service=“FuelService”}: fuel_core_services::service: 330: Starting FuelService service
2024-02-16T00:36:56.239658Z INFO new{name=fuel-core}:initialize_loop{service=“GraphQL”}: fuel_core_services::service: 330: Starting GraphQL service
2024-02-16T00:36:56.240385Z INFO new{name=fuel-core}:initialize_loop{service=“TxPool”}: fuel_core_services::service: 330: Starting TxPool service
2024-02-16T00:36:56.240489Z INFO new{name=fuel-core}:initialize_loop{service=“PoA”}: fuel_core_services::service: 330: Starting PoA service
2024-02-16T00:36:56.240543Z INFO new{name=fuel-core}:initialize_loop{service=“PoASyncTask”}: fuel_core_services::service: 330: Starting PoASyncTask service

  • Link full scope of the codebase pertaining to your issue

yes, whe inputing the [ Running a Local Node] i input my service name, secret keypair and api key

  • Any other relevant information
    nun

hey @olatonrain, just reaching out to find out if you came right with your node?
otherwise updating your packages and using the beta-5 toolchain will most likely fix it.