Search the Community

I have a simple setup. I have two folders on an x86_64 machine that sync to an ARM machine. This has worked fine for about a week. Today I upped the ante. I added a new 40GB folder to sync between machines. I added the folder on the source machine, the x86_64. After it indexed, I added it as ro on the ARM machine and the sync began. I stepped away and returned an hour later to find BTSync had died on the ARM machine. I don't see any clear errors in the sync.log file on the ARM machine. I ran btsync from terminal on the ARM machine to try and get more info. [root@arm .sync]# btsync --nodaemon --config /etc/btsync/btsync.config total physical memory -1 max disk cache 2097152 Using IP address 192.168.1.5 Loading config file version 1.2.73 UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Could not map UPnP Port on this pass, retrying. UPnP: Unable to map port 192.168.1.5:63806 with UPnP. Loaded folder /backup/BTSync/folder1 Loaded folder /backup/BTSync/Drop Killed I didn't send the kill signal. I don't know why "Killed" shows up, but when it does, it corresponds to the btsync process dying. There's about a minute between seeing "Loaded folder /backup/BTSync/Drop" and when btsync chokes and the "Killed" message appears. The 40GB folder never shows up in the stdout. It seems logical that btsync dies while "Loading" that folder. Watching top, mem usage never exceeds 18%. CPU usage is high, but never holds at 100. Hovering between 80 and upper 90s. BitTorrent Sync 1.2.73 on the ARM machine Based on the churning I hear from the USB hard drive on the ARM machine, it sounds like it's dying while indexing this new 40GB folder. Worst of all is that since the sync folders don't load in the WebUI prior to the crash, I can't go into the WebUI on the ARM machine and remove this folder that seems to be causing the issue.