Upgrading sync in a network with other versions

[RazorBladet]

Hi!

Just want your advice which way forward is the best.

I have a network of some Raspberry Pi 2 running older versions of sync: BitTorrent Sync 2.3.3 (296)

Yesterday I tried to upgrade 1 of these Pis with the latest armhf-version: Resilio Sync 2.5.12 (1191)

The upgrade went well and initially no problems. Server was runing fine, web-gui working fine.

The problems:

1. I started so see these in the logs on the Pi with the latest version:

[20180223 23:48:50.549] SF[XXXX] [XXXX]: Ignoring "peers" message
[20180223 23:48:50.662] SF[XXXX] [XXXX]: Ignoring "peers" message
[20180223 23:48:58.540] SF[XXXX] [XXXX]: Ignoring "peers" message
[20180223 23:48:59.688] SF[XXXX] [XXXX]: Ignoring "peers" message

2. My old laptop running Linux BitTorrent Sync 2.3.3 (296) started to act strange:

btsync process went 100% and memory usage went to the roof. The laptop was unresponsive.

The only strange thing in the log on my laptop was:

[20180223 21:58:53.395] assert failed /home/jenkins/slave-root/jenkins-Build-Sync-Manually-1668/KickSocket.cpp:222
[20180223 21:58:53.396] assert failed /home/jenkins/slave-root/jenkins-Build-Sync-Manually-1668/KickSocket.cpp:222
[20180223 21:58:53.396] assert failed /home/jenkins/slave-root/jenkins-Build-Sync-Manually-1668/KickSocket.cpp:222
[20180223 21:58:53.396] assert failed /home/jenkins/slave-root/jenkins-Build-Sync-Manually-1668/KickSocket.cpp:222

Solution for now:

Downgraded sync on Raspberry Pi 2 to the previous version so I could work with my old Linux laptop.

Question:

Should I upgrade my desktop-systems before I upgrade the Raspberry Pi servers? Which way forward in a mixed environment is the best?

Thanks for a great product!

Cheers!

[Helen]

Since this is all p2p, better upgrade all peers to same version. Cannot guarantee that 2.3 and 2.5 will work - way too distanced Sync versions. 

[RazorBladet]

Ok, I'll see thats the way forward, to reinstall sync on my network. Anyway, thanks for the swift answer.