Confirmation of Node Deployment

[DJX]

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)
nightly-x86_64-unknown-linux-gnu

active toolchain

latest-x86_64-unknown-linux-gnu (default)
forc : 0.49.2
- forc-client
- forc-deploy : 0.49.2
- forc-run : 0.49.2
- forc-crypto : 0.49.2
- forc-doc : 0.49.2
- forc-explore : 0.28.1
- forc-fmt : 0.49.2
- forc-lsp : 0.49.2
- forc-tx : 0.49.2
- forc-wallet : 0.4.3
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 issue
  After running my deploy command (“fuel-core run
  –service-name xoe .…”

It returns:
“2024-02-20T22:29:46.234229Z INFO fuel_core::cli::run: 266: Block production disabled
2024-02-20T22:29:46.234259Z WARN fuel_core::cli::run: 294: The coinbase recipient ContractId is not set!
2024-02-20T22:29:46.234264Z INFO fuel_core::cli::run: 358: Fuel Core version v0.22.0
2024-02-20T22:29:46.234267Z INFO fuel_core::service: 95: Opening database “/root/.fuel_beta5” with cache size “1073741824”
2024-02-20T22:29:46.266132Z INFO new{name=xoe}: fuel_core::service: 189: Initializing database
2024-02-20T22:29:46.266309Z INFO new{name=xoe}: fuel_core::service: 194: Initializing sub
…”

My question is really how do I know I’ve done the deployment correctly?

• Link full scope of the codebase pertaining to your issue
• Any other relevant information

[DJX]

Additionally do I need to have a coinbase address?

in reference to :" 2024-02-20T22:29:46.234259Z WARN fuel_core::cli::run: 294: The coinbase recipient ContractId is not set!"

[calldelegation]

Hey @DJX, currently, you don’t need a Coinbase address to run a node.

You should look for logs indicating that blocks are being downloaded, similar to the examples below . Hope this helps!

2024-02-22T15:44:16.655405Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5317682..=5319681
2024-02-22T15:44:16.707292Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5319682..=5321681
2024-02-22T15:44:16.757542Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5321682..=5323681
2024-02-22T15:44:16.891060Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5323682..=5325681
2024-02-22T15:44:17.012083Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5325682..=5327681
2024-02-22T15:44:17.062039Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5327682..=5329681
2024-02-22T15:44:17.114975Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5329682..=5331681
2024-02-22T15:44:17.166670Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5331682..=5333681
2024-02-22T15:44:17.228418Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5333682..=5335681
2024-02-22T15:44:17.293389Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5335682..=5337681
2024-02-22T15:44:17.375383Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5337682..=5339681
2024-02-22T15:44:17.465812Z  INFO new{name=beta-5-node}:initialize_loop{service="Relayer"}: fuel_core_relayer::service::get_logs: 33: Downloading logs for block range: 5339682..=5341651

[DJX]

Thanks glad to hear this! So the node is running successfully!
With this confirmation I have two questions remaining…

If I am using a vps to host the node, upon exit is the node still running?
Also will the node continue if other programs are running during the session.

Thanks for the input thus far!

-X

[calldelegation]

1. If your VPS continues to run after you exit, then yes, it will still be running.
2. Yes, provided it does not interfere with the resources that support your node.

[ktrip96]

So currently, the terminal is “occupied” when you are running a node, right?

In order to do other tasks, you have to open a new terminal window.

It would be really nice, if that didn’t happen and if these logs were running on the background.

Let me ask you something though.
I am running the fuel run command on a VPS server.
Everything seems to work properly.
When I run “top” on my terminal, I can clearly see the Fuel process.

BUT, when I restart my PC let’s say and I rerun the “top” command, I don’t see any Fuel process.

It is worth mentioning that when I restart my local PC, the VPS does not restart. The VPS is always up and running

#FuelRocks

[DJX]

Hey man take a look at “Screen”, this is how I implemented all of my fuel nodes.
It essentially creates new terminal windows that do not stop their process until told to do so. Will link the documentation below, you should be able to download it on any vps system running linux.

Screen tutorial:

screen command in Linux with Examples - GeeksforGeeks

If you need more than this feel free to reach out and will help you set it up on your system!

-X

[ktrip96]

@DJX

You are awesome dude! Thanks a lot.

Let me ask you one final question.

• You have started a screen session
• You have started the fuel node with the fuel-core run command.
• You detach from this particular screen session.

If you want to see the logs of the ‘fuel-core run’ command, how can you do it?

[DJX]

@ktrip96

Let me ask you one final question.

• You have started a screen session
• You have started the fuel node with the fuel-core run command.
• You detach from this particular screen session.

If you want to see the logs of the ‘fuel-core run’ command, how can you do it?

If you’ve started a screen session, launched the fuel node with the fuel-core run command within that session, and then detached from the screen session, you can still access the logs of the fuel-core run command. Here’s how you can do it:

1. Reattach to the Screen Session: First, reattach to the screen session where you initially started the fuel-core run command. You can do this by listing the available screen sessions and then attaching to the desired one. You might use a command like

screen -ls

This will list the available screen sessions along with their IDs. Then you can reattach to the desired session with:

screen -r [session_id]

2. View Logs: Once you’re inside the screen session, you can view the logs of the fuel-core run command. These logs are typically printed to the terminal. You can scroll through the terminal output to review the logs.
3. Scrollback: If you detached from the screen session without preserving scrollback, you may not see the full logs immediately upon reattaching. You can enable scrollback within the screen session by pressing Ctrl + A followed by [ to enter copy mode, then you can use arrow keys or page up/down to scroll through the logs. Press Esc to exit copy mode.

By reattaching to the screen session, you regain access to the terminal where fuel-core run was executed, allowing you to view the logs and interact with the command as if you never detached from the session.

[ktrip96]

Thanks DJX.
Everything is working as you described