![]() ![]() This appears to be something introduced in the latest build, for sure. I am also logged into the PC as the local admin account. so it's not an apparent permissions issue. These are clean, empty folders that are under the same share as the existing BTSync folders that I am currently using/syncing.Īny ideas? On the NAS I have full control (R/W) on the share, and I can go to the share and create / rename, place files, etc. (Cannot open Destination).Īlso, if I view the Folders tab of the application, looking at all of my existing folders which were working, under 'Size', they now all show the same error messageĪs for the new folders, I am creating, not adding someone else's secret, so it's not an issue with the sync folder missing on their end. This has been working fine for many weeks, but after the latest build, if I create a new folder under the share and then try to add the folder to BTSync, I immediately get the same error. I am using a NAS, and have setup BTSync to hit several folders via UNC paths. NAT-PMP: Unable to map port with NAT-PMP. Incoming connection from 192.168.1.101:56134 Notes: To resume sync tasks in Synology Drive Client, double-clicking on the Synology Drive Client icon from Windows system tray or Mac menu bar, select the server or task with issues, and click Resume. I tried to set it up completely new (renamed the bittorrent folder under 'application data'), but that did not solve it. With btsync 1.1.22 I keep getting the error "can't open the destination folder". With btsync 1.1.15 I had no problem adding z:\ to btsync. I have a boxcrypt partition containing the data (z:\). Settings.dat and as they were after stopping btsync.Ībout the sync.I installed btsync 1.1.22 on windows xp. ![]() Sync.log which was recorded while I started btsync, waited some minutes, started WebGui, waited, changed some preferences, waited, rebooted NAS, waited, stopped btsync. Progress, Last synced)Īfter I removed one connection to a shared folder on the other NAS it was really removed from the list, it wasn's visible anymore after restart, but trying to re-add the same folder again fails with a message 'the selected folder is already added to sync', even after I manually deleted the '.sync' folder, so it seems the removing wasn't done completely. If you need to synchronize files owned by current user - just add rslsync user to group of your current user and ensure read-write permissions for the mentioned group for the folder to be synced, for example: sudo usermod -aG usergroup rslsync. I tested a lot, nearly every modification I make in the WebGui is undone after restarting (allthough it persists when I close/open WebGui without re-starting):Īdditional added rows in the WebGui-overview (i.e. To enable automatic startup of Sync service under rslsync user: sudo systemctl enable resilio-sync. MC : too many nodes to send 190671, stopping at /NAS_II//Ī tipp I found in the internet told increasing max_torrent_metadata_size could probably solve the problem - I tried to do this and suprisingly found the change is undone when I restart BitTorrent Sync (no matter if I use the start-stop script or with reboot). MC : processing get_nodes message for /NAS_II// Now I noticed syncing files (I guess only new ones, but can't ensure) from one NAS to the other one fails since about one month ago, in the log I see lot's of messages like this: I have two NAS (DS 214, DSM 6.1.3-15152 Update 3) with BitTorrent Sync (Version 2.3.7-1) to synchronize data between distant locations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |