teoky

Members
  • Content Count

    15
  • Joined

  • Last visited

  • Days Won

    1

About teoky

  • Rank
    Member
  1. Hello Helen Yes both SyncShellExtension64_33554560.dll and SyncShellExtension86_33554560.dll are there. Also tried restarting explorer.exe and restarting Windows and it still not working. Actually I wrote to Bittorrent Sync Support. They suggested the same thing as you so I explained that it didn't solve the problem. That was 3 days ago and we have had no further reply from Bittorrent Sync Support :/
  2. @adam1v We ended up having to connect all users to the NAS as the user 'admin' which isn't ideal. Have just upgraded to btsync version 2.0.105 and will test this again. Will post if there is any update. Did anyone else test this with version 2.0.105? Thanks
  3. @RomanZ @vildhet @timdj @cranberry @lepbtsync, did you find a solution to the problem on this post? I am experiencing a similar problem on a QNAP NAS. See more detailed in at: http://forum.bittorrent.com/topic/32188-problem-with-qnap-and-bitorrentsync-1476/ Thank you
  4. This is everything that is logged before btsync crashes (Have used "#" to hide identifiable things like IP addresses): total physical memory -1 max disk cache #######Using IP address ###.###.###.250Loading config file version 1.3.106UPnP: Device error "http://###.###.###.251:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.250:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.66:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Device error "http://###.###.###.10:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Could not map UPnP Port on this pass, retrying.UPnP: Device error "http://###.###.###.250:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.251:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.66:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Device error "http://###.###.###.10:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Could not map UPnP Port on this pass, retrying.UPnP: Device error "http://###.###.###.250:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.251:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.66:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Device error "http://###.###.###.10:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Could not map UPnP Port on this pass, retrying.UPnP: Device error "http://###.###.###.251:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.66:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Device error "http://###.###.###.250:8080/##########.xml": (-2) UPnP: Device error "http://###.###.###.10:2869/upnphost/udhisapi.dll?content=uuid:########-####-####-####-############": (-2) UPnP: Unable to map port ###.###.###.250:41834 with UPnP.SF[####]: Loaded folder /share/MD0_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD1_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD1_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD1_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD1_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD1_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD2_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD0_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'SF[####]: Loaded folder /share/MD0_DATA/##########SF[####]: failed to read '/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability'Some observations: 1) "Loading config file version 1.3.106". This is strange since the App Manager in the QNAP control panel does report that BTSync is updated to version 1.4.76 2) I do not understand why BTSync is attempting to communicate with "http://###.###.###.251:8080/##########.xml" or "http://###.###.###.66:2869/". These are neither the NAS nor the router. 3) "/share/MD0_DATA/.qpkg/BitTorrentSync/.sync//########################################.availability" would never be able to be read because of the two "//" in the path after ".sync". Plus these ".availability" files do not exist. Other files exist with the same name but with different extensions as ".db", ".db-shm" and ".db-wal". I hope this helps to investigate the problem. Also I would really appreciate any advise on how to downgrade back to version 1.3. Many thanks
  5. Thank you @Shaav I was about to try out what you suggested but I updated to version 1.4 before trying and now btsync isn't working at all :/ I'll let you know once I can try it. Thanks!!
  6. I have just updated using the QPKG manager on a QNAP TS-809U and this is my experience: - After the update, btsync did not start automatically (or perhaps it did start but then crashed). - So I launched via ssh: /share/MD0_DATA/.qpkg/BitTorrentSync/btsync --config /share/MD0_DATA/.qpkg/BitTorrentSync/btsync.conf- When it is running, the GUI does not display at all in my browser at. It is clear that the browser is finding a page, but it is just completely blank. I have tried both Chrome and IE. - The bysync process eventually closes by itself after a few minutes. Am I able to downgrade to version 1.3? Thank you
  7. Thanks adam1v Actually that is the issue I am having. It is running 'a form' of linux but none of the normal linux fixes to this problem seem to apply to the QNAP version so I am stuck. If anyone does know how to do this, please let me know. Thanks!
  8. @adam1v Am I able to SSH into a QNAP NAS and modify the user of the btsync process? While I agree this this is not a solution, this would at least be a work around for me for now. I can not seem to find a way to do this. Actually, even if I could just set btsync to write the correct UMASK would be a workaround for now. I think the solution should be that the files and folders inherit the permissions of the parent directory. This is how it appears to work on the Windows and OS X versions. Thanks
  9. @RomanZ In the case of a QNAP NAS,... There doesn't appear to be a way to change the owner of the btsync process. Therefore users can not edit edit files and folders created by btsync because the users are not "Admin". There also appears to be no way to make btsync write with the correct UMASK to allow for the "group" to read/write. Thanks
  10. Hi Vitalii2014 and adam1v Still trying to find a solution. If you find one, please share it with me. I will do the same on here if I do. Thanks!
  11. Hi Richard I'm just trying to give users of the NAS read/write access to the syncronised files. Currently, if a file/folder is created on a PC or MAC which is running btsync, these files/folders are added to the QNAP NAS so that only the user "admin" has read/write access. Other users access this NAS as via network shares and can not edit anything created on the NAS by btsync (except for the user "admin") The group "bysync" is just an example. On the QNAP NAS, groups can be created (i.e. "department_a", "department_b", etc..) and users can be added to that group. We actually have several shared folders which bysync now sycronises across different physical sites. I have successfully managed to make files/folders created by btsync inherit the group permissions from the share's parent folder. The problem is that the group only has read permission and this needs to be read/write. I can't have all users logging on to the NAS' network share as the user "admin". Thanks
  12. Hi RomanZ Sorry for the confusion!.. I made a mistake.... I am running Bittorrent Sync on PCs and Macs also and they are all version 1.3.109. The version I am running on the QNAP is the QPKG standard installation and yes you are correct, I just double-checked and it is 1.3.106 Thanks
  13. Hi tuxpolodo Yes it is the QPKG. Is there a way to make the QPKG version of btsync write the file permissions we need? Thanks!
  14. Hello QNAP Model: TS-809U Firmware version: 4.1.0 Bittorrent Sync verison: 1.3.109 Linux version: 3.4.6 (root@NasX86-13) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 Normally, by default, Bittorrent Sync runs on linux as the user: “root” and group: “administrators” and writes these owner:group permissions to syncronized files and folder that it creates. In the case of the QNAP NAS, Bittorrent Sync writes files and runs as the user “admin”. I have successfully managed to enforce all sub-folders and files in my sync folder to inherit the group “btsync” in the file permissions by using: chown admin:btsync /syncchmod g+s /syncThe problem is that Bittorrent Sync creates new files and folders with read-only permissions for the group “bysync” (i.e. wxr-xr-x / octal 0755). From researching I have found that the 2 ways to change this normally would be: 1) Add this line to the btsync.conf file and restart btsync: // DAEMON_UMASK=0022) Use the following command and when prompted enter "002" as the umask dpkg-reconfigure btsyncNeither of the 2 above methods resolve the issue. In the case of item 1, this setting seems to be ignored by btsync. With item 2, “dpkg-reconfigure” is not a command available on the version of linux used by the QNAP NAS. Thank you in advance for your help!