zczcz

Members
  • Content Count

    10
  • Joined

  • Last visited

About zczcz

  • Rank
    Member
  1. User has been created: "rslsync:x:998:995::/home/btsync:/sbin/nologin" Directories and files have been created: "/etc/resilio-sync" "/var/lib/resilio-sync" [all files copied here] "/etc/init.d/resilio-sync" "/usr/lib/systemd/user/resilio-sync.service" ...
  2. I'm on a Raspberry Pi 1B and this is what I get. $apt-get install resilio-sync .... Setting up resilio-sync (2.4.4-1) ... Job for resilio-sync.service failed. See 'systemctl status resilio-sync.service' and 'journalctl -xn' for details. invoke-rc.d: initscript resilio-sync, action "start" failed. dpkg: error processing package resilio-sync (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resilio-sync E: Sub-process /usr/bin/dpkg returned an error code (1) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $sudo systemctl status resilio-sync.service ‚óŹ resilio-sync.service - Resilio Sync service Loaded: loaded (/lib/systemd/system/resilio-sync.service; enabled) Active: failed (Result: start-limit) since Fri 2016-12-16 00:47:27 PST; 5min ago Docs: http://help.getsync.com/ Dec 16 00:47:27 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. Dec 16 00:47:27 RPi1B systemd[1]: resilio-sync.service holdoff time over, scheduling restart. Dec 16 00:47:27 RPi1B systemd[1]: Stopping Resilio Sync service... Dec 16 00:47:27 RPi1B systemd[1]: Starting Resilio Sync service... Dec 16 00:47:27 RPi1B systemd[1]: resilio-sync.service start request repeated too quickly, refusing to start. Dec 16 00:47:27 RPi1B systemd[1]: Failed to start Resilio Sync service. Dec 16 00:47:28 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $ sudo journalctl -xn -- Logs begin at Thu 2016-12-15 19:47:48 PST, end at Fri 2016-12-16 00:51:18 PST. -- Dec 16 00:47:27 RPi1B systemd[1]: Failed to start Resilio Sync service. -- Subject: Unit resilio-sync.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit resilio-sync.service has failed. -- -- The result is failed. Dec 16 00:47:28 RPi1B systemd[1]: Unit resilio-sync.service entered failed state. Dec 16 00:47:31 RPi1B sudo[4538]: pi : TTY=pts/0 ; PWD=/etc/init.d ; USER=root ; COMMAND=/usr/bin/dpkg --configure resilio-sync Dec 16 00:47:31 RPi1B sudo[4538]: pam_unix(sudo:session): session opened for user root by pi(uid=0) Dec 16 00:47:32 RPi1B systemd[1]: Reloading. Dec 16 00:47:33 RPi1B systemd[1]: Reloading. Dec 16 00:47:34 RPi1B sudo[4538]: pam_unix(sudo:session): session closed for user root Dec 16 00:47:34 RPi1B systemd[1]: Failed to send queued message: Transport endpoint is not connected Dec 16 00:51:18 RPi1B sudo[4614]: pi : TTY=pts/0 ; PWD=/etc/init.d ; USER=root ; COMMAND=/bin/journalctl -xn Dec 16 00:51:18 RPi1B sudo[4614]: pam_unix(sudo:session): session opened for user root by pi(uid=0) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: $sudo dpkg --configure resilio-sync Setting up resilio-sync (2.4.4-1) ... Job for resilio-sync.service failed. See 'systemctl status resilio-sync.service' and 'journalctl -xn' for details. invoke-rc.d: initscript resilio-sync, action "start" failed. dpkg: error processing package resilio-sync (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: resilio-sync :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: I also get this error: $systemctl --user enable resilio-sync Failed to get D-Bus connection: No such file or directory Any idea what's going wrong?
  3. I have a similar issue for a file which does NOT exist on the drive (not even hidden). I am using 3 nodes (2 Windows, 1 linux) with v2.3.3 (296). The problem affects the linux client which thinks the folder is synced and doesn't transfer any other file within that folder. The Windows hosts sync all the files without problems. Log from Linux client: [20160224 16:16:43.899] MC[DF37] [FDB8]: failed to verify signature of remote file IMGPXYZ.JPG, aborting [20160224 16:16:43.900] assert failed /opt/sync/SyncFolderMergeController.cpp:880 By the way this path does not exist too: "/opt/sync/". Log from Windows client: [2016-02-24 16:18:23] MC[DF37] [5FE7]: will send files for /IMGPXYZ.JPG* This file was there months ago with incorrect timestamp and I had deleted it when I saw the error. Since then I have upgraded to several newer versions of BTSync and the problem is still there. I have used different folders to sync, I have deleted all files and started from scratch, nothing worked! This file does NOT exist on any client these days but I still see it in my logs and the linux host doesn't sync this folder. Is it cached somewhere? How can I get rid of it?
  4. Hi guys, I have 2 clients with version 1.4.111, one client has write access on a folder (Windows) and the other one read-only (Linux Raspberry Pi). There was a problem with one file because of incorrect timestamp, but then I deleted the file from the Windows client. I still get the following errors even if this file does NOT exist on any node, it was deleted some days ago. Log from the read-only Linux client: [20150414 11:18:44.824] Incoming connection from 67.215.229.106:3000 [20150414 11:18:47.089] MC[DF37] [FDB8]: failed to verify signature of remote file IMGP111.JPG, aborting [20150414 11:18:54.543] Incoming connection from 67.215.229.106:3000 [20150414 11:18:55.205] MC[DF37] [b784]: failed to verify group signature of files message, aborting Does the relay host store any files??? I uninstalled the Linux client, deleted the databases and installed again but nothing changed. I would like to avoid generating a new key because there are more clients connected which are currently offline and the change is not gonna be easy. Any help would be appreciated.
  5. Thank you kos13 for your comment, it would be nice to have an official detailed reply from you with comments to all their findings.