HeinerDD

Sync with Raspberry Pi

Recommended Posts

I actually am having this very same problem.  I have an encrypted rPi setup, and was running btsync 2.2.x for months with no problem -- syncing to encrypted external 3TB hard drives.  After updating to 2.3.3, the btsync seems to crash every 30-90minutes. I can't seem to figure out why.  When i switch back to btsync 2.2.x, it seems to work fine...

Is anyone else having this issue?

Share this post


Link to post
Share on other sites

@VDub Have you seen the core dump? If you don't have any core dumps generated, could you please try to run

ulimit -c unlimited

and then start Sync in the same console? It should make a core dump then either in same folder where btsync binary stays, or in storage folder, or in location mentioned in your "/proc/sys/kernel/core_pattern" file.

Share this post


Link to post
Share on other sites

Hi to all,

I messed around a bit because of the missing core dump.

As I wrote I did some changes in the file /proc/sys/kernel/core_pattern (see above). But I can't find any core pattern.

All the things I did I have read here: https://sigquit.wordpress.com/2009/03/13/the-core-pattern/

The link was mentioned here: http://help.getsync.com/hc/en-us/articles/206214615-Collecting-crash-reports-mini-dumps-and-core-dumps

Now I tried to kill the btsync process with "kill -s SIGSEGV <PID>". If I did so, I found are core dump in my data directory /home/pi/.btsync/

But if the btsync process kills itself, there is no core dump. There is no difference if I set "ulimit -c unlimited" or not.

Share this post


Link to post
Share on other sites
10 hours ago, RomanZ said:

Everyone affected the issue - I suggest testing this build. Let me know if your RPI will stop crashing.

I'm testing now and will get back to you soon.

Thanks so much.

Share this post


Link to post
Share on other sites
15 hours ago, RomanZ said:

Everyone affected the issue - I suggest testing this build. Let me know if your RPI will stop crashing.

So I tried this build out, and it still crashes after about 90 mins.  Here's the last few lines of the log:

 

[20160303 16:56:09.689] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:09.689] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:09.699] LF[204D]: LicenseFolder::IsActive(consumer): return TRUE, personal license
[20160303 16:56:09.699] LF[204D]: LicenseFolder::IsActive(consumer): return TRUE, personal license
[20160303 16:56:15.918] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:15.918] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:21.849] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:21.850] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:27.406] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:27.406] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:33.480] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:33.481] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:39.341] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:39.341] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:45.861] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:45.861] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:51.669] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:51.716] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"
[20160303 16:56:58.295] SyncFolderNotify: SyncFolderNotify: "ID", event = "IN_CLOSE_WRITE"
[20160303 16:56:58.309] [OnNotifyFileChange] "/mnt/WD_1/Programs/Programs/.sync/ID"

I noticed the the license part of the log is close to the end of the last time it crashed.

Furthermore, I tried to do a core dump, but because the rPi itself is stable, it didn't dump any crashes when I tried to use the aforementioned command.

2.2.x still works just fine and doesn't seem to crash.

I'm at a loss.

Thoughts?

Share this post


Link to post
Share on other sites

@VDub That's weird. Just to make sure we are on the same page: before starting Sync you did the

ulimit -c unlimited

command and then start Sync from the same terminal? This command ensures that OS will save the dump no matter of its size.

Share this post


Link to post
Share on other sites

@RomanZ Yeah, I ran that command in the same window as starting Sync.  But I didn't see a dump created when the program crashed.  To clarify, my rPi isn't crashing.  It works quite well actually, and is stable.  It's just the Sync program that just "terminates".

As a side note, I wanted to be sure nothing changed in my rPi, so I ran Sync 2.2.5(131) to be sure my rPi wasn't having issues or my syncdata wasn't causing the program crash.  Version 2.2.5 ran all night and is still running perfect as always.  So I'm not sure what is up with 2.3.x

I'm surprised more people haven't reached out regarding this issue as the crash seems to affect both of my rPi setups.

Share this post


Link to post
Share on other sites

@VDub While we are checking other options and trying to repro it in our lab: 1) haven't you notice how much memory Sync was consuming when it crashes? 2) if there any details you can share so we can attempt repro: what kind of OS you use, how many folders do you have, how many files and subfolders inside, etc.?

Share this post


Link to post
Share on other sites

@RomanZ Yeah, I monitored everything via htop.  Memory usage around 41%.  Seems to be similar to 2.2.x.  OS is a core version of Ubuntu 15.04 (GNU/Linux 4.1.7v7-aufs armv7l)  It is an option of BerryBoot.  Syncing 19 folders with about 4TB of data.  With many nested folders, large (4+TB [backups of virtual machines]) and very small files(eBooks, excel, pdf, etc).  Using Rasberry Pi 2B.

2.2.x Will push my rPi to the max while syncing everything for the first time, but it is stable and doesn't quit.  It seems like 2.3.x will actually work longer under heavy load (90mins), but seems to crash more quickly under less to no load (10-30mins).

