Search the Community

Showing results for tags 'logging'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. I think a key missing feature from Sync is stopping errors from propagating by interacting with the user and presenting her with options on what one can do. As an example, I recently filed an issue #49958 where the indexing was out of control. It turned out that due to some naming conflict (probably due to the composed/decomposed issue) *.Conflict folders were being created. By the time we found out why indexing never finished 1.4 million such conflict folders had been created for one particular weirdly named folder. When stuff like that happens Sync should notify the user that something really fishy is going on (ok, I am a programmer so I know that is way too wide description to implement, but you get the gist) and some possible solutions like: Folder X is causing conflicts because of naming issues. These are your options for fixing the problem: - Notify user X that the created file Y has a filename causing problems and ask her to rename the folder - Do X - Do Y We will stop sync for this subfolder/item until the problem has been fixed. If there had been some kind of "cross-network error diagnostics" built into the protocol maybe errors that arise on another peer than the one that created the filename can be propagated back to the origin to fix the error in the source. AFAIK only the "destination" peer gets any info through the GUI that a filename contains illegal characters, and from my experience they have no idea what to do about it (if they even understand it's a problem).
  2. Hi. I am using btsync (newest version, 1.3.106) on a few computers (windos 8, 64 bit), spreaded around germany and connected via VPN. I now realised, that the logging ("chronic" on GUI) doesn't show up the actual changes correctly. I don't know, if this is already in fixing but i didn't see a thread about this. Many changes are logged there, but some changes (adding new small txt-file to sync.folder or deleting some small files) aren't shown up there BUT they are still synced correctly. This happens not only on one computer, it happens on at least 2 and i think it will happen on every computer. Already known? Need more Information about this? Hope to get this small bug fiyed Best wishes spYro
  3. During this discussion with knireis I discovered, that btsync 1.2.68 has stopped saving it's log file in the storage_path. Also creating the ominous debug.txt file in the storage_path has no effect. It seems that the entire logging in 1.2 is broken, since I found absolutely nothing. Look: linux-dev-64 /var/lib/btsync # echo FFFF > debug.txtlinux-dev-64 /var/lib/btsync # service btsync restart* Stopping P2P file synchronisation daemon(s)...* Stopping btsync instance 'debconf-default' ...done.* Starting P2P file synchronisation daemon(s)...* Autostarting btsync instance 'debconf-default' ...done.linux-dev-64 /var/lib/btsync # ls -latotal 316drwxr-xr-x 2 root root 4096 Nov 12 12:07 .drwxr-xr-x 42 root root 4096 Nov 6 21:05 ..-rw-r--r-- 1 root root 5 Nov 12 12:07 debug.txt-rw-r--r-- 1 root root 2714 Nov 12 12:07 settings.dat-rw-r--r-- 1 root root 2714 Nov 12 12:07 settings.dat.old-rw-r--r-- 1 root root 210 Nov 6 21:15 sync.dat-rw-r--r-- 1 root root 85324 Nov 12 12:07 sync.lng-rw-r--r-- 1 root root 6 Nov 12 12:07 sync.pid-rw-r--r-- 1 root root 206647 Nov 12 12:07 webui.ziplinux-dev-64 /var/lib/btsync # cat /etc/btsync/debconf-default.conf//!/usr/lib/btsync/btsync-daemon --config//// Default instance automatically created by debconf//// DO NOT EDIT THIS FILE MANUALLY - SERIOUSLY//// THIS FILE WILL BE OVERWRITTEN AT EVERY UPDATE// OR RECONFIGURATION SO DO NOT EVEN TRY IT//// USE dpkg-reconfigure btsync INSTEAD TO MODIFY// THE CONFIGURATION////{ "device_name": "linux-dev-64 - Default Instance", "storage_path" : "/var/lib/btsync", "listening_port" : 0, "check_for_updates" : false, "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "disk_low_priority" : true, "lan_encrypt_data" : true, "lan_use_tcp" : false, "rate_limit_local_peers" : false, "folder_rescan_interval" : 600, "webui" : { "listen" : "0.0.0.0:8888", "login" : "admin", "password" : "asd" }}linux-dev-64 /var/lib/btsync # Where has the log file gone?
  4. I have BtSync set up on a handful of machines and it's working great: Debian 7 (x86) - 192.168.10.102 Debian 7+ (Testing) (x86) - office computer Android 4.2 - 192.168.10.105 Android 4.1 - 192.168.10.106 This machine doesn't work: Debian 7+ (Testing) (x64) - 192.168.1.100 Network setup: Internet > 192.168.1.0/24 Router, anything on this network BtSync won't work > 192.168.10.0/24 Router, anything on this network BtSync works fine On the problem machine (192.168.1.100), I cannot get anything to connect outside of that subnet. The router has UPnP enabled and netstat shows the btsync is listening, but nothing connects. I can connect/sync if I have both devices on the same network subnet (192.168.1.0/24) but nothing outside of that will connect; I have another router and devices on the 192.168.10.0/24 range (router IP 192.168.1.111) and they work fine (and the 192.168.10.0 network uses the 192.168.1.0 network as the default gateway). So I have to think the network is allowing traffic through, if the 192.168.10.0 network functions. I've tried using a custom config for btsync, no change;I've ensured UPnP was enabled in my routers (error before this was "Could not map UPnP Port ___ retrying.");I've found the .sync/ folder and tried to create ~/.sync/debug.txt with FFFF inside it, but nothing shows in the logs;I've tried running with --nodaemon but there are no messages being printed to stdout or stderr that I can see (now that "Could not map UPnP..." is resolved)netstat shows the ports listening;there is no local firewall running on this machine at this timeconnections don't work to the next router (downstream) nor over the Internet (upstream) I am out of ideas, can anyone help me?