w82

New Members
  • Posts

    9
  • Joined

  • Last visited

w82's Achievements

New User

New User (1/3)

  1. Hi, I made one small tweak to my config yesterday and since then, BTSync (latest official Linux version) no longer starts. Systemd kills it immediately, then retries infinitely, failing constantly. The change I made was the download directory for all the folders, from /path/a/b to /path/b. All paths exist and are accessible. The .sync folders are still present (though I did try deleting them all to see if that was causing an issue). Nothing else has changed. I've removed and purged btsync with apt-get, tried a basic config as well as my normal one. I've even tried the standard example from the installation. Nothing works, and what's weirder is nothing has (to my knowledge) changed on the system (a Pi). I've tried everything and am lost - some logs below, which hopefully someone can diagnose better than me. I think a dependency might be broken though... Thanks for any help! Will Systemd status May 23 18:58:44 raspberrypi systemd[1]: Started BitTorrent Sync service. pi@raspberrypi:~$ sudo systemctl status btsync.service ● btsync.service - BitTorrent Sync service Loaded: loaded (/lib/systemd/system/btsync.service; disabled) Active: inactive (dead) Docs: http://help.getsync.com/ May 23 18:58:25 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:30 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:58:32 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:58:33 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:58:36 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:41 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:58:43 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:58:44 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:58:46 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:58:50 raspberrypi systemd[1]: Stopped BitTorrent Sync service. pi@raspberrypi:~$ sudo systemctl status btsync.service ● btsync.service - BitTorrent Sync service Loaded: loaded (/lib/systemd/system/btsync.service; disabled) Active: inactive (dead) Docs: http://help.getsync.com/ May 23 18:59:46 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 18:59:51 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 18:59:53 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 18:59:53 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 18:59:55 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 19:00:04 raspberrypi systemd[1]: Stopped BitTorrent Sync service. May 23 19:00:06 raspberrypi systemd[1]: Starting BitTorrent Sync service... May 23 19:00:06 raspberrypi systemd[1]: Started BitTorrent Sync service. May 23 19:00:09 raspberrypi systemd[1]: Stopping BitTorrent Sync service... May 23 19:00:14 raspberrypi systemd[1]: Stopped BitTorrent Sync service. Sync.log (for the standard config) [19:00:52.412] Debug log mask has been set to FFFF [19:00:52.413] Features mask has been set to 0 [20160523 19:00:52.423] Configuration from file "/etc/btsync/config.json" has been applied [20160523 19:00:52.442] ZIP: Can't locate [version] in zip, error -100. [20160523 19:00:52.453] PLC[0x01f321c0] binding on 0.0.0.0:25768 [20160523 19:00:52.453] Socket[0x01f321c0][8] bound listening socket 8 to IP 0.0.0.0:25768 [20160523 19:00:52.454] UDP: bound listening socket 9 to IP 0.0.0.0:25768 [20160523 19:00:52.454] Socket[0x01f32dc0][10] bound listening socket 10 to IP 127.0.0.1:8888 [20160523 19:00:52.458] UPNP: Using IP address 172.16.0.95 [20160523 19:00:52.490] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642 [20160523 19:00:52.490] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD [20160523 19:00:52.490] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293 [20160523 19:00:52.492] Loading config file version 2.3.7, current version 2.3.7 [20160523 19:00:52.492] My PeerID: 10344197918885B006FE520626BBF53C4462DA96 [20160523 19:00:52.493] loaded history: 0 events [20160523 19:00:52.495] setup socket 14 for local peer discovery for 127.0.0.1: success [20160523 19:00:52.495] setup socket 15 for local peer discovery for 172.16.0.95: success [20160523 19:00:52.496] setup socket 16 for local peer discovery for 10.136.1.6: success [20160523 19:00:55.478] Received shutdown request via signal 15 [20160523 19:00:55.483] saved history: 0 events [20160523 19:00:55.503] SyncFolderScanner: shut down [20160523 19:00:55.503] Shutdown. Saving config sync.dat [19:01:02.925] Debug log mask has been set to FFFF [19:01:02.927] Features mask has been set to 0 [20160523 19:01:02.961] Configuration from file "/etc/btsync/config.json" has been applied [20160523 19:01:03.012] ZIP: Can't locate [version] in zip, error -100. [20160523 19:01:03.029] PLC[0x012481c0] binding on 0.0.0.0:31140 [20160523 19:01:03.036] Socket[0x012481c0][7] bound listening socket 7 to IP 0.0.0.0:31140 [20160523 19:01:03.036] UDP: bound listening socket 8 to IP 0.0.0.0:31140 [20160523 19:01:03.037] Socket[0x01248dc0][9] bound listening socket 9 to IP 127.0.0.1:8888 [20160523 19:01:03.038] UPNP: Using IP address 172.16.0.95 [20160523 19:01:03.057] test sha1: AE5BD8EFEA5322C4D9986D06680A781392F9A642 [20160523 19:01:03.057] test sha2: 630DCD2966C4336691125448BBB25B4FF412A49C732DB2C8ABC1B8581BD710DD [20160523 19:01:03.058] test aes: 0A940BB5416EF045F1C39458C653EA5A07FEEF74E1D5036E900EEE118E949293 [20160523 19:01:03.059] Loading config file version 2.3.7, current version 2.3.7 [20160523 19:01:03.060] My PeerID: 10344197918885B006FE520626BBF53C4462DA96 [20160523 19:01:03.060] loaded history: 0 events [20160523 19:01:03.061] setup socket 14 for local peer discovery for 127.0.0.1: success [20160523 19:01:03.062] setup socket 15 for local peer discovery for 172.16.0.95: success [20160523 19:01:03.062] setup socket 16 for local peer discovery for 10.136.1.6: success Sync.log (for my usual config) [20160523 19:06:04.913] SyncFolderNotify: Added path=/home/epistrophy/bt/Will-FileStore/rsyncNEW/home/pi/btsyncOLD with fd=176 [20160523 19:06:05.127] UPnP: Device error "http://172.16.0.221:8060/": (-2) [20160523 19:06:06.129] Received shutdown request via signal 15 [20160523 19:06:06.131] saved history: 0 events [20160523 19:06:08.135] UPnP: Could not map UPnP Port on this pass, retrying. [20160523 19:06:10.163] UPnP: Device error "http://172.16.0.17:9000/TMSDeviceDescription.xml": (-2) [20160523 19:06:10.185] UPnP: Device error "http://172.16.0.137:7676/smp_2_": (-2) [20160523 19:06:10.187] UPnP: Device error "http://172.16.0.137:7676/smp_6_": (-2) [20160523 19:06:10.193] UPnP: Device error "http://172.16.0.125:49153/setup.xml": (-2) [20160523 19:06:10.196] UPnP: Device error "http://172.16.0.150:49153/setup.xml": (-2) [20160523 19:06:10.198] UPnP: Device error "http://172.16.0.137:7676/smp_10_": (-2) [20160523 19:06:10.199] UPnP: Device error "http://172.16.0.137:7676/smp_18_": (-2) [20160523 19:06:10.219] UPnP: Device error "http://172.16.0.17:9000/NMCServerDescription.xml": (-2) [20160523 19:06:10.255] UPnP: Device error "http://172.16.0.36:80/description.xml": (-2) [20160523 19:06:10.440] UPnP: Device error "http://172.16.0.19:49153/description5.xml": (-2) [20160523 19:06:10.623] UPnP: Device error "http://172.16.0.19:49153/description6.xml": (-2) [20160523 19:06:10.851] UPnP: Device error "http://172.16.0.13:8008/ssdp/device-desc.xml": (-2) [20160523 19:06:11.703] UPnP: Device error "http://172.16.0.19:49153/description4.xml": (-2) [20160523 19:06:12.157] UPnP: Device error "http://172.16.0.17:58130/": (-2) [20160523 19:06:12.285] UPnP: Device error "http://172.16.0.53:32469/DeviceDescription.xml": (-2) [20160523 19:06:12.493] UPnP: Device error "http://172.16.0.76:8080/dd.xml": (-2) [20160523 19:06:12.889] UPnP: Device error "http://172.16.0.221:8060/": (-2) [20160523 19:06:14.892] UPnP: Could not map UPnP Port on this pass, retrying. [20160523 19:06:14.892] NAT-PMP: Unable to map port with NAT-PMP. Config { "device_name": "Chuck Berry", "listening_port" : 0, "storage_path" : "/home/pi/btsync/", "pid_file" : "/var/run/btsync/btsync.pid", "sync_trash_ttl": 3, "agree_to_EULA": "yes", "folder_rescan_interval":300, "webui" : { "listen" : "0.0.0.0:1234" }, "shared_folders" : [ { "secret" : "x", "dir" : "/home/a1", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "y", "dir" : "/home/a2/", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "z", "dir" : "/home/a3", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false }, { "secret" : "zz", "dir" : "/home/a4", "use_relay_server" : true, "use_tracker" : true, "search_lan" : true, "use_sync_trash" : true, "overwrite_changes" : false } ] } Systemd service file [Unit] Description=BitTorrent Sync service Documentation=http://help.getsync.com/ After=network.target [Service] Type=forking User=pi Group=pi UMask=0002 Restart=on-failure PermissionsStartOnly=true PIDFile=/var/run/btsync/btsync.pid ExecStartPre=/bin/mkdir -p /var/run/btsync ExecStartPre=/bin/chown -R pi:pi /var/run/btsync ExecStart=/usr/bin/btsync --config /home/pi/.config/btsync/config2.json [Install] WantedBy=multi-user.target
  2. Hi Helen, I've managed to sort it, thanks. Here are my findings for backing things up on debian / raspberry pi. Config Webui and shared folders can't work together, so you can't monitor things in the web interface. To add a shared folder, you need a key which you can generate - then just use this key on other devices. Save the config file with a unique name so it isn't automatically over-written, and make a backup of it in a completely separate folder which isn't touched. Keep it safe! To run this config using systemd, create a new service file. This is mine. Save and overwrite it in /lib/systemd/system/btsync.service [Unit] Description=BitTorrent Sync service Documentation=http://help.getsync.com/ After=network.target [Service] Type=forking User=pi Group=pi UMask=0002 Restart=on-failure PermissionsStartOnly=true PIDFile=/var/run/btsync/btsync.pid ExecStartPre=/bin/mkdir -p /var/run/btsync ExecStartPre=/bin/chown -R pi:pi /var/run/btsync ExecStart=/usr/bin/btsync --config /home/pi/.config/btsync/config2.json I'm running it as pi instead of btsync in order to preserve permissions. When you upgrade btsync, all your settings are overwritten - including /lib/systemd/system/btsync.service. So, once you've installed btsync or upgraded, run a script to restore your backups: sudo systemctl stop btsync.service sleep 2 sudo rm /lib/systemd/system/btsync.service sudo cp /home/pi/btsyncconfig/btsync.service /lib/systemd/system/btsync.service sudo systemctl daemon-reload sudo systemctl start btsync.service This will run btsync using my backed-up config and all the old shares are still there. Hope this helps someone Will
  3. Hi Roman, Thanks. Option 2 makes more sense I think. So I took a look at the config and have tried to populate "Shared folders section" without luck. I've used the key for a shared folder from another BTSync instance on another device. Is this correct? When I run BTsync, the folder isn't appearing, so I've obviously done something wrong and I'm sure it's to do with the key. The docs for shared folders in configs is a bit sparse, so would love your help if you get time Thanks Will
  4. Hi, Over the last month, I've had a lot of trouble with BTSync and had to reinstall several times. Each time I've done this, I have lost all the config options (mainly the shares). I'm now on the official debian version, but am confused which config files I should back-up. I want to get to the stage where I can install BTSync on a freshly formatted device, restore a config, and all the old settings and shares are there and working. Can anyone advise which folders and files are essential to be backed-up to make this happen? Thanks Will
  5. Hi, I was pleased to see the official Linux packages release last week, but on Debian Jessie (on a Raspberry Pi), the CPU usage is up above 100% and often 150%. It's unusable. Has anyone else seen similar or knows a way around it, or do we have to wait for the Sync team to do a fix? Thanks
  6. Hi Cipherplain. Thanks. How do you advise I install these libraries? I just ran this command, which seems to suggest quite a few are missing: ~ $ ldd /bin/lslinux-vdso.so.1 (0x7ef0d000)/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0x76f9d000)libselinux.so.1 => /lib/arm-linux-gnueabihf/libselinux.so.1 (0x76f60000)libacl.so.1 => /lib/arm-linux-gnueabihf/libacl.so.1 (0x76f49000)libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0x76e0c000)/lib/ld-linux-armhf.so.3 (0x54abd000)libpcre.so.3 => /lib/arm-linux-gnueabihf/libpcre.so.3 (0x76d99000)libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0x76d86000)libattr.so.1 => /lib/arm-linux-gnueabihf/libattr.so.1 (0x76d70000)libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0x76d48000)
  7. Hi there. Did you ever fix this? I've got exactly the same problem.
  8. It's mounted in /home/user/mount_dir/ - not /home/
  9. Update: midway through this post I tried running BT Sync as root, group btsync, and it works. I don't like it, but it works. There is some awful permission-hell happening but I hope this helps someone. Hi, I've spent four days trying to resolve this, and I really am stumped. I can't get BTSync to write to a CIFS mount which is in my home directory, and which is used by various other programs and scripts perfectly fine. What's odd is that when creating a new folder in BT Sync's Web Gui, this is created in the CIFS share correctly, but no files can be synced and it displays the error "Don't have permissions to write to selected folder". I've tried changing the mount parameters to include 0777 file_mode and dir_mode (as listed here). After chmodding 777 to the folder I've also tried, successfully, in SSH: sudo -u btsync touch boo.cBut, still, the error above persists.