Search the Community

Showing results for tags 'sync raspberry pi raspbian'.



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 1 result

  1. 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