The Node is Not in Sync v0.8.5

[starowner777]

Describe the bug
My node is not syncing to the blockchain.

Mandatory Information

1. jcli --full-version output;
   $ jcli --full-version

jcli 0.8.5 (master-3db06807, release, linux [x86_64]) - [rustc 1.40.0 (73528e339 2019-12-16
)]

2. jormungandr --full-version output;

$ jormungandr --full-version
jormungandr 0.8.5 (master-3db06807, release, linux [x86_64]) - [rustc 1.40.0 (73528e339 201
9-12-16)]

To Reproduce
Steps to reproduce the behavior:
jcli rest v0 node stats get -h "http://127.0.0.1:8443/api"

$ jcli rest v0 node stats get -h "http://127.0.0.1:8443/api"
---
blockRecvCnt: 0
lastBlockContentSize: 0
lastBlockDate: "2.833"
lastBlockFees: 0
lastBlockHash: d45d84e54c1d83ae36b2e081d237ece91ec632d0af64842dd43f07716f50e571
lastBlockHeight: "996"
lastBlockSum: 0
lastBlockTime: "2019-12-24T19:17:56+00:00"
lastBlockTx: 0
lastReceivedBlockTime: ~
state: Running
txRecvCnt: 0
uptime: 101548
version: jormungandr 0.8.5-3db06807

node config.yaml

$ cat config.yaml
storage: "/home/ec2-user/jor-test/self_node/jormungandr-storage-test/"

rest:
  listen: "127.0.0.1:8443"

p2p:
  trusted_peers: [
      {
        "address": "/ip4/52.9.132.248/tcp/3000",
        "id": "671a9e7a5c739532668511bea823f0f5c5557c99b813456c"
      },
      {
        "address": "/ip4/52.8.15.52/tcp/3000",
        "id": "18bf81a75e5b15a49b843a66f61602e14d4261fb5595b5f5"
      },
      {
        "address": "/ip4/13.114.196.228/tcp/3000",
        "id": "7e1020c2e2107a849a8353876d047085f475c9bc646e42e9"
      },
      {
        "address": "/ip4/13.112.181.42/tcp/3000",
        "id": "52762c49a84699d43c96fdfe6de18079fb2512077d6aa5bc"
      },
      {
        "address": "/ip4/3.125.75.156/tcp/3000",
        "id": "22fb117f9f72f38b21bca5c0f069766c0d4327925d967791"
      },
      {
        "address": "/ip4/52.28.91.178/tcp/3000",
        "id": "23b3ca09c644fe8098f64c24d75d9f79c8e058642e63a28c"
      },
      {
        "address": "/ip4/3.124.116.145/tcp/3000",
        "id": "99cb10f53185fbef110472d45a36082905ee12df8a049b74"
      }
    ]
  public_address: "/ip4/×.×.×.×/tcp/8299"
  listen_address: "/ip4/0.0.0.0/tcp/8299"
  topics_of_interest:
    messages: high
    blocks: high

Additional context
Output config.yaml with bootstrap

where changed
trusted_peers:　
add from itn_rewards_v1
https://hydra.iohk.io/build/1523436/download/1/index.html

messages: →high
blocks: low→high

add
public_address →my serever public address
listen_address →0.0.0.0

tail -f my_node.log

$ tail -f my_node.log
Dec 24 19:56:55.472 INFO Starting jormungandr 0.8.5 (master-3db06807, release, linux [x86_6
4]) - [rustc 1.40.0 (73528e339 2019-12-16)], task: init
Error in the overall configuration of the node
 |-> The Rest configuration is invalid: Failed to bind the port
 |-> Failed to bind the port
 |-> Address already in use (os error 98)
Dec 24 19:57:16.001 INFO Leader event started, event_remaining_time: 9s 998ms 982us 623ns, 
event_end: 2019-12-24T19:57:26+00:00, event_start: 2019-12-24T19:57:16+00:00, event_date: 2
.1069, leader_id: 1, task: leadership
Dec 24 19:57:16.001 INFO receiving block from leadership service, date: 2.1069, parent: 097
731778430d72426303b70fb14428996bd8dd2d37affdd2db2790eb6180b2b, hash: 71af24ff5536f7509b6d68
5af810935b58df5419055b365d51942588799751ad, task: block
Dec 24 19:57:16.004 INFO block from leader event successfully stored, date: 2.1069, parent:
 097731778430d72426303b70fb14428996bd8dd2d37affdd2db2790eb6180b2b, hash: 71af24ff5536f7509b
6d685af810935b58df5419055b365d51942588799751ad, task: block
Dec 24 19:57:16.004 INFO update current branch tip, date: 2.1069, parent: 097731778430d7242
6303b70fb14428996bd8dd2d37affdd2db2790eb6180b2b, hash: 71af24ff5536f7509b6d685af810935b58df
5419055b365d51942588799751ad, task: block

[mark-stopka]

You already have some other process bind to that socket, considering you're getting Jormungandr API on the jcli queries, I would assume it's another Jormungandr instance in the background.

Error in the overall configuration of the node
 |-> The Rest configuration is invalid: Failed to bind the port
 |-> Failed to bind the port
 |-> Address already in use (os error 98)

Besides, your config is not a valid YAML nor JSON file.

[starowner777]

@mark-stopka thank you for replay

it's another Jormungandr instance in the background.
Besides, your config is not a valid YAML nor JSON file.

I see,How should I change my config or some files to synchronize nodes?