Investigate syncing

[JakubFornadel]

Bug Report

0x00007fbdf0ff9640 b3888b0b… GET_PBFT_SYNC_PH [2023-02-13 10:03:21.783688] ERROR: Exception caught during packet processing: PacketProcessingException -> MaliciousPeer: Peer c89a1587e38653e01147adc896276118e4e5dcc682e15db3920f408a649a74df622e8bd07dde4fef57b9109aabdc0c44651fe67bc1167061fb4638f378cacbf5 request syncing period start at 91014. That's bigger than own PBFT chain size 73796 .PacketData: {"from_node_id":"c89a1587e38653e01147adc896276118e4e5dcc682e15db3920f408a649a74df622e8bd07dde4fef57b9109aabdc0c44651fe67bc1167061fb4638f378cacbf5","id":358,"priority":2,"receive_time":"2023-02-13 10:03:21 node local time","rlp_items_count":1,"rlp_size":0,"type":"GetPbftSyncPacket"}

It is weird that a node at 91014 would ask a node that is on 73796 to sync, so this logic does not seem to work correctly

Description

Info about the bug goes here.

Steps to Reproduce

1. Step 1
2. Step 2

Expected Result

The expected result was...

You may write the expected result or add a screenshot.

Actual Results

The actual result was...

Would be awesome to link screenshots here and/or error messages received.

Environment

Node version

Use docker command to find node image version:

docker images --format '{{.ID}}' 'taraxa/taraxa-node:latest'

Operating System details.

CPU, memory, disk details.

NOTE: In many cases log files are also useful to include. Since these files may be large, a Taraxa developer may request them later. These files may include public addresses that you're participating with. If that is a concern please be sure to scrub that data.