yifanlu

BitTorrent Sync OSX crashing consistently

Recommended Posts

BTSync worked for a day and now it always crashes a minute after launching it. I've tried restating OSX and quitting other apps (including Transmission), but it still crashes. It's always about a minute after launch (usually while it's indexing). If it helps, I have another mac on the network also running btsync (with no error). I'm also syncing files from an external drive.

 

I've attached a crash log BitTorrent Sync_2013-09-19-215955_Yifans-MacBook-Air.txt

Share this post


Link to post
Share on other sites

Hi,

 

One other place to look for information is the sync.log file in the library folder:

/Users/<yournamehere>/Library/Application Support/BitTorrent Sync

Maybe have a look at suspicious entries and/or attach to a post here as well.

Share this post


Link to post
Share on other sites

Hmm, the file does not give any indication on what is going on. You can have a more verbose output in sync.log if you check "Enable Debug Logging" in the menu options. Maybe something then crops up, which goes unnoticed otherwise.

 

And then, does it always crash with the Documents folder being last? Maybe a new file in there creates problems?

Share this post


Link to post
Share on other sites

It's crashing for me too, but not until I started syncing a much larger folder than I was before (went from hundreds of megabytes to 1.6 GB).  The last message in the sync.log says:

 

[20130922 21:39:07.537] Going to connect to peer 192.168.1.10:27168 for file <some file.png>
[20130922 21:39:07.537] Finished receiving metadata for '<some file.png>'
 
(where <some file.png> is an actual filename and path)
 
And then it just quits.  Not clue as to why.  I'm running btsync 1.1.70 on Max OS X 10.8.4.  I have messages that 10.8.5 is ready to install, I just haven't done it yet.  The peer at 192.168.1.10:27168 is my Linux desktop, running 1.1.70 also, in case that helps.

Share this post


Link to post
Share on other sites

Just noticed a few lines up in the sync.log that there is a file with a <DF> in the name (highlighted, when I view sync.log with less).  When I view sync.log with emacs it's this character: ß and when I look at the actual file on the original machine (a linux box), it has a question mark in the name.  I'm not sure where that came from, but could that be the problem?  It does not exist on the Mac, like it never actually go copied over.

 

Wow!  Getting off topic now, but I had synced the same folder using Spideroak before, and I just looked at the destination folder and that file with the ? in the name is completely missing.  Spideroak just silently skipped right over it, apparently.  I guess other apps have problems with that filename too...

Share this post


Link to post
Share on other sites

Hmm, the file does not give any indication on what is going on. You can have a more verbose output in sync.log if you check "Enable Debug Logging" in the menu options. Maybe something then crops up, which goes unnoticed otherwise.

 

And then, does it always crash with the Documents folder being last? Maybe a new file in there creates problems?

 

 

I think I found the problem. It was a link that was invalid. I had a "backup" of /proc from an embedded linux machine on my OSX computer. One soft link in this folder had permissions that was l-wx------ but I couldn't access or change the permissions (to see where the link pointed to). I deleted this /proc backup directory and sync works.

Share this post


Link to post
Share on other sites

Just noticed a few lines up in the sync.log that there is a file with a <DF> in the name (highlighted, when I view sync.log with less).  When I view sync.log with emacs it's this character: ß and when I look at the actual file on the original machine (a linux box), it has a question mark in the name.  I'm not sure where that came from, but could that be the problem?  It does not exist on the Mac, like it never actually go copied over.

 

Wow!  Getting off topic now, but I had synced the same folder using Spideroak before, and I just looked at the destination folder and that file with the ? in the name is completely missing.  Spideroak just silently skipped right over it, apparently.  I guess other apps have problems with that filename too...

 

The same problem was reported by some other users in this forum, citing that using the french accents in filenames caused trouble as well. For the time being, it seems best to stick with the US alphabet without any localised characters.

Share this post


Link to post
Share on other sites

More information this morning.  I tried syncing the same directory (with the filename with a ? in it) with another linux machine and it synced just fine, question mark and all (so, for the record, it handled it better than Spideroak).  Next I'll trying renaming the file to get rid of the question mark and see if the Mac btsync client can proceed without crashing.

Share this post


Link to post
Share on other sites

Mac OS 10.9; when I try to launch BitTorrent Sync I get the following any suggestion much appreciated. 

 

Bus error: 10

 

Hi!

Do you get this error after update to 1.2.82 version or after clean install?

Thanks!

Share this post


Link to post
Share on other sites

I am having constant crashes on the Mac as well. I am also running it on two other windows machines on my network and the windows versions are stable. The Mac one crashes constantly and is unusable.

 

I have sent in some of the crash report logs via the send feedback option in sync.

Edited by aoleon

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.