tiptronic

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by tiptronic

  1. @Gane O'dwyer What are the proper folder permissions?

    The current situation is like this:

    • If I copy to the NAS using AFP or SMB, the files/folders are copied using my user/group.
    • If I copy to a sync-folder on my Mac, the files are saved to the NAS as rslsync/rslsync.
    • Both users have full access to the synced folder(s) and the hierarchy up.

    Generally this work fine - except when the 'locked' message appears. Unfortunately I can't find out, what makes Sync to see the file as 'locked', because it is somwhat random.

    Any other idea what this could be? (Btw. the two NASes have different users)

    In the logs all I see is what I sent in my previous question.

  2. @Gane O'dwyerInterestingly this is only for *some* files and not for others. Sometimes it helps if I copy the file to Synology2 and then it syncs over to Synology1 - sometimes not. The mileage varies...

    So - why do I get a -13 error from 1 of 10 files I copy from my Mac to one of the Synologies? 

    After some days of working fine, today I had the problem again: I can't upload a file without getting the error.

    - If I copy the file to my Mac's Sync folder, it sometimes works, but sometimes it happens, that one of the Synologies gets the file and the other throws the 'file locked' message and doesn't sync the file.

    - If I copy the file to one of the Synologies using their own File-Manager, it mostly works, but sometimes the other Synology throws the 'file locked' message.

    - The behaviour is random - I couldn't find a pattern

    -> In all cases, my Macs get the file without any problems

    Could it be that the file gets locked when the Synology is indexing (or whatever)?

  3. So the locking problem is back :( 

    I try to sync on 2 x Macs and 2 x Synology, where all have the latest Resilio Sync version and identical Date/Time-settings and NTP-connections.

    There are a couple of files which won't sync. If I delete these files and re-upload (even under a different name), the problem appears again. But it seems to be dependent on: from WHERE I upload the file.

    Both Macs are synching fine!

    The log on Synology 1 sais:

    [20180301 08:13:43.528] Entry "/volume2/OFFICE 2016/Testfile.csv" was updated, current state: pvi[type:1 s:120203 mt:1519831315 h:], expected: pvi[NULL]
    [20180301 08:13:43.528] FC[AD41]: fs event for entry "/volume2/OFFICE 2016/Testfile.csv" t:1519831315 s:120203 id:2307:108437560 type:1
    [20180301 08:13:43.529] TorrentController: (reading) failed to open file "/volume2/OFFICE 2016/Testfile.csv" - 13
    [20180301 08:13:43.529] JOURNAL[AD41]: cancelling new entry job for "/volume2/OFFICE 2016/Testfile.csv" - failed to init tf
    [20180301 08:13:43.529] JOURNAL[AD41]: repost fs event for path "/volume2/OFFICE 2016/Testfile.csv"  - torrent creation aborted
    [20180301 08:13:53.093] Entry "/volume2/OFFICE 2016/Testfile.csv" was updated, current state: pvi[type:1 s:120203 mt:1519831315 h:], expected: pvi[NULL]
    [20180301 08:13:53.093] FC[AD41]: fs event for entry "/volume2/OFFICE 2016/Testfile.csv" t:1519831315 s:120203 id:2307:108437560 type:1
    [20180301 08:13:53.093] TorrentController: (reading) failed to open file "/volume2/OFFICE 2016/Testfile.csv" - 13
    [20180301 08:13:53.093] JOURNAL[AD41]: cancelling new entry job for "/volume2/OFFICE 2016/Testfile.csv" - failed to init tf
    [20180301 08:13:53.113] JOURNAL[AD41]: repost fs event for path "/volume2/OFFICE 2016/Testfile.csv"  - torrent creation aborted

    The log on Synology 2 (btrf):

    I already re-verified users/groups/file- and folder-permissions... Now I'm running out of ideas. Anyone can help?

    And I think, this one could be related:

    [20180301 08:13:43.523] JOURNAL[AD41]: won't perform job for entry "andy/2018/18-D-156.pdf" - parent has fs error
    [20180301 08:13:43.524] JOURNAL[AD41]: won't perform job for entry "andy/2018/18-D-159.pdf" - parent has fs error

    Re-uploading the files doesn't help - after a minute the problem appears again. But there are more files in the folder, which sync fine. It seems to be dependent on from where the file was added (or to which device).

    Any ideas with that??

    Any info appreciated!

    andy

  4. I have the same problem since today (after installing Apple's latest software security update - as of 2018-02-21).

    I re-verified ALL my connected peers and they have all the same time (since they all access the same ntp).

    Resilio Sync still says 'Invalid time'. Unfortunately there's nothing in  the logs (or wherever) which indicates which of the peers it thinks there is a problem...

    Any hint?

    thx

    andy

  5. Just before I wrote the comment, I updated everything to 2.5.12 (1911)

    When I add a file on Syno1 (using FileStation) it syncs fine. Everything syncs fine on my Macs. When I add files through Finder (onto the Syno Mount) it doesn't sync.

    I just saw, that most of the files have the correct rights and some has a user rslsync... Do I explicitely add a user rslsync to the Synologies?

  6. Is there any news to this problem?

    I just tried to add a folder from my old Synology 412+ (6.2) to my new Synology 718+ (6.2). And as soon as I add a file from my Mac to one of the Synology folders (using smb), I am getting the exact 'locked' file error...

    Now I have 3 sync folders and everything has a different state. I restarted the Synologies Sync, re-added the folders, changed/verified permissions, but nothing worked.

    Any idea - except using 2.3.8?

  7. Hi Helen,

    thx for the hints. I dunno what happened - here's a summary:

     

    - the folders were always read/write (under 1.4)

    - when I installed 2.2.0 it showed all folders read/write (in the BTSync window), but I noticed, that the Finder-icon showed a strike-through pen (read-only?)

    - I couldn't relink the folder to make it read-write, so

    • I stopped BTSync 2.2.0
    • I created a fresh folder (same name) and moved all data but the '.sync' folder to the new folder
    • re-connected the folder

    now everything works again...

    Interestingly there is another folder showing the same habit (any other folders (3 more) are fine)...

     

    Very mysterious... - but now it works again (leaving a slightly bitter feeling behind). ;)

     

    thx for your support

  8. After the announcement of policy changes starting with 2.2.x I gave BTSync 2.2.0 a shot, but it doesn't work :(

     

    - I have 3 Macs (Home, Office, Mobile) synced fine (different folder-trees) using 1.4.x

    - Now I updated 1 Mac to 2.2.0 and syncing only goes into 1 direction (from 1.4 -> 2.0). 

      -> Folders on the updated Mac show their '1.4' folder-sign

      -> If I add a file to one of the Macs using 1.4.111, sync works accross all devices

      -> If I add a file to the new 2.2.0, nothing is synced to the 1.4.111

     

    How can I fix this? (And no: I can't/won't just update all devices, since I also share a couple of folders with family, who are far away and still on 1.4.111 and I don't have access to their machines.)

     

    Is there a way to sync from 2.0 to 1.4.111 reliably or do I need to go back to 1.4.111? (Can I go back without loosing all my synced settings)?

  9. @tiptronic

    Can you provide your javascript console output so we can take a look what happens there? Also, which browsers you tried to open the WebUI? Is it simply blank or it shows something like "Page cannot be found", etc.?

     

    Hi Roman,

     

    it is simply blank.... 

     

    In Google Chrome the UI sometimes shows 'Welcome to BitTorrent Sync' (after a while), but then stops there. Console is also blank. At this point I am able to open Preferences. When clicking the UI preferences, there are chances, the UI finally loads - but not before messing with the UI preferences.

     

    In Safari I found out, that if I open the Web-Inspector and follow the network-request, the last request doesn't come back most of the times... but sometimes it comes back after 30 seconds or a minute or more (this is on a 1Gbit LAN).

     

    Fonts (e.g. opensans-regular.woff have a mime-type of text/html - that should be "application/x-woff" anyway). Maybe the whole font-declaration in your css is not correct - that would explain those IE problems. (Btw: why not remove theses fonts alltogether - or optionally load them - and fall back to Helvetica and Arial; I think this would solve lots of IE problems automatically)?

     

    andy

  10. I just got the auto-update of 1.4.-72on my Synology 409 and now I got a blank window as well. 

     

    Please note:

    This is on Mac OSX 10.9.4 - I tried Safari, Chrome and Firefox (all latest builds available).

     

    Also I noticed, the btsync process takes 150MB RAM on the Syno (which is lots on this old chap). Can I somehow force it to purge btsync's memory?

     

    I just updated to 1.4.83-8... no change... The Javascript stack starts running, but nothing is added to the body.... (Same devices as above)

  11. I just got the auto-update of 1.4.-72on my Synology 409 and now I got a blank window as well. 

     

    Please note:

    This is on Mac OSX 10.9.4 - I tried Safari, Chrome and Firefox (all latest builds available).

     

    Also I noticed, the btsync process takes 150MB RAM on the Syno (which is lots on this old chap). Can I somehow force it to purge btsync's memory?

  12. Although not really aggressive, BTSync 132 needs more CPU power when idle, than 116 did.

    On my MacBookPro (late 2008), 10.8.3, 8GB RAM it takes approx. 0.6-1.2% CPU (12 Threads) when idle. The 116 version took 0.02-0.06%...

    This is just an observation... I don't know if this is informative for anyone, but anyway...

    andy