Recommended Posts

When I follow the exact same procedure to do a completely new installation of Sync onto a completely new Raspbian (Jessy) installation, it works 100% fine on a Raspberry PI 2, though fails as follows on a Raspberry PI 1:

 

Setting up btsync (2.3.8-1) ...
Job for btsync.service failed. See 'systemctl status btsync.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript btsync, action "start" failed.
dpkg: error processing package btsync (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u3) ...
Errors were encountered while processing:
 btsync
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

"systemctl status btsync.service" states:

● btsync.service - BitTorrent Sync service
   Loaded: loaded (/lib/systemd/system/btsync.service; enabled)
   Active: failed (Result: start-limit) since Thu 2016-07-14 02:16:39 AEST; 10min ago
     Docs: http://help.getsync.com/
  Process: 2005 ExecStart=/usr/bin/btsync --config /etc/btsync/config.json (code=killed, signal=ILL)
  Process: 2002 ExecStartPre=/bin/chown -R btsync:btsync /var/run/btsync (code=exited, status=0/SUCCESS)
  Process: 1999 ExecStartPre=/bin/mkdir -p /var/run/btsync (code=exited, status=0/SUCCESS)

Jul 14 02:16:38 SYNC_Slave_01 systemd[1]: Unit btsync.service entered failed state.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: btsync.service holdoff time over, scheduling restart.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Stopping BitTorrent Sync service...
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Starting BitTorrent Sync service...
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: btsync.service start request repeated too quickly, refusing to start.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Failed to start BitTorrent Sync service.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Unit btsync.service entered failed state.

 

" journalctl -xn" states:

-- Logs begin at Thu 2016-07-14 01:56:34 AEST, end at Thu 2016-07-14 02:17:01 AEST. --
Jul 14 02:16:38 SYNC_Slave_01 systemd[1]: Unit btsync.service entered failed state.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: btsync.service holdoff time over, scheduling restart.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Stopping BitTorrent Sync service...
-- Subject: Unit btsync.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit btsync.service has begun shutting down.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Starting BitTorrent Sync service...
-- Subject: Unit btsync.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit btsync.service has begun starting up.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: btsync.service start request repeated too quickly, refusing to start.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Failed to start BitTorrent Sync service.
-- Subject: Unit btsync.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit btsync.service has failed.
--
-- The result is failed.
Jul 14 02:16:39 SYNC_Slave_01 systemd[1]: Unit btsync.service entered failed state.
Jul 14 02:17:01 SYNC_Slave_01 CRON[2007]: pam_unix(cron:session): session opened for user root by (uid=0)
Jul 14 02:17:01 SYNC_Slave_01 CRON[2011]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 14 02:17:01 SYNC_Slave_01 CRON[2007]: pam_unix(cron:session): session closed for user root

 

Should I remove the SD card from the PI 1 and run it on the PI 2, it works! Returning the SD card to the PI 1 and the problem persists...
 

Both PIs use each their own 5V 2A PSU, 8GB SANDISK SD Card, with 2016-03-18-raspbian-jessie-lite.img

"uname -r" on the PI 1 states: 4.4.13+
"uname -r" on the PI 2 states: 4.4.13-v7+

I'm unfortunately lost at troubleshooting this. Any aid will be greatly appreciated. Thanks

 

 

Share this post


Link to post
Share on other sites

Having a similar issue. In my case Jessie Raspbian on RPi 1 fails as well as Jessie OSMC on RPi 2

Case 1 - RPi 1 Raspbian: Tried the method 1 via official repo:

sudo sh -c 'echo "deb http://linux-packages.getsync.com/btsync/deb btsync non-free" > /etc/apt/sources.list.d/btsync.list'

wget -qO - http://linux-packages.getsync.com/btsync/key.asc | sudo apt-key add -

sudo apt-get update

sudo apt-get install btsync

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  btsync
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,506 kB of archives.
After this operation, 6,786 kB of additional disk space will be used.
Get:1 http://linux-packages.getsync.com/btsync/deb/ btsync/non-free btsync armhf 2.3.8-1 [4,506 kB]
Fetched 4,506 kB in 3s (1,465 kB/s)
Selecting previously unselected package btsync.
(Reading database ... 118183 files and directories currently installed.)
Preparing to unpack .../btsync_2.3.8-1_armhf.deb ...
Unpacking btsync (2.3.8-1) ...
Processing triggers for systemd (215-17+deb8u4) ...
Setting up btsync (2.3.8-1) ...
Job for btsync.service failed. See 'systemctl status btsync.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript btsync, action "start" failed.
dpkg: error processing package btsync (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (215-17+deb8u4) ...
Errors were encountered while processing:
 btsync
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

Case 2 - RPi 2 running OSMC: Tried the method 1 via official repo: it shows the service started ok and is running but the Web Interface from another host 192.168.x.x:8888/gui/ says "unable to connect"

Case 3 - RPi 2 running OSMC: Also tried method 2 via Rpi armhf deb link I found on this forum.

cd ~/
sudo mkdir Temp
cd Temp
sudo wget https://download-cdn.getsync.com/2.3.8/PiWD/bittorrent-sync-pi-server_2.3.8_armhf.deb
sudo dpkg –i ~/Temp/bittorrent-sync-pi-server_2.3.8_armhf.deb
sudo nano /etc/btsync/config.json
	"listen" : "INSERT_YOUR_IP_HERE:8888"

Method 2 fails to install on my OSMC due to expected "pi" user_id. I tried editing the config file but it would still fail to start.

sudo nano /etc/init.d/btsync
BTSYNC_USER=”osmc”

EDIT: I tried dpkg .deb install on Raspbian RPi1 since it has default "pi" user and it is worked. Additional step I needed was to update config.json file to listen on LAN IP and not 127.0.0.1

Share this post


Link to post
Share on other sites
16 hours ago, Skeptic said:

invoke-rc.d: initscript btsync, action "start" failed.

it installs, but fails to start. It can be either lack of RAM (the device has 512 Mb, right?) or, as @Skeptic noticed, the wrong user in startup script. 

Yes, to access UI from LAN, you need to set WEBUI to listen on 0.0.0.0:port. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.