jocko

Members
  • Content Count

    16
  • Joined

  • Last visited

About jocko

  • Rank
    Member
  1. Hi thomas, You forgot a comma in your json file: "force_https" : true ,"ssl_certificate" : "/etc/resilio-sync/cert.pem" "ssl_private_key" : "/etc/resilio-sync/pkey.pem" missing an ',' just before "ssl_private_key". This comma closes the previous line
  2. jocko

    Latest desktop build 2.6.0

    Hi There is an undocumented change in the releases note. Indeed at least since version 2.6, some events in history are hidden on a free licence version. Only returns the mention "Upgrade to Pro". Please, can you give what sorts of event are impacted by this change ?
  3. jocko

    Fake core warning

    Thank you it is done
  4. jocko

    Fake core warning

    Just an additional information, free space on the operating system is root@Acrab:/ # df -h /share/1100/btsync Filesystem Size Used Available Use% Mounted on /dev/md0 10.8T 3.6T 7.1T 34% /share/1100 root@Acrab:/ # df -h / Filesystem Size Used Available Use% Mounted on /dev/sda1 226.2M 186.3M 27.4M 87% /
  5. jocko

    Fake core warning

    Hi, With version 2.6.0 on a linux OS, I get this core warning In your help page, you write this warning appears if there's less than 1 Gb left on the operating system. Sync runs as root and it runs in config mode and uses a large operating partition (in my case a raid5 12TB). In config file, storage_path is set with the line "storage_path" : "/share/1100/btsync", and /share/1100 is the mountpoint of my raid. Indeed, on the fs partition (where is the mountpoint) I have less than 1GB free space (~40MB) and it seems Sync does not follow the mountpoint to get the real free size
  6. jocko

    Latest desktop build 2.6.0

    Thank you Helen. Additional information for linux user, if you have this error message in sync.log OpenSSL: can't find suitable trusted CA location That means your CA file is not stored in the locations handled by resilio /etc/ssl/certs/ca-certificates.crt /etc/pki/tls/certs/ca-bundle.crt /usr/share/ssl/certs/ca-bundle.crt /usr/local/share/certs/ca-root.crt /etc/ssl/cert.pem In this case just create a symlink by using one of these paths toward your ca file (in my case was /usr/ssl/cert.pem)
  7. jocko

    Latest desktop build 2.6.0

    Hi I just tested the new version 2.6.0 and I notice some advanced user options are no longer supported with the last version : root@Acrab:/ # /direct-usb/fvdw/addons/sbin/btsync --config /rw_fs/etc/btsync.conf [20180731 15:56:31.992] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'send_buf_size'" [20180731 15:56:31.996] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'send_buf_size'" Error while parsing config file: Invalid key 'send_buf_size'Error while parsing config file: Invalid key 'send_buf_size' root@Acrab:/ # /direct-usb/fvdw/addons/sbin/btsync --config /rw_fs/etc/btsync.conf [20180731 16:00:19.077] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'recv_buf_size'" [20180731 16:00:19.080] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'recv_buf_size'" root@Acrab:/ # /direct-usb/fvdw/addons/sbin/btsync --config /rw_fs/etc/btsync.conf [20180731 16:01:13.161] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'enable_journaling'" [20180731 16:01:13.164] Can't parse config file "/rw_fs/etc/btsync.conf": "Error while parsing config file: Invalid key 'enable_journaling'" root@Acrab:/ # /direct-usb/fvdw/addons/sbin/btsync --config /rw_fs/etc/btsync.conf (note: we use a btsync symlink for compatibility issue with old version of our firmware and currently we use version 2.5.2) So at least these options can be no longer used: send_buf_size; recv_buf_size; enable_journaling Only the last option removal is annoying as it allowed to standby the disk on NAS with our firmware. Is there another option or now is useless ?
  8. I see that version 2.5.4 allows now to configure this option via the config file Thank you
  9. Hi Helen, Yes now after the page 404, the server redirects to the page 207371636. So it is ok.
  10. Thank you RomanZ. At least the main settings are here. About option "context" I already know how to use it with the sub-option "folder_blacklist" but maybe there are other sub-options... on version 2.5.2 (966), I also noted the link in sample-config output (option --dump-sample-config) is down: "http://help.getsync.com/customer/portal/articles/1902048-sync-advanced-preferences--more-options"
  11. Thank you, RomanZ for this feedback. Temporarily, we will add a symlink "/Resilio Sync" on the system partition towards /dev/null to avoid any overloading. Otherwise, I did not find information on some "un-documented" config options. For example like "display_new_version" or "context" which seems very handy or force_https, ...(or I did not succeed to find where they are available) Is there somewhere an advanced doc for setting config file?
  12. Well, seems to be a bad way. You use now an integrity check on settings The file '/share/1004/btsync/settings.dat' was damaged or missing. It has been recovered. and I assume by using the option '.fileguard' So how can I prevent an overload on the system partition if the user does not change this default path value ?
  13. Hi So nobody here for giving information ? I assume I may edit settings.dat on the option "files_default_path" by using the python script: btsync_edit_settings_w4.py But sadly, the link http://syncapp.bittorrent.com/support/script/btsync_edit_settings_w4.py is broken. How can I retrieve this file ? Thank
  14. Hi, We develop an alternative firmware for LACIE NAS (ARM version) and we added support for resilio (http://plugout.net). In your last version, I see a new option "File download location". Currently I do not understand the purpose of this option. I did not find how to change the default value "/Resilio Sync" which is very bad on our fimrware. So How I can change this default value so that it may be right with our environment. Anyhow I see this option handles the options "directory_root" and "directory_root_policy" set in the conf file as if the user wants to change the default value, the folder tree is built in accordance with these options.