RazorBladet

I had the same issue while testing to upgrade to version 2.5.12 in a network with older versions of btsync running on other systems. I am thinking about upgrading the versions running on my network, but as it is working just fine, I'll do it another day.... My post on a similar issue

I had similar problem med different versions of sync on my network. I upgraded one of my Raspberry Pi:s to the latest sync version for testing. My laptop with an older version of sync freezed the computer (Linux). Sync process and memory usage went to 100%. The other Raspberry Pi:s with the same old sync version as the laptop didn't have the same issues. Strange.

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

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!

Thanks for the reply! I understand that the servers are trying to connect to the "discovered" peer, and that's how it all works and should. Cheers

Are you running btsync as user btsync or as root? Maybe you have mounted this network share with no write permission.

Hi! iPad using BitTorrent Sync version 2.3.5 (254) client, my home network has 2 Raspberry Pi running BitTorrent Sync v2.3.3 (296). I was visiting our summer cabin this last weekend and used iPhone to create a hotspot for our iPad for connection via 3g. So after starting up the BitTorrent Sync app on the iPad, the servers on my home network tried to connect to 172.20.10.x, the same IP-address iPhone gave to the iPad. By looking in the Sync logs you see peer information for an external ip and a local ip (172.20.10.x). Then the server tries to ping 172.20.10.x, of course with no result (timed out). Questions: 1) is this a bug in the client app for iPad/iPhone? 2) Are my BitTorrent servers not really understanding the protocol from the iPad client app? 3) Is this an aggressive peer discovery protocol running amok? Anyhow, thanks for a great product! Regards