# Full Node settings

## Full Node settings

the operation to modify the setting information for the operating environment is required in order for Full Node to operate mutually.\
Please refer to below steps to proceed the settings 

### Setting PATH

Enter the container Shell to set the PATH.

```bash
root@4e60bc34a625:/omnione-testnet# source /etc/profile
```

### Checking the script file

Use 'ls' command to check the Full Node script file.

```bash
root@4e60bc34a625:/omnione-testnet# ls
drwxr-xr-x 1 root root 4096 Feb 10 01:48 bp_node
-rwx------ 1 root root  259 Feb 10 02:35 gen_bp_start.sh
-rwx------ 1 root root   72 Feb 10 01:48 keosd_start.sh
-rwx------ 1 root root  270 Feb  7 00:57 stop.sh
```

### Changing the name of the folder and script file

```bash
root@4e60bc34a625:/omnione-testnet# mv bp_node full_node
root@4e60bc34a625:/omnione-testnet# mv gen_bp_start.sh gen_full_start.sh
```

### Starting the FullNode

the operation to run FullNode by the script.

```bash
root@4e60bc34a625:/omnione-testnet#./gen_full_start.sh
```

### Checking the execution log

```bash
root@4e60bc34a625:/omnione-testnet# tail -f full_node/node_data/nodeos.log
```

If you have followed up to this part, FullNode should be executed normally.\
To terminate safely please press **`Ctrl + p or q`**.

## Checking the interworking operation with the real chain

This is a task to check whether it has been successfully connected on a chain within the real Docker 

```bash
curl http://localhost:18888/v1/chain/get_info
```

#### Outputs for executing the command line are as shown below.

> {"server\_version":"05be92e5",`"chain_id":"dfc4f3b5242822ee1d8add97be1246af57b793d470f1106d2758304d21868297"`,"head\_block\_num":4148172,"last\_irreversible\_block\_num":4148133,"last\_irreversible\_block\_id":"003f4ba57db4ed4229de775f3b3df293b7e046afa3d2feea6c138a36198f01be","head\_block\_id":"003f4bcc28d18f7ed74be581ab4613ab0d0891f473ebb6be33b55532b369097e","head\_block\_time":"2020-02-10T06:34:25.000","head\_block\_producer":"h1rqhln1rzb5","virtual\_block\_cpu\_limit":100000000,"virtual\_block\_net\_limit":1048576000,"block\_cpu\_limit":99900,"block\_net\_limit":1048576,"server\_version\_string":"v1.8.6-16-g05be92e57-dirty","fork\_db\_head\_block\_num":4148172,"fork\_db\_head\_block\_id":"003f4bcc28d18f7ed74be581ab4613ab0d0891f473ebb6be33b55532b369097e"}

## Checking the block data on a local environment

Check if the block data that is stored in the local directory is created properly.

```bash
cd ~/Raonsecure/docker/testnet/omnnode-data
ls
blocks eosd.pid nodeos.log snapshots  state
tail -f nodeos.log
```

Executing the last command line will be able to check block created data. For termination command is  **`ctrl + c`**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev-en.omnione.net/node-creation/untitled/full-node-by-using-docker/full-node-setting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.