Remote is forked soncronizaction error catapult

Technical Discussion
#1

I am trayin to connect a node peer and a node api, I am using catapult. When the api node is trying to sincronize, something wrog happens.

" ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 11:52:11.346972 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 11:52:11.347128 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 11:52:12.154640 0x00007f9badf13700: (net::PacketWriters.cpp@303) [5 log count] no packet io available for checkout
2018-07-31 11:52:12.398604 0x00007f9badf13700: (ionet::PacketSocket.cpp@448) connected to 127.0.0.1 [127.0.0.1:7900]
2018-07-31 11:52:12.400787 0x00007f9badf13700: (extensions::NetworkUtils.h@49) accept result to local node port 7900: Accepted
2018-07-31 11:52:12.441392 0x00007f9badf13700: (net::ServerConnector.cpp@92) VerifyServer failed with Failure_Challenge
2018-07-31 11:52:12.441538 0x00007f9badf13700: (extensions::PeersConnectionTasks.cpp@97) connection attempt to peernode @ 127.0.0.1 completed with Verify_Error
2018-07-31 11:52:12.441752 0x00007f9badf13700: (ionet::PacketSocket.cpp@51) eof reading from socket: End of file
2018-07-31 11:52:12.441815 0x00007f9badf13700: (net::ChainedSocketReader.cpp@66) reader (ED4951073F311BFA6CF091BB06E1DF46F58F28E4E403ABBD32023E38A7379A53 @ 127.0.0.1) read completed with error: Closed
2018-07-31 11:52:13.432021 0x00007f9badf13700: (net::PacketWriters.cpp@303) [21 log count] no packet io available for checkout
2018-07-31 11:52:14.391432 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 11:52:14.391634 0x00007f9badf13700: (chain::RemoteAp"

could somebady help me?

Thanks

#2

Sorry I made a mistake, this is the error:

(peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:41.682348 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:41.682475 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:44.726569 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:44.726691 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:47.771232 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:47.771332 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:50.823181 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:50.823296 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:53.871941 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:53.872040 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:00:56.963162 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:00:56.963400 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:01:00.007958 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked
2018-07-31 12:01:00.008847 0x00007f9badf13700: (chain::RemoteApiForwarder.h@65) completed ‘synchronizer task’ (peernode @ 10.16.101.52) with result Failure
2018-07-31 12:01:03.098410 0x00007f9badf13700: (chain::ChainSynchronizer.cpp@285) node interaction failed: Remote_Is_Forked

#3

Friend apparently the nemesis blocks are badly generated, check that you are doing well the nemesis generation proceedings!

#4

Can you share the full log?
How many nodes does the network have and for long is it already running?