My build uses a default download of Ubuntu 15.04 CORE through BerryBoot.  It is encrypted by berryboot.  I have an encrypted usb drive connected to the rPi using crypt, that auto mounts.  The bsync program runs in the root folder .btsync/btsync, and is running under the root user.  Furthermore, I have to use the --storage /root/.btsync/.sync option when running btsync due to the change of how 2.3 finds the identity, config, etc.  (Otherwise, when running 2.3.x it can't find the old folder from the 2.2.x and previous version, and wants me to start everything over.)  I am not using a .config folder/file

I hope this helps.  Thanks so much for creating such an great piece of software!

Oh, I run 2.3.3 on two Debian builds (not rPi architecture, rather in a VirtualMachine) and btsync works great!

Edited by VDub

Share this post


Link to post
Share on other sites
On 2016-03-01 at 4:46 PM, VDub said:

I actually am having this very same problem.  I have an encrypted rPi setup, and was running btsync 2.2.x for months with no problem -- syncing to encrypted external 3TB hard drives.  After updating to 2.3.3, the btsync seems to crash every 30-90minutes. I can't seem to figure out why.  When i switch back to btsync 2.2.x, it seems to work fine...

Is anyone else having this issue?

I haven't got this issue before, it started yesterday. i turned overclocked to 1ghz and also installed plexmediaserver, which is pretty heavy.

[12031.754019] Out of memory: Kill process 683 (btsync) score 460 or sacrifice child

probably not Sync's fault here.

Share this post


Link to post
Share on other sites

@RomanZ I wanted to update my memory usage -- I've been monitoring things closely today, and I'm seeing memory usage around 740Mb I think.  But again, this is under heavy load.

Share this post


Link to post
Share on other sites

@VDub Thanks for info. Could you send me full log from your RPI? It's not as good as dump, though still can give us some hints on what happens on your raspberry.

Share this post


Link to post
Share on other sites

Hello to all,

I was on vacation for a few days. The sync (about 700 GB) was completed before I startet the trip, so btsync on the rPi was i a idle mode for more than 6 days.

What coul I say. The process did not crash meanwhile. I uploaded now some pictures to the sync folder of my PC (about 20 GB) and it synced well.

Maybe its only a problem with havy load over a long time, maybe a problem with i/o on HD? I have heatsinks on the rPi, but if it is a thermal problem, the whole rPi should be instable.

Share this post


Link to post
Share on other sites

Hello @Roman Z

I've probably the same issue than @VDub currently with a Raspberry Pi B (the first one). I'm running Sync 2.3.5 (latest at the moment). I'm indexing several important folders stored on a 3.5 USB drive (with external power supply). Pi CPU usage is important for the btsync program (80%), and it's the same for the Mem usage. The Btsync app crash after approx 1h. No other apps are running on this Pi.

Kern.log contains :

kernel: [1876371.227781] Out of memory: Kill process 30420 (btsync) score 818 or sacrifice child
kernel: [1876371.227805] Killed process 30420 (btsync) total-vm:570284kB, anon-rss:385016kB, file-rss:504kB

Do you know if the performances are really different with btsync and the new Pi3 ?

Thanks !

 

Share this post


Link to post
Share on other sites

I am running the latest BitTorrent Sync version on a Raspberry Pi v1 and it is perfectly fine without issues so there is no need for you to upgrade to Raspberry Pi v3.

Like previously, it is a great help to follow the steps the Team has given to troubleshoot the issue you are experiencing.

Share this post


Link to post
Share on other sites

@citronbleu It directly depends on amount of files you attempt to Sync. If you'll try to sync 1M of files, Sync will hog your RPI rather quickly. RPIv1 has only 512Mb, so that would be enough for around 300K of files - if you leave no space for other apps in RAM ;)

Share this post


Link to post
Share on other sites

Hi @Roman Z

Thanks for your feedback. I have several RO folders synced :

- Folder 1 : 160 GB, 25 000 files

- Folder 2 : 30GB, 16 000 files

- Folder 3 : 13GB, 800 files

- Folder 4 : 22GB, 4 000 files

What kind of information can I provide to Support team if you this this is not normal to have this sort of behaviour ?

Thanks !

 

 

Share this post


Link to post
Share on other sites

Same issue here but with BitTorrent Sync 2.3.6 (378) running on a BeagleBone White under Linux BeagleBoneWhite 3.8.13-bone79.

[  428.033327] Out of memory: Kill process 942 (btsync) score 579 or sacrifice child
[  428.041226] Killed process 942 (btsync) total-vm:234080kB, anon-rss:150724kB, file-rss:500kB

Sync crashes when I launch the web GUI.

Under /.sync, one .db file weights 1172480 and one .db-wal 1032312. Files in the /.sync directory are to big to be attached.

I've opened a ticket as suggested.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.