Package Details: btsync 2.3.8-1

Git Clone URL: https://aur.archlinux.org/btsync.git (read-only)
Package Base: btsync
Description: BitTorrent Sync (Resilio) - automatically sync files via secure, distributed technology
Upstream URL: https://www.getsync.com
Licenses: custom:btsync
Conflicts: btsync-1.4
Submitter: ava1ar
Maintainer: ava1ar
Last Packager: ava1ar
Votes: 297
Popularity: 5.500424
First Submitted: 2013-09-17 03:06
Last Updated: 2016-06-24 23:09

Dependencies (0)

Required by (3)

Sources (5)

Latest Comments

ava1ar commented on 2016-06-24 23:11

Sorry for the delay - just updated the package to 2.3.8.
As for now, I changed the binary for armv7 arch to hf version, keeping other unchanged. Please check how it works and let me know if other updated are needed.

zifnab commented on 2016-06-21 08:59

@mad_cow:
u got me a bit wrong mate.
optimal for u, is not the RPi1 workaround, but the armv7h (hf) workaround (because currently, u are missing out on performance optimizations. I do own a cubox-ipro 4 too, just like you):

- hf devices >= armv7 (basically, ANYTHING >= armv7): they can update to latest glibc, and overwrite their btsync binary with the hf version (can now be found on official btsync website)
- non hf devices, AND hf devices <= armv6 (so basically, rpi1 and all armv5 boards): stick with glibc-2.23-1 for now (you can find how to downgrade in other posts here), and go with the btsync 2.3.7-1 package from ava1ar (which refers only to non hf for now)
(I have to say, I don't have any armv5 board, so for them, I don't have confirmation for the glibc part of the workaround...)
I am sure ava1ar will update his PKGBUILD for hf and non hf btsync binary builds for >= 2.3.7-2 (if/when it comes out).

mad_cow commented on 2016-06-21 07:19

for Cubox i4 pro; i followed instructions adapted from https://archlinuxarm.org/forum/viewtopic.php?f=60&t=10260&sid=8fa41b6eb4e2a5165148e70652010d59&start=10
(these instructions are for RPI 1)

1) downgrade glibc;
sudo pacman -U http://fraggod.net/static/mirror/packages/archlinuxarm/armv7h/glibc-2.23-1-armv7h.pkg.tar.xz
2) reinstalled btsync

bim9262 commented on 2016-06-05 15:04

(gdb) r --config .config/btsync/btsync.conf
Starting program: /usr/bin/btsync --config .config/btsync/btsync.conf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()

I'm no expert, but looking at the gdb output it looks like it fails on loading host libthread_db library "/usr/lib/libthread_db.so.1" and then fails to go any further... It doesn't look like it's executed any of the application if it is dying at 0x00000000.

BunBum commented on 2016-05-15 13:48

@broken.pipe I wrote a lot of emails with the sync support team and in the end they suggested that I should try the armhf binary from the link that I posted. Unfortunately you can't find the binary on the sync website. I suggested to update their website for that. I'm curious when / if they update it.

After all I don't understand which Arch update broke the previous binary that worked for me in the last couple of months.

zifnab commented on 2016-05-15 08:55

summary attempt:
- armv5 devices: should ALL work with "non hf" version (which is the one provided by ava1ar in package 2.3.7-1) as none of these devices does have "hf" support
- armv6 devices: only the raspberry pi 1 is supported by arch linux arm, which is a "hf" enabled device: for now, this should be the ONLY (yet widespread) device NOT working (because the hf binary seem to be compiled with armv7 as a min. requirement)
- armv7 devices (ALL are "hf" devices) and up (armv8, etc...): all should work with the alternate "hf" binary (link provided by BunBum)

anyway: it doesn't seem we are "addressing" the true root cause here, as rpi1 device used to work with all versions (tested from 2.3.1 to 2.3.6). now all (2.3.1 to 2.3.7) stopped working: so another updated package would be the true culprit here.
still, it is better for hf devices to go with the hf binary!

ava1ar commented on 2016-05-15 04:49

I use btsync only on one ARM device (which is old Marvell Kirkwood ARMv5) and have no problem with latest version. Let's summarize what we have now with ARM versions and decide what should we do with the package.

zifnab commented on 2016-05-14 21:01

thx BunBum.
- worked for armv7h (cubox-i4pro here)
- still doesn't work for armv6h (raspberry pi 1)

broken.pipe commented on 2016-05-14 10:11

@BunBum: It's probably built with a newer toolchain, this is why it stopped working under archlinux after the glibc upgrade. How did you figured it out? Thanks!

BunBum commented on 2016-05-14 07:19

I've got it! You have to download the binary from here: https://download-cdn.getsync.com/2.3.7/linux-armhf/BitTorrent-Sync_armhf.tar.gz
Then it should work on armv7 machines. I don't know if it's working on armv6. Would it be possible to update the PKGBUILD for that?

broken.pipe commented on 2016-05-10 06:49

I noticed this error on armv7h and armv6h. Take a look at my list of updated packages (http://pastebin.com/bEtPKuZc). One of them caused the failure.

Maybe this kind of error: https://forum.getsync.com/topic/42057-230-segmenation-fault-on-raspberry-pi-with-openelec/

Lulzon commented on 2016-05-09 18:52

@ava1ar I installed this on a freshly formatted raspberry pi and it occured.

Edit: I realized this comment is pointless - yesterday was a long day. You meant that maybe downgrading from 2.3.7 wasn't successful due to some cache.

BunBum commented on 2016-05-09 18:15

I believe that something was updated on the Arch Linux ARM architecture. A segmentation fault indicates that there went something wrong while allocating memory.

On my desktop machine everything works as expected, it only happens on my ARM machine (Odroid U3). So some update of the linux kernel / gcc / something else broke the btsync binary compatibility.

Note: I *believe* that's the reason but maybe I am wrong with this theory.

ava1ar commented on 2016-05-09 17:50

@BunBum did you try to clean the cache folder (or what is the name of it for btsync). Broken old version make me think that this is related to configuration/cache.

Lulzon commented on 2016-05-09 17:39

@BunBum, I did a curl GET on 2.3.6 for linux-arm. The response header came back with this, so I'm guessing previous versions weren't updated:

Last-Modified: Fri, 08 Apr 2016 18:39:58 GMT

BunBum commented on 2016-05-09 10:42

Same here. I also tired a downgrade to 2.3.6 and 2.3.5. No one is working anymore on my Odroid (armv7).

❯ btsync -h
[1] 8339 segmentation fault (core dumped) btsync -h

Did they changed the binaries for all versions?

ava1ar commented on 2016-05-09 01:01

@zifnab sounds like btsync issue? Did you check btsync forums for this issue?

zifnab commented on 2016-05-08 08:10

btsync fail to start after update to 2.3.7-1 (on armv7).
user service always worked so far, throughout all the previous versions. reboot does not help.
btsync.service: Failed with result 'core-dump' (code=dumped, status=11, signal=SEGV).

broken.pipe commented on 2016-05-07 10:27

btsync stopped working after the latest updates:
http://pastebin.com/bEtPKuZc

Error: http://pastebin.com/mdGr1yDm

noko commented on 2016-02-23 18:05

2.3.3 is out

fryfrog commented on 2016-02-22 17:35

Looks like they've got official rpm and deb packages available now. Is that useful in anyway? I'm guessing not.

https://blog.getsync.com/2016/02/18/official-linux-packages-for-sync-now-available/

tuxflo commented on 2016-02-19 15:07

@flow why not just markt it out of date? That is why this flag exists...

flow commented on 2016-02-19 10:09

2.3.2
https://forum.getsync.com/topic/42172-latest-desktop-build-232/

flow commented on 2016-02-03 23:18

2.3.1
http://forum.getsync.com/topic/42083-latest-desktop-build-231/

ava1ar commented on 2016-01-22 02:39

Updated to 2.3.0

ava1ar commented on 2015-11-23 00:45

Updated to 2.2.7.
btsync-autoconfig no longer exists? I removed the opt dependency from it.

fryfrog commented on 2015-10-12 05:10

And a git format-patch for 2.2.5, maybe saves someone some time?

https://ptpb.pw/GiS1

fryfrog commented on 2015-10-02 20:03

And here is a git format-patch for 2.2.2, hopefully it saves someone some time.

https://ptpb.pw/ZKbg

fryfrog commented on 2015-09-23 02:19

Here is a git format-patch to update to 2.2.1, if it saves you any time. I just downloaded the files and sha1sum'd them.

https://ptpb.pw/kPat

akurei commented on 2015-09-21 09:39

Great! Thank you!
(And sorry I just noticed the patch was reversed.)

ava1ar commented on 2015-09-20 04:40

akurei,
thanks, requested change committed.

akurei commented on 2015-09-20 02:29

Hey ava1ar, could you please accept my patch for the PKGBUILD?
https://gist.github.com/anonymous/2f7e1f77252836c03c1c

Now when I do

$ makepkg -scf
==> Making package: btsync 2.2.0-1 (Sun Sep 20 04:20:04 CEST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found btsync.service
-> Found btsync_user.service
-> Found btsync.conf
-> Found BitTorrent-Sync_x64.tar.gz
==> Validating source files with sha1sums...
btsync.service ... Passed
btsync_user.service ... Passed
btsync.conf ... Passed
==> Validating source files with sha1sums...
BitTorrent-Sync_x64.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

Is says that one file did not pass the checksum test. That is because the PKGBUILD in its current form does not differentiate the downloads between versions. My patch names the download according to the version and pkgrel. The result is that it builds even with old versions of the source archive present:

$ makepkg -scf
==> Making package: btsync 2.2.0-1 (Sun Sep 20 04:27:58 CEST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found btsync.service
-> Found btsync_user.service
-> Found btsync.conf
-> Found BitTorrent-Sync_x64-2.2.0-1.tar.gz
==> Validating source files with sha1sums...
btsync.service ... Passed
btsync_user.service ... Passed
btsync.conf ... Passed
==> Validating source files with sha1sums...
BitTorrent-Sync_x64-2.2.0-1.tar.gz ... Passed
==> Extracting sources...
-> Extracting BitTorrent-Sync_x64-2.2.0-1.tar.gz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Purging unwanted files...
-> Removing libtool files...
-> Removing static library files...
-> Compressing man and info pages...
==> Creating package "btsync"...
-> Generating .PKGINFO file...
-> Adding install file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: btsync 2.2.0-1 (Sun Sep 20 04:27:59 CEST 2015)
==> Cleaning up...

ava1ar commented on 2015-08-18 04:30

Thanks, I updated the URLs

zpAUHlWLSNdNqVSU commented on 2015-08-16 11:40

For reference, if you use the domain `getsync.com` rather than `getsyncapp.com` you won't get the HTTPs errors and you can drop the `-k` from cURL.

zpAUHlWLSNdNqVSU commented on 2015-08-16 11:40

For reference, if you use the domain `getsync.com` rather than `getsyncapp.com` you won't get the HTTPs errors.

marcn commented on 2015-08-13 22:31

Is it possible, that the x86_64 file was changed by bittorrent? I got an other sha1sum: 0552a2afee08b832bc74bf9ed26757120c07dc3c

cmorgenstern commented on 2015-08-11 14:17

Ditto. Asked about it upstream (http://forum.bittorrent.com/topic/28106-linux-desktop-gui-unofficial-packages-for-bittorrent-sync/?p=109288) but no response yet.

Also, anyone know whether btsync-gui is going to be migrated to the new AUR setup?

cmorgenstern commented on 2015-08-11 14:16

Ditto. Asked about it upstream (http://forum.bittorrent.com/topic/28106-linux-desktop-gui-unofficial-packages-for-bittorrent-sync/?p=109288) but no response yet.

tuxflo commented on 2015-07-27 21:19

Getting the "i_agree" errors here too. Trying to setup btsync-gui. 1.4 works without any problems.

PhotonX commented on 2015-07-26 09:48

Getting many of

Error while parsing config file: Invalid key 'i_agree'WARNING:root:BitTorrent Sync seems to be crashed. Restarting...

after some of the recent updates, any thoughts?

CyberGhost commented on 2015-05-26 22:26

I found the problem. I did use the btsync-autoconfig package, to initially configure it however I made a typo on the storage_path key in the config file. This broke the program.

ava1ar commented on 2015-05-26 03:25

CyberGhost,

did you read and follow the postinstall steps printed after package install/update? User service for btsync is not automatically configured after installation and require manual adjustments of the configuration files and creation of required directories. If you want it to work out of the box, please take a look at btsync-autoconfig.

CyberGhost commented on 2015-05-25 21:01

Whenever I try to start the btsync user service it fails to start.
The output from "systemctl --user status btsync" is always:
"btsync.service - Bittorent Sync per-user service
Loaded: loaded (/usr/lib/systemd/user/btsync.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Mon 2015-05-25 16:50:27 EDT; 13s ago
Process: 809 ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf (code=dumped, signal=ABRT)

May 25 16:50:26 Arch systemd[384]: Starting Bittorent Sync per-user service...
May 25 16:50:27 Arch systemd[384]: btsync.service: control process exited, code=dumped status=6
May 25 16:50:27 Arch systemd[384]: Failed to start Bittorent Sync per-user service.
May 25 16:50:27 Arch systemd[384]: Unit btsync.service entered failed state.
May 25 16:50:27 Arch systemd[384]: btsync.service failed."

Anybody else have this issue and if so does anybody have a fix?

ava1ar commented on 2015-05-16 00:25

leidola,

As far as I see here http://www.freedesktop.org/software/systemd/man/systemd.exec.html WorkingDirectory is set by default to the respective user's home directory for user units. No need to duplicate it.

leidola commented on 2015-05-14 14:02

Please add:

WorkingDirectory=%h

to the service part of the user unit. Otherwise the default config (as generated by btsync --dump-sample-config won't work, as by default btsync tries to generate the PID files in a path relative to the working directory.

fazky commented on 2015-04-17 23:28

Same here, syncing is not working on Raspberry Pi.

PythonNut commented on 2015-04-13 18:11

I keep getting these in sync.log:

20150413 18:05:23.676] assert failed /mnt/jenkins/workspace/Build-Sync-ARM/network.cpp:3279

Does this look familiar at all?

So far, syncing seems to be stalled on an Raspberry Pi 2.

zatricky commented on 2015-03-31 08:58

Not sure what the problem was ... working now. :-/
Thanks, ava1ar.

ava1ar commented on 2015-03-31 00:42

Works for me, unflagging.

zatricky commented on 2015-03-24 07:52

Seems it has changed again:
==> Validating source files with sha1sums...
BitTorrent-Sync_x64.tar.gz ... FAILED

ava1ar commented on 2015-03-21 03:58

lybin, please try again now

lybin commented on 2015-03-21 03:55

==> Validating source files with sha1sums...
BitTorrent-Sync_x64.tar.gz ... FAILED

fattoony commented on 2015-03-09 14:58

Zifnab, you sir are a gent

"loginctl enable-linger username" worked a treat.

Have been trying to sort this for such a long time, you guys was my last option!
Thanks also to starquake & a big thanks to the maintainer ava1ar.

Regards,

zifnab commented on 2015-03-09 14:29

@ava1ar: thx, works great here too, as reported by frol.

zifnab commented on 2015-03-09 08:57

@fattoony:
with your symptoms, I guess it is one of two things (the latter being probably the good one):
- either you start it manually via ssh, rather than using a service (enable, start...)
- either you use a "user" service, and then you need to enable "lingering" (search for this word here, and you should be set: https://wiki.archlinux.org/index.php/Systemd/User ).

starquake commented on 2015-03-09 08:05

@fattoony

What command do you use to start BTSync? Are you running it as a daemon?

You can find more info here: https://wiki.archlinux.org/index.php/BitTorrent_Sync

frol commented on 2015-03-09 07:58

@ava1ar Thank you! It works like a charm.

fattoony commented on 2015-03-08 23:31

Hi apologies if this is not the place to be asking this question but i am all out of
ideas & getting no help from the btsync forum.

The problem is BTSync will only sync with active ssh connection (ArchLinux)

I have setup some shares in BTSync 2.x & every thing is syncing fine & i can connect via the web ui.
Once i disconnect ssh from the archlinux box, the sync stops also the web ui also stops working.

I have the same setup working fine on Openelec.

I âm using upnp on all nodes & upnp is enabled on my router. i have tried specifying a listening port & forwarding in on the router, this has no affect. I have also tried deactivating the firewall on the router also with no affect.

I should say I was also having this problem on 1.4.x before i upgraded to 2.0.x

I would really appreciate it if you can offer some ideas.


Regards,

fattoony commented on 2015-03-08 23:09

Was Having same problem as frol, zifnab on cubox-i4pro ARMv7
Can confirm.. Last Updated @ 2015-03-08 22:58 worked fine for me.

Regards,

ava1ar commented on 2015-03-08 22:59

frol, zifnab

please check now - I fixed misprints in PKGBUILD.

zifnab commented on 2015-03-08 22:37

same error as frol here (armv7 too: cubox-i4pro device).

frol commented on 2015-03-08 09:31

I forgot to mention that I run ARMv7 Arch (Odroid U3).

frol commented on 2015-03-08 09:28

I have an error during update from 2.0.81-1 to 2.0.85-1:
install: cannot stat ‘/tmp/yaourt-tmp-frol/aur-btsync/src/btsync’: No such file or directory

Here is a full log:

==> Building and installing package
==> Making package: btsync 2.0.85-1 (Sun Mar 8 01:25:30 PST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found btsync.service
-> Found btsync_user.service
-> Found btsync.conf
==> Validating source files with sha1sums...
btsync.service ... Passed
btsync_user.service ... Passed
btsync.conf ... Passed
==> Extracting sources...
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat ‘/tmp/yaourt-tmp-frol/aur-btsync/src/btsync’: No such file or directory
==> ERROR: A failure occurred in package().

ava1ar commented on 2015-03-07 19:04

Updated. Please check if it is working good. I had to change the download links, since old location is not updated as fast as official mirror.

zifnab commented on 2015-03-07 18:55

2.0.85 out (for all platforms. pushed out kinda silently...).
thx a lot for all your hardwork and cautious approach in dealing with the change from 1.4.x to 2.0.x... (I do think 2.x is able to do for free everything that 1.4 was doing, but the limit to 10 folders might prove an issue for some at some point. unfortunately, last time I tried the competition (syncthing), transfer speeds were nowhere close from btsync...).

zifnab commented on 2015-03-07 18:50

2.0.85 out (for all platforms).

fjim commented on 2015-03-06 13:24

In case any suffers the same:

http://forum.bittorrent.com/topic/34409-btsync-20-core-dumps-in-some-linux-x86-64-computers/

fjim commented on 2015-03-06 09:33

It's core dumping in 2 out of 3 x86_64 machines for me. All three are up to date, so I suspect it might have to do with illegal instructions.

Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz: works
Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz: cores
Intel(R) Celeron(R) CPU 1007U @ 1.50GHz: cores

Is it happening to anyone else?

ava1ar commented on 2015-03-05 01:44

Updated to 2.0.81. For 1.4.111 version, please use btsync-1.4 package.

duch commented on 2015-03-04 22:08

Latest version of the 1.4 branch (1.4.111) will probably also be the last.

ava1ar commented on 2015-03-04 19:39

Thanks everybody for the comments.
I am planing to update this package to the version 2.0, however I'll upload version 1.4 as btsync-1.4 for those who are going to continue use of old version.

vladthedog commented on 2015-03-04 19:06

I don't believe 1.4 will ever stop working; it just won't be able to talk with v2 and above clients. They have explicitly stated it's always been built from the ground up not to need any sort of centralized server, nor was there a need to upgrade once the official commercial release came out. My vote would be to keep two packages (mark this legacy or some such and create a new version?). I doubt there will be many/if any upgrades to 1.4 so it will just sit there.

mart-e commented on 2015-03-04 15:41

Version 2 introduces a big restriction: maximum 10 synced folders for free users!
It's ok for me but many people on bittorrent forums are asking how to downgrade.
I expect 1.4 not to be maintained anymore.
So I would say upgrade this one to 2.0 but making a package btsync-1 may interest some people (not sure if you can share folders under 1.4 with devices with 2.0)

auberginepop commented on 2015-03-04 15:32

Version 2 looks good though and any new features that come out will only go into 2.

Why wait to upgrade?

lockheed commented on 2015-03-04 15:10

@auberginepop, you can install 1.4 apk downloaded from the internet manually and disconnect it from Android Market. This way it will always stay intact even with automatic updates on. I just did it myself. There is neither point nor necessity to going to v2. At least for the moment.

auberginepop commented on 2015-03-04 13:08

The btsync app on my Android phone has automatically updated to version 2 so I have no choice to upgrade to this version on all my other devices as and when it is available.

Now 2 is out I suspect v1.4 will be dropped pretty soon anyway.

starquake commented on 2015-03-04 11:41

I am thinking of switching to some other solution. Syncthing is looking nice lately and they say it's stable and also ownCloud might be a good solution for me. Not te same as btsync though.

Will report back if I made up my mind.

ava1ar commented on 2015-03-04 11:31

Any thoughts about what we should do with this package? Version 2.0 is out, but now this is a free version of the commercial product. Should we keep this package as i.e. btsync1 and create PKGBUILD for version 2 as btsync? Anybody plans to continue using 1.4?
Let's wait couple of days to understand the future of 1.4 version - if it will stop working in the future, this package will be updated to version 2. If no, separate PKGBUILD will be created for version 2 and version 1 will be also available in the repository as i.e. btsync1.
Comments?

bse commented on 2015-02-20 10:10

@aminzai: Please read https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

@threepointtwo: The PKGBUILD uses "./btsync --dump-sample-config" - so its using the newly extracted binary. /etc/btsync.conf is generated fine this way.

threepointtwo commented on 2015-02-19 16:15

the PKGBUILD uses the "btsync --dump-sample-config" command to create /etc/btsync.conf. this makes no sense as someone installing for the first time will not have the btsync command on their system. it created an empty config file for me and the service wouldn't start until i created a valid config.

aminzai commented on 2015-02-05 13:43

Hi:
I found a lost require package "binutils" and "fakeroot" :)

aminzai commented on 2015-02-05 13:42

Hi:
I found a lost require package "binutils" :)

ava1ar commented on 2015-01-14 00:54

Updated to 1.4.106

ava1ar commented on 2014-12-31 20:48

truh

This PKGBUILD is using new syntax, introduced in pacman 4.2. Sorry, but you won't be able to use this script with Manjaro till they update to new pacman release.

truh commented on 2014-12-31 20:44

What is pacman>=4.2 needed for?

Looks like Manjaro has not updated pacman to this version yet.

==> Install or build missing dependencies for btsync:
[sudo] password for jakob:
error: target not found: pacman>=4.2

Anyway, thanks for maintaining.

ava1ar commented on 2014-12-31 20:39

I made some cosmetic changes to the package function and added temporary makedepends=('pacman>=4.2') to force people use of new pacman to ensure proper build.

Please report if you still having issues with building/installing this package.

bryanchuckles commented on 2014-12-31 19:04

makepkg fails. The way PKGBUILD is written, it doesn't download the files from bittorrent.com

caemir commented on 2014-12-31 12:55

→ ERROR: btsync is not available for the 'armv7h' architecture.
Note that many packages may need a line added to their PKGBUILD
such as arch=('armv7h').

← arch=('i686' 'x86_64' 'armv7h')

→ install: cannot stat ‘btsync’: No such file or directory

caemir commented on 2014-12-31 12:54

→ ERROR: btsync is not available for the 'armv7h' architecture.
Note that many packages may need a line added to their PKGBUILD
such as arch=('armv7h').

i do it

$ arch=('i686' 'x86_64' 'armv7h')

→ install: cannot stat ‘btsync’: No such file or directory

caemir commented on 2014-12-31 12:53

==> ERROR: btsync is not available for the 'armv7h' architecture.
Note that many packages may need a line added to their PKGBUILD
such as arch=('armv7h').
==> ERROR: Makepkg was unable to build btsync.

gatonero commented on 2014-12-31 11:42

When updating btsync I got following error:
==> Starting package()...
install: cannot stat ‘btsync’: No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
==> ERROR: Makepkg was unable to build btsync.

lockheed commented on 2014-12-31 07:13

Well, arm6h is the absolute most-have as AFAIK it is the most widely used here because of RaspberryPi.

ava1ar commented on 2014-12-31 04:58

I cleaned up some arm architectures and left only arm for now, since I am not sure which of them are really used. Please report missing arm architectures and hardware and I will add them back individually.

joko commented on 2014-12-15 16:35

@asaaki: apparently that was the case:

% groups
wheel users joko

My main user belongs to the wheel group. Running btsync as the btsync user works.

Brawl commented on 2014-12-15 14:46

I can't start btsync anymore.
systemctl --user status btsync returns
Failed to get D-Bus connection: File or Directory not found
(translated)

It worked a few days ago oO

asaaki commented on 2014-12-15 13:55

@joko: Looks like you try to start it as a root-ish user. You should always start it as your own user, then it will create the `.sync` folder in your home directory.

joko commented on 2014-12-15 12:14

Hello,

I have just installed btsync 1.4.103-1 and I cannot make it work. Even with the dummy config file and by running it directly from the command line it is not working.

strace reports that it tries to access and create the directory /usr/bin/.sync and it is missing obviously permissions, so this might be the problem here. Is there any workaround?

DepthDeluxe commented on 2014-11-23 16:02

@ava1ar,

Could you include a reference in your install information to enabling user lingering? Just spent a decent amount of time debugging btsync stopping on logout until I found this. Basically if you want btsync to keep running after you lot out, you have to tell systemd to let you via "loginctl enable-linger $USERNAME"

See this: https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances

lockheed commented on 2014-11-13 07:58

@ava1ar,

This is a problem with systemd 218 - it is not possible to run user instances of systemd. I downgraded to 217 and everything works fine, but obviously I need to find a solution to fix it, unless its a bug in 218.

ava1ar commented on 2014-11-13 04:49

@lockheed

Can you run following command and paste it's output:

systemctl --user status btsync

?

lockheed commented on 2014-11-12 14:34

Since today's update, btsync no longer starts and when I try to run manually, I get:

$ systemctl --user start btsync
Failed to start btsync.service: Process org.freedesktop.systemd1 exited with status 1

ava1ar commented on 2014-11-12 04:07

Updated to 1.4.103

ava1ar commented on 2014-11-12 04:02

@mkaito

Logs are written to the sync.log, which is located in the btsync config folder. If you are using btsync in system mode, the file location is /var/lib/btsync/sync.log; if you are using user instance, log file is here: ~/.config/btsync/sync.log

mkaito commented on 2014-11-12 01:31

Well, the process is dying. Systemd doesn't try to restart it, and there is nothing of value in any logs I've seen. Let's see what 1.4.103 does about that.

Mutantx commented on 2014-11-11 22:42

mkaito - a new version (1.4.103)has released which may resolve whatever bugs your trying to log. Would probably be worth waiting for this to be release here IMO.

mkaito commented on 2014-11-11 16:06

So where is it logging to? I can't see anything in /var/log or in the journal.

Mutantx commented on 2014-10-31 14:26

New version 1.4.99 has been released and is supposed to address several key issues that arose in this version.

Cross your fingers!

kmindi commented on 2014-10-13 14:35

the current file location does not exsist anymore (http://syncapp.bittorrent.com/1.4.83/btsync_-1.4.83.tar.gz)

I think it should now be one of:
- http://download-new.utorrent.com/endpoint/btsync/os/linux-x64/track/stable
- http://download-new.utorrent.com/endpoint/btsync/os/linux-glibc23-x64/track/stable

see alternate download page: http://www.bittorrent.com/intl/de/sync/download

ava1ar commented on 2014-09-19 14:32

@justin8

If you read previous comnment, you will find out that --nodaemon option was there previously and btsync output was written to the journal. But since there are no way to set logging level, lot of people (I believe with log of shares and syncing activity) were reporting btsync produces too much output and overfilling the journal file. I tried to find a way to make logging less verbose, but did not find any, so I just using separate log file now.

If you know how to configure logging level for btsync please let us know I will consider using --nodaemon option again.

justin8 commented on 2014-09-19 13:25

Hi,

Would it be possible to add --nodaemon to the service file? this way it will actually generate log output in the journal. (and change type to be simple obviously)

hendry commented on 2014-09-19 07:07

This morning I found moving stuff from ~/.config/btsync/ to /var/lib/btsync/ fixed things except my iphone's camera roll backup is still now working.

I reset the key, but not btsync uses this strange getsync URL which invokes xdg-open which then launches Firefox and doesn't work.

http://s.natalian.org/2014-09-19/1411110287_1364x748.png

Any ideas?

timski commented on 2014-09-19 03:40

@ava1ar

I helped myself with a cronjob an a bashscript, starting btsync, if it's not running. No beauty, but does the trick.

ava1ar commented on 2014-09-19 02:19

@timski

Thanks! Looks like this is bug in v1.4. You can always switch to 1.3 while it is not fixed in never versions.

timski commented on 2014-09-19 01:19

@ava1ar

I removed all configuration files, also the default one, deleted btsync completely und reinstalled it.

Then I switched to lingering to start btsync at boot.

It worked find with no shares added, but after adding my folders, the same as before(crashing after ca 1/2 min). So I guess it's because of to many files to sync/index. But it worked on 1.3.x, so it might work again.

But running it via lingering is nice, works like a charm for deluged

ava1ar commented on 2014-09-18 19:04

@timski

Do not forget to share your experience with lingering and btsync, other users may find it useful.

timski commented on 2014-09-18 19:00

I will try lingering, that's sounds like what I want

thanks alot for your time!

and also thank you very much for maintaning the btsync package :)

ava1ar commented on 2014-09-18 14:52

@timski

Technically, user instance of btsync starts on user login, not at system start (unless you enable lingering https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances).
To troubleshoot the user instance can you please do the following:

1. Remove/rename btsync user configuration dir:
~/.config/btsync
2. Copy /etc/btsync/btsync.conf to ~/.config/btsync/btsync.conf:
mkdir -p ~/.config/btsync
cp /etc/btsync.conf ~/.config/btsync/btsync.conf
3. Replace user-specific references with the appropriate information. For now
storage_path and pid_file are enough. Be sure to specify existing and accessible path.

Than reload systemd user isntances and start the btsync:
systemctl --user daemon-reload
systemctl --user start btsync

Then post here the errors you will see in the journal.

timski commented on 2014-09-18 13:18

I tried now, but I'm not able do get a functioning init script to start btsync as a user anymore.

The standart btsync.service and I can start it manually as a user, but not via systemd at boot

I also upgraded to 1.4.82

ava1ar commented on 2014-09-18 03:25

@timski

Did you try creating clean configuration and re-adding your shares? I wonder if your problem will still persist.

timski commented on 2014-09-17 01:04

Here, that should be the startup log part:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[19700101 01:00:21.792] total physical memory -1 max disk cache 2097152
[19700101 01:00:21.879] Unable to listen for HTTP traffic on port 8880. Exiting...
[19700101 01:00:21.999] Loading config file version 1.4.75
[19700101 01:00:34.224] Using IP address 192.168.178.20
[19700101 01:00:35.401] UPnP: Device error "http://192.168.178.1:49000/MediaServerDevDesc.xml": (-2)
[19700101 01:00:35.403] UPnP: Device error "http://192.168.178.1:49000/l2tpv3.xml": (-2)
[19700101 01:00:42.092] SF[AE98]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:56.250] SF[0D7F]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:56.433] SF[C017]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:56.675] SF[F79D]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:58.523] SF[D1A5]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:59.570] SF[4D85]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:00:59.781] SF[DD15]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:01.372] SF[449F]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:05.393] SF[C540]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:21.485] SF[6B7E]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:23.131] SF[53CE]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:23.427] SF[5ED7]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:23.494] SF[8ECB]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:29.232] SF[535F]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:29.860] SF[D2FF]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:29.981] SF[2F0D]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:30.054] SF[3E99]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:30.105] SF[51AB]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:30.152] SF[9678]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:31.875] SF[C4B5]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:31.949] SF[8D7D]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:32.005] SF[B9A3]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:32.051] SF[BD87]: Loaded folder /mnt/extdisk0/btsync/#######
[19700101 01:01:35.393] SyncEncryptHandler: bad shareID (STATE_BEGIN)
[19700101 01:01:37.451] Shutdown. Saving config sync.dat
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
could be the problem, that the time isn't synced at this point?

ava1ar commented on 2014-09-15 01:14

@timski

Any logs / stacktrace / other artifacts. It is really difficult to troubleshoot the problem just by generic description.

timski commented on 2014-09-14 23:16

since the upgrade to 1.4.x btsync crashes after starting at boot on my raspberry pi. I run it as a user, not as root, by a systemd btsync@.service as it were a few versions ago.

could not find any hint about what's going wrong,

if I start it with
systemctl --user start btsync
it does not crash

any ideas?

timski commented on 2014-09-14 23:14

since the upgrade to 1.4.x btsync crashes after starting at boot on my raspberry pi. I run it as a user, not as root, by a systemd btsync@.service as it were a few versions ago.

could not find any hint what going wrong,

if I start it with
systemctl --user start btsync
it does not crash

any ideas?

timski commented on 2014-09-14 23:14

since the upgrade to 1.4.x btsync crashes after starting on boot on my raspberry pi. I run it as a user, not as root, by a systemd btsync@.service as it were a few versions ago.

could not find any hint what going wrong,

if I start it with
systemctl --user start btsync
it does not crash

any ideas?

timski commented on 2014-09-14 22:31

since the upgrade to 1.4.x btsync crashes after starting on boot. I run it as a user, not as root, by a systemd btsync@.service as it were a few versions ago.

could not find any hint what going wrong,

if I start it with
systemctl --user start btsync
it does not crash

any ideas?

ava1ar commented on 2014-09-08 20:11

@lockheed

You should adjust owner and permission for the folder you want to sync. btsync system instance is running using dedicated btsync:btsync user, so just make sure btsync user or btsync group have write permission in the folder you want to sync.

lockheed commented on 2014-09-08 18:45

@ava1ar,
Thank you. The service now start correctly. However, when I try to assign a data folder populated by a previous btsync installation, I get this:

"Don't have permissions to write to selected folder."

That old instance of btsync was run at boot time from root crontab with command:
/usr/bin/btsync --config /home/malina/.config/btsync/btsync.conf --nodaemon


What should I do now to make it work with the new btsync instance?

ava1ar commented on 2014-09-08 15:49

@lockheed

Just install updated package and execute following commands:

sudo systemctl daemon-reload
sudo systemctl start btsync

This will start the system instance. Now you can navigate to http://localhost:8888 and start using btsync.

ava1ar commented on 2014-09-08 15:24

Just uploaded update. Changes are:

- using direct links for btsync binaries;
- changes in system config autogeneration
- adding tmpfiles.d config to automatically create directories for pid

Now system btsync instance should start and work correctly directly out of the box.

@lockheed

Can you please try again with system instance?

snv commented on 2014-09-08 14:16

Static links can be found like this: http://syncapp.bittorrent.com/1.4.75

Using those would avoid PKGbuilds which break, because checksums stop matching

lockheed commented on 2014-09-08 14:10

@ava1ar,

Al-right, but in no way does it change the issue. I want to run it as system user, but I can't run it as root, I can't run it as user, and I can't run it as user with sudo.

ava1ar commented on 2014-09-08 13:04

@lockheed

There is no option to run btsync as root. You can chose from 2 options: running system instance as dedicated btsync user or running per-user instance with user-specific configuration. Per-user instance requires either manual configuration before use or installing btsync-autoconfig package to create initial configuration automatically. Please read package post-install/post-upgrade instructions for details.

lockheed commented on 2014-09-08 10:58

I can't get btsync to run. I install it from scratch, and as I want to run it as root user, I don't edit the /etc/btsync.conf

But when I try to run the service, I get:
Can't open pid file /usr/bin/.sync//sync.pid. Permission denied

Why?

ava1ar commented on 2014-09-05 20:00

@rollhax

Thanks for digging into this and sharing your findings - they may be really useful for other people using btsync from AUR. Personally I did not face any issues (may be because I am not using password on my btsync isntances). I will update post_install instructions with link to the forum thread on mentioned in case somebody else will face same issues.

P.S. Damn EULA! Why not just share code under GPL and forget about that crap.

rollhax commented on 2014-09-05 18:55

I managed to get it working. My steps:

pacman -R btsync
rm -rf /var/lib/btsync (and other btsync-related files/dirs)
Download btsync from getsync.com
Run btsync withOUT a config file, get it setup
Stop btsync, re-run with my config file, profit
(I then wrote a systemd service config)

This is apparently a somewhat known issue in the community. See one of the comments on http://forum.bittorrent.com/topic/31476-btsync-on-linux-not-saving-settings-other-issues/ for another possible fix.

rollhax commented on 2014-09-05 13:09

@ava1ar

The arch installation is pretty new/mostly up-to-date. Nothing special about it, and I'm experiencing the issue on 3 separate arch installs, all of varying age/updatedness. No problems to speak of, one box (the one I managed to get it kind-of working on for a day or two) hasn't been updated in months, the others are kept pretty up-to-date.

I'll keep kicking at it. I have a support ticket in to bittorrent inc, as well as a forum post: http://forum.bittorrent.com/topic/31476-btsync-on-linux-not-saving-settings-other-issues/

ava1ar commented on 2014-09-05 02:57

@rollhax

Issues with the post_upgrade its my fault - I already re-uploaded PKGBUILD with fix applied.

What about issues with btsync itself - it is strange, I did not see anything similar. I have no clue what may cause this. Do you have updated arch installation? Anything specific with it? Did you see similar problems with other applications?

rollhax commented on 2014-09-05 02:03

post_upgrade directions are not showing. For me, it just prints the words "post_upgrade" (but I can see it if I edit btsync.install).

Also, after setup, when I try to log into the webgui, I get a bunch of http status 500 errors with the following response string:

"Need to agree with the license"

Any ideas? To be clear, I am clicking the "I agree" checkbox when creating my user (although it's odd, because I have a user/password set in my btsync.conf file, which is as follows):

{
"device_name": "btsync",
"listening_port" : 0, // 0 - randomize port

"storage_path" : "/home/dusty/.config/btsync",
"pid_file" : "/home/dusty/.config/btsync/btsync.pid",

"use_upnp" : false,

"download_limit" : 0,
"upload_limit" : 0,

"webui" :
{
"listen" : "0.0.0.0:8888" // remove field to disable WebUI
,"login" : "dusty"
//,"password" : "password"
,"password_hash" : "obfuscated" // password hash in crypt(3) format
//,allow_empty_password" : false // Defaults to true
//,"directory_root" : "/home/dusty"
}
}

rollhax commented on 2014-09-05 02:02

post_upgrade directions are not showing. For me, it just prints the words "post_upgrade" (but I can see it if I edit btsync.install).

Also, after setup, when I try to log into the webgui, I get a bunch of http status 500 errors with the following response string:

"Need to agree with the license"

Any ideas?

ava1ar commented on 2014-09-04 03:23

@JibbsIsMe

It will be created after you start the btsync and deleted after it stopped. You don't need to do anything related to pid, except specifying its location in btsync.conf.

JibbsIsMe commented on 2014-09-04 03:22

I have no btsync.pid in my /.config folder, should I just copy the other one over?

ava1ar commented on 2014-09-03 05:32

@JibbsIsMe
Here is configuration file I am using (located at ~/.config/btsync/btsync.conf)

{
"device_name": "ava1ar-laptop",
"listening_port" : 0,
"storage_path" : "/home/ava1ar/.config/btsync",
"pid_file" : "/home/ava1ar/.config/btsync/btsync.pid",
"check_for_updates" : false,
"use_upnp" : true,
"download_limit" : 0,
"upload_limit" : 0,
"webui" :
{
"listen" : "0.0.0.0:7777"
"login" : "admin",
"password" : "password"
}
}

JibbsIsMe commented on 2014-09-03 05:21

When I had those problems earlier, I had btsync-autoconfig installed. I uninstalled everything and and now reinstalling, but what should I set the "pid_file" to if I'm running as a user? "/usr/bin/.sync/sync.pid" throws a permission error.

ava1ar commented on 2014-09-03 02:30

Updated to 1.4.75

@JamieKitson
You might need to add you shares from scratch :(

JamieKitson commented on 2014-09-02 17:35

When I try to access the API, eg, http://localhost:8888/api?method=get_folders, I get "invalid request", does the api need to be enabled/installed separately?

JamieKitson commented on 2014-09-02 17:20

After upgrading to 1.4 from 1.3 my shares are no longer displaying. I noticed the note about not being able to downgrade, but do I have to do anything to upgrade?

ava1ar commented on 2014-09-02 14:10

@snv

I will update the package soon. What about direct links - I also prefer them, but they are usually not available right after new version release and appearing with delay. Do you have direct links for the latest version?

snv commented on 2014-09-02 14:05

sha1sum should be 'b0bd808f8ad3901909ac63fbcf30169c2e396957' for linux x64 v1.4.75

using static links would be better

flexiondotorg commented on 2014-09-02 10:45

Hashes do not match.

ava1ar commented on 2014-08-30 02:26

I updated post-install instructions to clearly describe requirement in configuration either by installing btsync-autoconfig or following manual steps.

ava1ar commented on 2014-08-30 02:09

@JibbsIsMe

Did you follow the instructions displayed after package installation? Looks like not. If you want to user btsync user service, you should either configure it manually or use btsync-autoconfig package.

Here are manual instructions, which are displayed after installation:

User-specific BTSync configuration

Copy /etc/btsync/btsync.conf to ~/.config/btsync/btsync.conf for the user you wish to configure btsync as:

mkdir -p ~/.config/btsync
cp /etc/btsync.conf ~/.config/btsync/btsync.conf

Replace user-specific references with the appropriate information, including the following settings:
- storage_path
- pid_file
- webui.listen
- webui.login
- webui.password

Make sure folder you specified as storage_path and folder where pid_file will be located both exist in the filesystem, since btsync will not create it for you.

JibbsIsMe commented on 2014-08-30 02:04

After a fresh install, I had the error "Can't open pid file /sync.pid. Permission denied" when running "systemctl --user start btsync".

"journalctl -xn" didn't provide enough info, so I ran "/usr/bin/btsync --config ~/.config/btsync/btsync.conf --nodaemon" and it showed me specifically where the .pid file was: "/usr/bin/.sync/sync.pid".

So I fixed it by running "sudo chmod 777 /usr/bin/.sync/sync.pid" and now everything works.

ava1ar commented on 2014-08-26 20:06

Updated to 1.4.72. Please note: downgrade to 1.3 is not possible after installing Sync 1.4! If you want to downgrade - please uninstall Sync with removing all settings, then install 1.3 and configure all folders from scratch.

vaski commented on 2014-08-18 13:13

@emlun Thanks, this did the trick.
@ava1ar Adding btsync to group users did not work, btsync would not start, complained about root folder

emlun commented on 2014-08-16 08:04

@vaski Or, if all else fails, you could modify the service by copying /usr/lib/systemd/system/btsync.service to /etc/systemd/system/btsync.service and change the User= setting to whatever user you need, and # systemctl daemon-reload. Service files in /etc override ones in /usr/lib.

ava1ar commented on 2014-08-16 04:10

@vaski

Nothing to prevents you to add btsync to users group and give the group proper permissions for folders your are syncing in the /home/someusername. The only difference between 2 service files for btsync is that one is started by system instance of systemd and another by user instance. Seconds service works great for PC you are logging in, first for headless servers where no login normally performed at all.

vaski commented on 2014-08-15 23:34

@ava1ar
Thanks, but I need to be able to sync folders in /home/someusername, and I ran into problems trying that using btsync.service

ava1ar commented on 2014-08-15 16:09

@vaski

On headless server you can use btsync.service instead of user instance. It is running on separate user and does not depend on user login.

emlun commented on 2014-08-15 12:04

@vaski You could try enabling lingering [1]. Disclaimer: I'm not a systemd expert, most of what I know about how to get these things working comes from reading the wiki. :P

[1]: https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances

vaski commented on 2014-08-15 12:00

@emlun, ahh you are right, when I install btsync on my desktop pc everything is working, but not on my headless server (where I got the failed d-bus connection). I don't login to the server, only access it with ssh so Systemd user instance does not start automatically, can I start it through ssh?

emlun commented on 2014-08-15 07:05

@vaski seems like you don't have [D-Bus set up in your systemd user session][1], do you? The old "btsync@user.service" and the new "--user btsync.service" differ slightly in more than just invocation syntax. The former runs in the system instance of systemd, while the latter runs in a user instance.

[1]: https://wiki.archlinux.org/index.php/Systemd/User#Basic_setup

emlun commented on 2014-08-15 07:03

@vaski seems like you don't have [D-Bus set up in your systemd user session][1], do you?

[1]: https://wiki.archlinux.org/index.php/Systemd/User#Basic_setup

vaski commented on 2014-08-14 22:49

I get this, with or without sudo
$ systemctl --user start btsync
Failed to get D-Bus connection: Connection refused
@mielouk, was dropping the sudo all you did?

mielouk commented on 2014-08-10 15:25

@Vodun

THX, up and running again :)

Vodun commented on 2014-08-10 14:56

1/ Try without sudo: systemctl --user start btsync

2/ There is no more 'btsync@user' service. (replaced by method 1)

mielouk commented on 2014-08-10 13:13

After updating my server and my desktop over the last few days, my btsync setup got broken. I'm not able to start btsync@user on either machine.

$ sudo systemctl --user start btsync
Failed to get D-Bus connection: Connection refused

$ sudo systemctl start btsync@X
Failed to start btsync@X.service: Unit btsync@X.service failed to load: No such file or directory.

I didn't change any settings or made any changes on the system.
Might you have some suggestions on how this might have happened or how to fix this?

ava1ar commented on 2014-08-09 16:50

@emlun

Thanks for sharing this. Current implementation is redirecting all output to the sync.log using btsync in daemon mode. If somebody want part of the output go to the journal, he/she may follow approach your are pointing to: switch btsync to non-daemon mode and wrap it with the shell script.

@djhaines

I saw somewhere on the forums, that btsync since version 1.3 has log rotation built-in and strips the log files to 10 megabytes by default. I am not a heavy btsync user, so I can't confirm this myself, but I believe some of the users can (like @dam5h), so lets wait for more feedback.
Anyway, I think btsync developers should implement log level configuration from config file to let people select logging level for their needs. In this case logging to journal will be safe and trouble-free.

P.S. thank you, I really appreciate the kind words I've heard from you.

emlun commented on 2014-08-09 16:25

Here's a gist showing what I was trying to explain earlier: https://gist.github.com/emlun/6f847a74e0136188d7a4

If you want some of the output in the journal, but not all of it, you could just monkey patch the executable with a shell script that filters the output. As shown in the example, you can *also* save it to a file if you so prefer. I hope it might be of use to someone. :)

emlun commented on 2014-08-09 16:25

Here's a git showing what I was trying to explain earlier: https://gist.github.com/emlun/6f847a74e0136188d7a4

If you want some of the output in the journal, but not all of it, you could just monkey patch the executable with a shell script that filters the output. As shown in the example, you can *also* save it to a file if you so prefer. I hope it might be of use to someone. :)

dhaines commented on 2014-08-09 15:40

Also, I would like to thank you, ava1ar, for being one of the truly good maintainers on the AUR. Over time, you have exhibited a tremendous capacity to actually listen and respond to your userbase. It's much appreciated.

dhaines commented on 2014-08-09 15:38

I am unaware of any log levels, but the thing is that logging to a file is the same as logging to the journal when it comes to disk usage. Either way, the partition with the log is going to fill up. The difference is that one method consolidates the logs in an easy-to-filter central location that conforms to the standard expected on systemd-based systems and the other one doesn't.

In either case, unless you're running a service with the equivalent of a verbose or debug flag, a large number of log messages usually means that the sysadmin should be fixing a problem, not that the service is being overly verbose. So don't worry about big logs being a mere possibility; worry about your local configuration when they actually present themselves.

ava1ar commented on 2014-08-09 02:20

I did not find any way how to configure log level for btsync. If you know how to do this - please share your knowledge. Otherwise I think the approach with logging to file is more correct and safe, at least heavy btsync users can use it without cleaning up the journal time-to-time.

dhaines commented on 2014-08-08 18:29

I deleted my comment earlier re: the --log option because I realized that it wasn't the right way to do it. An inherent part of systemd is the journal, so even though it may be to @dam5h's chagrin, the log really should end up accessible via journalctl, making it consistent with all other systemd services. I personally would like to see a reversion to the previous unit file and would instead point @dam5h to btsync's support options (or just Google it; possible issues include firewalls with DDoS protection and corrupt databases).

ava1ar commented on 2014-08-07 20:57

Ok, I just uploaded new version with logging problem solved. So, basically now systemd starts btsync in daemon mode with type forking. In this case not logs are going to journal, all is logged to sync.log. Please test and report your feedback.

ava1ar commented on 2014-08-07 20:15

Actually, --log <file> option for --nodaemon mode is not working for some reason, can anybody confirm this?

dhaines commented on 2014-08-07 19:23

Just use the --log <file> parameter to btsync itself.

ava1ar commented on 2014-08-07 19:08

OK, I found an easy way to completely disable output from btsync to journal. To achieve this, just put

StandardOutput=null

line in [Service] section of the systemd unit you are using and restart the service. After this output will be redirected to /dev/null.

Better approach will be to copy systemd unit to the /etc/systemd/{system or user depending of unit you are using} and make change there.

Now I am looking for the option to redirect it to the file...

emlun commented on 2014-08-07 18:57

No, I can't see any reason why using the user service instead would fix your problem. What I meant was that you can override /usr/lib service files with ones in /etc or (if it's a user service) ~/.config . Then you can experiment with it and see if you manage to solve it.

dam5h commented on 2014-08-07 18:53

Yes, that's how I start it. So I should use the user based approach via systemctl? It's odd to me that would fix the logging level issue but I'll try it.

emlun commented on 2014-08-07 18:30

@dam5h

You mean the one running as user btsync (# systemctl start btsync)? Then override with a service file at /etc/systemd/system/btsync.service instead. :)

dam5h commented on 2014-08-07 18:25

@avat1ar
When transfering, the log is reporting a line for each segment of a file that is completed:

Aug 06 17:45:51 blue btsync[24004]: file X: Piece 182 complete
Aug 06 17:45:52 blue btsync[24004]: file X: Piece 183 complete
Aug 06 17:45:52 blue btsync[24004]: file X: Piece 184 complete
Aug 06 17:45:52 blue btsync[24004]: file X: Piece 185 complete

Then, once it completes syncing the files I am getting these strange "Blocked downloading" messages related to a couple files and their respective lock files
Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file X.xlsx due Connection closed
Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file ~$X.xlsx due Connection closed
Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file Y.xlsx due Connection closed
Aug 07 09:26:44 blue btsync[27157]: Blocked downloading file ~$Y.xlsx due Connection closed

Thanks again for any help on this.

@emiun, I will take a look and see if I have a user defined service, I am using the system wide one, I am the only user of this machine.

emlun commented on 2014-08-07 17:17

@dam5h, I don't know of a way to configure btsync, so you're probably stuck with redirecting its output somewhere else. You could try overriding /usr/lib/systemd/user/btsync.service with one in ~/.config/systemd/user (or /etc) and monkey around with that. If all else fails, you could wrap the btsync call in a shell script that does some filtering on stdout (`btsync | grep foo` or the like).

ava1ar commented on 2014-08-07 17:06

@dam5h

What type of entries you have in the log? Do they appears only when you are transferring something or all the time btsync is running? Can you dump somewhere part of your log to take a look?

dam5h commented on 2014-08-07 16:56

@avat1ar, have you been able to look into the logging issue lately? I a getting huge journalctl files when I leave btsync running. They grow so fast I can't leave it running for more than a few hours before deleteing some of the journal.

Thanks!

hermes14 commented on 2014-08-07 10:59

I used to start btsync with btsync@user.service, but now with the --user service all my shares are gone. Is there an easy way to restore them instead of adding each one again?
If you think this is not the place to discuss the issue, I will open a forum thread

ava1ar commented on 2014-08-07 06:23

Yep, missprint :)

emlun commented on 2014-08-07 06:22

@ava1ar I suppose the @ in btsync_user@.service is a typo? :)

In other words, this use is no longer supported:

root@nsa # systemctl start btsync@alice

Use this instead:

alice@nsa $ systemctl -- user start

ava1ar commented on 2014-08-07 00:51

Updated to 1.3.109. btsync@.service removed, so please use btsync.service and btsync_user@service.

joepalma commented on 2014-08-06 06:56

Version 1.3.109 released

http://syncapp.bittorrent.com/1.3.109/

emlun commented on 2014-08-04 11:42

@jancici

Consider using the user service instead, the btsync@user service (which is a system service) is deprecated.

$ systemctl --user start btsync
$ systemctl --user enable btsync # Will start on first login, see the wiki [1] for how to start on boot

[1]: https://wiki.archlinux.org/index.php/Systemd/User#Automatic_start-up_of_systemd_user_instances

jancici commented on 2014-08-04 09:37

hi, I running btsync just for user, starting during boot.
I did : systemctl enable btsync@my_username

Everything is wokring well. I am interesting about logging. BTsync is producing alotof messages in log journal. Is there any way how to change level of logging?

thanks

Honiix commented on 2014-07-28 14:09

@emlun
Thanks for the clarification.
If you look at https://wiki.archlinux.org/index.php/Btsync you'll read "storage_path: ~/.btsync"
Maybe I could create an account on the wiki to edit that line, but I will test your package first :)

emlun commented on 2014-07-25 13:13

@Honiix

Yeah, seems like btsync doesn't expand ~ in storage_path. btsync also won't create the storage_path for you, although this isn't detailed in the package's post-install instructions.

If you want things to "just work", btsync-autoconfig will create all these files and directories automagically.

emlun commented on 2014-07-23 23:44

@Honiix

I'm the author of btsync-autoconfig. Thanks, I'll take a look at it tomorrow.

Honiix commented on 2014-07-23 20:25

I don't know if it's the right place to tell that, sorry if not!
I use only this package, no others like btsync-autoconfig.

$ mkdir ~/.btsync <- Had to do that, otherwise I got: "Storage path specified in config file does not exist."

In ~/.config/btsync/btsync.conf:
storage_path = "~/.btsync" <- Didn't worked for me
storage_path = "/home/MyUsername/.btsync" <- Works for me

Any idea why? If not, maybe we could update the wiki and/or btsync-autoconfig?

ava1ar commented on 2014-07-07 15:00

@akaleta91
%h will not work for system unit starting systemd 209.

@djhaines
totally agree, so

ALL

btsync@.service unit is DEPRECATED starting this moment. It will be deleted with next btsync update. Anyone using it is advised to switch to btsync_user.service user unit. If somebody has any thoughts why btsync@.service is useful in regard to btsync please share them.


dhaines commented on 2014-07-07 14:14

ava1ar: I believe that akaleta91's question answers your earlier question of whether "we actually need btsync@.service now?" I would submit that the answer is no. With systemd's user services, my view is that the @ syntax for specifying the process's user is at best deprecated and at worst a bad practice.

I say get rid of it and make people use the user service (and loginctl enable-linger, as necessary).

akaleta91 commented on 2014-07-07 08:22

Please replace (in btsync@.service)
"ExecStart=/usr/bin/btsync --config /home/%i/.config/btsync/btsync.conf --nodaemon"
with:
ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf --nodaemon

Because if home directory of user isn't equal with its name (ex. /home/u/user or sth) the daemon wouldn't start.

ava1ar commented on 2014-06-24 01:31

@ecengiz

What do you mean by posting this? PKGBUILD already updated 2 days ago to the latest version.

ecengiz commented on 2014-06-24 01:08

if [ "$CARCH" == x86_64 ]; then
source+=(http://syncapp.bittorrent.com/${pkgver}/${pkgname}_x64-${pkgver}.tar.gz)
sha1sums+=('68f5e0efbe153025759f3e83be77f08a8307ea22')
elif [ "$CARCH" == i686 ]; then
source+=(http://syncapp.bittorrent.com/${pkgver}/${pkgname}_i386-${pkgver}.tar.gz)
sha1sums+=('1bb8ffaa6be37d7ef0cffc0085ad3f18d0895893')
elif [[ "$CARCH" == arm || "$CARCH" == armv6 || "$CARCH" == armv6h || "$CARCH" == armv7 || "$CARCH" == armv7h ]]; then
source+=(http://syncapp.bittorrent.com/${pkgver}/${pkgname}_arm-${pkgver}.tar.gz)
sha1sums+=('eeead86fa1653164d35663a8350365c29d00dd55')
fi

tes5884 commented on 2014-06-12 15:51

Seems to be failing validity check.

Maybe the hash needs to be updated.

ava1ar commented on 2014-05-23 04:42

@RubenKelevra

I have no idea, you should better ask at http://forum.bittorrent.com/forum/107-bittorrent-sync/

RubenKelevra commented on 2014-05-22 18:41

Well is there any option to bind btsync to more than one interface or a specific one?

Best regards

Ruben

ava1ar commented on 2014-05-20 00:39

Updated to 1.3.105,

@EasySly, thanks for the direct links!

EasySly commented on 2014-05-19 18:20

I propose to use static urls to btsync distributions:

http://syncapp.bittorrent.com/${pkgver}/${pkgname}_${arch}-${pkgver}.tar.gz

Please note that $arch is not the same as in pacman =(

You can look at the updated PKGBUILD here http://pastebin.com/Bu0YNHXr

EasySly commented on 2014-05-19 18:17

I propose to use static urls to binary btsync distributions:

http://syncapp.bittorrent.com/1.3.94/btsync_$arhc-$version.tar.gz

You can look at the updated PKGBUILD here http://pastebin.com/Bu0YNHXr

ava1ar commented on 2014-05-06 17:18

@emlun

Thanks for the update. I read some docs and looks like %h is working for user services and do not work for system, so we are good here.

After settings WantedBy=default.target mine starts fine too (I am using KDE4).

Here is another question, coming to my mind: do we actually need btsync@.service now? Previously I was using it for running btsync as user, what is done via user service. For system-wide btsync execution, there is btsync.service. Is the any case left where we may need btsync@.service?

emlun commented on 2014-05-06 16:26

@ava1ar

I followed the instructions in Systemd/User on the wiki, and my autostarts are working with WantedBy=default.target . I haven't tested to see whether they start on boot or wait until login, though. You might need to enable "lingering", which is also documented on the wiki. Also I'm not using a DM, I log in directly to the tty.

emlun commented on 2014-05-06 16:20

@ava1ar

I followed the instructions in Systemd/User on the wiki and my autostarts are working with WantedBy=default.target . I haven't tested to see whether they start on boot or login, though. There's this thing called "lingering" you might need to enable, it's documented in the wiki.

emlun commented on 2014-05-06 16:17

@ava1ar

$ pacman -Q systemd; man systemd.unit | grep '%h' -A9 -B1
systemd 212-3
├──────────┼─────────────────────────────────┼─────────────────────────────────┤
│"%h" │ User home directory │ This is the home directory of │
│ │ │ the configured user of the │
│ │ │ unit, or (if none is set) the │
│ │ │ user running the systemd user │
│ │ │ instance. Similar to "%U", this │
│ │ │ specifier is not available for │
│ │ │ units run by the systemd system │
│ │ │ instance, unless the configured │
│ │ │ user is the root user. │
├──────────┼─────────────────────────────────┼─────────────────────────────────┤

Seems to work for me:

~ $ mkdir ~/tmp; cd ~/tmp; ls -la
total 8
drwxr-xr-x 2 emlun emlun 4096 6 maj 18.14 .
drwxr-x--- 103 emlun emlun 4096 6 maj 18.14 ..
~/tmp $ cat ~/.config/systemd/user/test.service
[Service]
Type=oneshot
ExecStart=/usr/bin/touch %h/tmp/test
~/tmp $ systemctl --user start test.service
~/tmp $ ls -la
total 8
drwxr-xr-x 2 emlun emlun 4096 6 maj 18.14 .
drwxr-x--- 103 emlun emlun 4096 6 maj 18.14 ..
-rw-r--r-- 1 emlun emlun 0 6 maj 18.14 test

ava1ar commented on 2014-05-06 15:22

@acidicX

not yet, I did not find quick solution. Will need to do deeper research, but have no time now.

@all

I added user btsync.service file. It is working fine with systemctl --user start/stop. But autostarting for user services is not working for me. Is this require some specific configuration related to systemd and DM I am using? @emlun, can you share you experience with this?

acidicX commented on 2014-05-06 13:47

@ava1ar did you manage to look into the log situation yet? :)

ava1ar commented on 2014-05-06 13:13

@umlun

%h was used originally, but since systemd 209, %h is not supported anymore. Correct me if I am wrong.

I am checking if we can easily move btsync@,service to systemd/User units.

emlun commented on 2014-05-06 12:01

@ava1ar

Use the %h parameter instead of %i: --config %h/.config/btsync/btsync.conf

And why does the package still not contain a /usr/lib/systemd/user/btsync.service (like https://gist.github.com/emlun/9129128 ) ? ;)

ava1ar commented on 2014-05-06 05:04

@RubenKelevra

Do you know a good way to add such support? Suggestions are welcome? I don't think parsing /etc/passwd is good idea.

RubenKelevra commented on 2014-05-05 12:27

the service-file should honour the $HOME path set in /etc/passwd:

btsync[23727]: Error while opening config file /home/btsync/.config/btsync/btsync.conf


# cat /etc/passwd | grep btsync
btsync:x:997:996::/var/lib/btsync:/bin/sh

# systemctl | grep btsync
btsync@btsync.service

ziv667 commented on 2014-04-28 09:19

according to bit torrent sync forum 1.3.93 is still the current build, so why is here 1.3.94 ?

or did i miss something

ava1ar commented on 2014-04-25 18:19

Updated to 1.3.94.

ava1ar commented on 2014-04-25 17:42

Looks like old scheme for direct urls is not working anymore, trying to fix the pkgbuild

ava1ar commented on 2014-04-18 22:34

Updated to 1.3.93

@acidicX, thanks for sharing, I will take a look if I can do something here.

acidicX commented on 2014-04-13 20:25

I noticed that btsync writes a *lot* of journal entries, including IPs and filenames. I'd prefer no logging. Normally btsync writes into a logfile, but since this runs as a systemd service.. is there a way to stop logging?

guildencrantz commented on 2014-04-11 18:09

1.3.87 (x86) works again.

Dala commented on 2014-04-10 08:22

@ava1ar I already downgraded myself, just left a note for other people experiencing sync problems.

ava1ar commented on 2014-04-08 19:30

@Dala

I would wait for the update. If it is critical for you - you can easily downgrade yourself by downloading sources for version 1.3.77 and building it locally. Please let me know if you need assistance with this.

fmpfeifer commented on 2014-04-08 17:28

nevermind.. it only works for root user

fmpfeifer commented on 2014-04-08 13:06

I found a error preventing btsync to run as root user. That's because the root home folder doesn't belong to the /home folder. Here follows my suggested fix:
--------
diff -Naur btsync-orig/btsync@.service btsync/btsync@.service
--- btsync-orig/btsync@.service 2014-02-21 13:21:01.000000000 -0300
+++ btsync/btsync@.service 2014-04-08 09:56:48.946976368 -0300
@@ -4,7 +4,7 @@

[Service]
User=%i
-ExecStart=/usr/bin/btsync --config /home/%i/.config/btsync/btsync.conf --nodaemon
+ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf --nodaemon
Restart=on-abort

[Install]

fmpfeifer commented on 2014-04-08 13:03

I found a error preventing btsync to run as root user. That's becouse the root home folder doesn't belong to the /home folder. Here follows my suggested fix:
--------
diff -Naur btsync-orig/btsync@.service btsync/btsync@.service
--- btsync-orig/btsync@.service 2014-02-21 13:21:01.000000000 -0300
+++ btsync/btsync@.service 2014-04-08 09:56:48.946976368 -0300
@@ -4,7 +4,7 @@

[Service]
User=%i
-ExecStart=/usr/bin/btsync --config /home/%i/.config/btsync/btsync.conf --nodaemon
+ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf --nodaemon
Restart=on-abort

[Install]

Dala commented on 2014-04-08 12:28

If you are getting the "too many open files" error (http://forum.bittorrent.com/topic/29255-btsync-error-check-too-many-open-files/page-2, http://forum.bittorrent.com/topic/29145-desktop-latest-build-1380/), they are working on the issue, and will release a new build soon, but suggest as work-around reverting to 1.3.77 perhaps we should also revert back to 1.3.77?

timski commented on 2014-04-05 12:38

@Cippaciong
I tried it, it worked :)

thanks a lot!

cippaciong commented on 2014-04-05 10:56

@timski I had a similar problem with another package on my raspberry. It should happen because the raspi hangs compressing the package with its low performance hardware.
I simply disabled compression in /etc/makepkg.conf and that solved the issue.
To do so simply go to the end of the file, locate the string beginning with PKGEXT and comment it in this way to disable compression

#PKGEXT='.pkg.tar.xz'
PKGEXT='.pkg.tar'

Hope this helps =)

timski commented on 2014-04-05 10:45

Hej, I've got an error when building on my rasberry pi


==> Creating package "btsync"...
-> Generating .PKGINFO file...
-> Adding install file...
-> Generating .MTREE file...
-> Compressing package...
/usr/bin/makepkg: line 1915: 23766 Killed ${COMPRESSXZ[@]:-xz -c -z -}
bsdtar: Write error
==> ERROR: Failed to create package file.
==> ERROR: Makepkg was unable to build btsync.

ava1ar commented on 2014-03-27 19:18

Checksum fixed.

cippaciong commented on 2014-03-26 19:13

The correct sha1sum is this one:
e487975b0132d54387deea0b8172a96e44ccbbe5

zifnab commented on 2014-03-26 16:20

sha1sums...
btsync_arm-1.3.67.tar.gz ... FAILED
when trying to upgrade btsync (on a Raspberry Pi)...

emlun commented on 2014-03-23 10:23

Any chance we could get a systemd service definition for the user session (example: [1]) included in the package? This is probably the preferred way to run systemd services as a normal user anyway, or will be soon enough.

[1]: https://gist.github.com/emlun/9129128

emlun commented on 2014-03-23 10:20

Any chance we could get a systemd service definition for the user session integrated in the package? For example: https://gist.github.com/emlun/9129128

moonman commented on 2014-03-17 11:22

And by the way, "'armv6' 'armv7'" don't exist in repos, v6 and v7 are all compiled with hardfloat.

moonman commented on 2014-03-17 11:20

Looks like at least armv5 needs alignment fixup:

cat /etc/tmpfiles.d/btsync.conf
w /proc/cpu/alignment - - - - 2

Don't know if other arm{v6h, v7h} are affected

ava1ar commented on 2014-03-12 23:05

Updated. Please note: version 1.2.91-2 is listed in AUR page because arm build has this version. While installing, 1.2.92 version will be installed for i386 and x86_64.

ava1ar commented on 2014-03-12 22:54

Looks like 1.2.92 is available only for i386 an x64 for Linux. I will update pkgbuild shortly.

gaelic commented on 2014-03-12 16:03

Sorry, forgot setting the flag.

dhaines commented on 2014-03-12 13:34

Everyone, please just use the flag out-of-date link instead of posting comments relating to new versions. Thanks.

gaelic commented on 2014-03-12 10:22

BUMP: 1.2.92 is out

ifschleife commented on 2014-03-06 21:34

I've updated the PKGBUILD for 1.2.91:
https://gist.github.com/ifschleife/9400132

DePingus commented on 2014-02-23 01:06

@tes5884

I was having the same issue on my RPi. So I re-installed ArchLinuxARM onto my 8gb sdcard to get a fresh start. Here's what I did different: After writing the image I removed the sdcard and reinserted it. Then I used GParted to extend the main Arch partition to almost fill up the card (it was only using 2GB). I left 512M at the end and, still in GParted, designated it as a linux-swap partition. Then I followed the swap entry in the Arch wiki to make an actual swap partition (not a swap file) on /dev/mmcblk0p3 (use fdisk -l to find your swap partition, it will say Linux Swap). Lastly, I used packer to install btsync with no problem.

ava1ar commented on 2014-02-21 16:25

Fixed.

I think, lets keep /home/%i for now - this is working for both 208 and 209 until 209 goes to stable.

dhaines commented on 2014-02-21 14:35

@ava1ar: You put %h in the service file, not %i. If you want to use %h, don't put the preceding "/home". You might consider installing a /usr/lib/systemd/user/btsync.service (in which you can use %h).

mrSpinx commented on 2014-02-21 12:05

Hello, i have updated the package, now it gave me this error from systemctl status btsync@mrspinx

Process: 1226 ExecStart=/usr/bin/btsync --config /home/%h/.config/btsync/btsync.conf --nodaemon (code=exited, status=1/FAILURE)
btsync[1226]: Error while opening config file /home//home/mrspinx/.config/btsync/btsync.conf

I haven't testing repo, so systemd 208.

bjo commented on 2014-02-21 11:42

@ava1ar: No hurry, 209 is in testing, not in core yet.

DePingus commented on 2014-02-21 05:19

@tes5884

Did you ever figure it out? I'm getting the same error on my RPi.

emlun commented on 2014-02-21 05:13

Maybe like this? https://gist.github.com/emlun/9129128 (I haven't upgraded to 209 yet so I can't test it)

Old:
root@host # systemctl start btsync@alice

New:
alice@host $ systemctl --user start btsync

emlun commented on 2014-02-21 05:11

Maybe like this? https://gist.github.com/emlun/9129128

ava1ar commented on 2014-02-21 04:58

Changed to /home/%i for now, thanks for sharing - I somehow missed this change.

vp1981 commented on 2014-02-21 04:54

Hello, for those who updated systemd to 209 version and uses btsync@.service:
due to changes in systemd (search NEWS for 'nss') now it is not possible to use '%h' in that service file. One option is to use '/home/%i' instead of '%h', another option is to create a user '.service' file in $HOME/.config/systemd/user (say 'btsync.service') but without 'User=%i' line and start service with systemctl --user start btsync.service.

teek commented on 2014-02-12 20:46

Ah, my error was solved in a different way:

systemctl status btsync@me:

Feb 12 20:38:06 krommekomkommers btsync[16796]: Storage path specified in config file does not exist.

So I:
mkdir .btsync

and everything works well, server is found at xx.xx.xx.xx:8889

nwilks101 commented on 2014-01-28 23:12

I'm just curious how you all feel about issuing the "echo 2 > /proc/cpu/alignment" fix for some ARM processors... my entire system (goflex home with arch) crashed and required a full reflash a couple weeks back and I'm not sure if it was due to the cpu alignment or perhaps another issue.

Are you all running it fine on your systems with the alignment "fix", if so, any insight as to whether or not it could have caused my system to cease functioning?

Thanks,

tes5884 commented on 2014-01-28 18:59

I got this error on my RaspberryPi, any ideas?
/usr/bin/makepkg: line 1915: 30176 Killed ${COMPRESSXZ[@]:-xz -c -z -}
bsdtar: Write error
==> ERROR: Failed to create package file.

23ua commented on 2014-01-28 08:50

Lorde,
You're right. The problem was the storage_path setting in my config.
Thanks.

emlun commented on 2014-01-28 08:28

23ua: it sounds more like the problem is that the 'pidfile' setting in your ~/.config/btsync/btsync.conf is set to '/var/lib/btsync/sync.pid'. If you leave that setting unset (just comment it out) it'll default to wherever other auxiliary files are saved (the 'storage_path' setting, default '~/.btsync' in btsync-autoconfig). The pidfile is not needed by the systemd service, so unless you're doing something exotic you'll probably be better off leaving it at the default.

emlun commented on 2014-01-28 08:27

23ua: it sounds more like the problem is that the 'pidfile' setting in your ~/.config/btsync/btsync.conf is set to '/var/lib/btsync/sync.pid'. If you leave that setting unset (just comment it out) it'll default to wherever other auxiliary files are saved (the 'storage_path' setting). The pidfile is not needed by the systemd service, so unless you're doing something exotic you'll probably be better off leaving it at the default.

23ua commented on 2014-01-28 08:22

teek,
I had similar problem.
___
systemctl status btsync@username
...
Jan 28 10:07:45 ... btsync[5615]: Can't open pid file /var/lib/btsync/sync.pid. Permission denied
___
Try fixing permissions for /var/lib/btsync/sync.pid. It solved my issue.

teek commented on 2014-01-27 17:12

Btw, I'm using the file created by btsync-autoconfig, my kernel is 3.8.4-1-ARCH (not up to date because Digital Ocean (vps provider) does not like that)

teek commented on 2014-01-27 17:09

Dear all,

btsync works well, when I:
<i>sudo systemctl start btsync</i>
It uses the values in /etc/btsync.conf, nice! (I can get to the webui at ip.a.d.dr:8888)

But when I
<i>sudo systemctl start btsync@user</i>
(user being my username)
Nothing happens, it is not using the values in ~./config/btsync/btsync.conf
(So no webui at ip.a.d.dr:8889 or 8888).

Any ideas?

ava1ar commented on 2014-01-07 00:36

Anyone else can reproduce problems, described by tes5884?

Based on error description, I can assume, that you have problems with file download. Can you check, what is file size of the btsync archive? And check if it is not corrupted?

ava1ar commented on 2014-01-07 00:34

Anyone else can reproduce problems, described by tes5884?

tes5884 commented on 2014-01-06 19:53

First, on my machine the sha1 for x64 is wrong.

Second, if I bypass integrity check I get the following error;

---
install: cannot stat 'btsync': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
---

Thanks!!

ava1ar commented on 2014-01-04 18:04

etes5884, this is rally strange, all checksums looks OK and works fine for me. Can you please post your checksums, just to compare.

tes5884 commented on 2014-01-03 02:14

I tried on virtualbox using x64, as well as my raspberry pi arm architecture.

ava1ar commented on 2014-01-03 01:52

What arch? Works for me, please provide details.

tes5884 commented on 2014-01-02 17:27

ava1ar
Seems to be failing validity checks...

ava1ar commented on 2014-01-01 21:58

tes5884,

thanks! Links were updated.

tes5884 commented on 2014-01-01 21:47

I think you need to change the download URL to http://syncapp.bittorrent.com/1.2.82/

emlun commented on 2013-12-24 10:31

nwilks101: What do you mean? The btsync package is right here. If you mean you can't find the package with pacman, that's because the AUR is an unofficial repository of user-contributed packages. See https://wiki.archlinux.org/index.php/AUR#Installing_packages for instructions on how to install packages from the AUR. While the AUR is meant to be an open repository where users can contribute useful packages of software not included in the official repositories, these packages could contain malicious software since anyone can submit packages of any kind to it. Be careful when you build and install unofficial packages.

Also, after you install the btsync package there's also the btsync-autoconfig package here in the AUR that helps with creation of configuration files. :)

emlun commented on 2013-12-24 10:29

nwilks101: What do you mean? The btsync package is right here. If you mean you can't find the package with pacman, that's because the AUR is an unofficial repository of user-contributed packages. See https://wiki.archlinux.org/index.php/AUR#Installing_packages for instructions on how to install packages from the AUR. While the AUR is meant to be an open repository where users can contribute useful packages of software not included in the official repositories, these packages could contain malicious software since anyone can submit packages of any kind to it. Be careful when you build and install unofficial packages.

nwilks101 commented on 2013-12-23 01:56

Hi everyone,

I am not able to find btsync in the AUR.

I am running Arch on Arm5, (a GoFlex Home NAS).

I have made lots of attempts at installing outside of pacman but I'm having no luck. I can download, extract, and see the files, but I'm not able to execute the program.

Any help is much appreciated, but I figured it would be easiest to just do it via pacman (if I could find it there...)

Thanks,

jipiese commented on 2013-11-29 12:13

1.2.82 has been released
http://syncapp.bittorrent.com/1.2.82/

smokephil commented on 2013-11-28 22:30

please add 'arm' to arch, I have successfully installed it
Hardware: Pogoplug v2

emlun commented on 2013-11-25 13:45

About the pid_file setting: Unless you're very picky with this kind of thing, you don't need to change this from the default (that is, you can leave it undefined in the config file). The systemd service definition uses the --nodaemon flag since some time ago and completely ignores the pid file.

=====

To flesh out ava1ar's post: the btsync@.service definition file does not need modification to work, you only need to create the configuration file ~/.config/btsync/btsync.conf. If you have the btsync-autoconfig package installed (and its service enabled, done by default in post_install) then a working config file will be created for you when you start the btsync@alice service.

All this is also documented on the BitTorrent Sync wiki page.

emlun commented on 2013-11-25 13:42

To flesh out ava1ar's post: the btsync@.service definition file does not need modification to work, you only need to create the configuration file ~/.config/btsync/btsync.conf. If you have the btsync-autoconfig package installed (and its service enabled, done by default in post_install) then a working config file will be created for you when you start the btsync@alice service.

All this is also documented on the BitTorrent Sync wiki page.

emlun commented on 2013-11-25 13:37

About the pid_file setting: Unless you're very picky with this kind of thing, you don't need to change this from the default (that is, you can leave it undefined in the config file). The systemd service definition uses the --nodaemon flag since some time ago and completely ignores the pid file.

ava1ar commented on 2013-11-25 02:42

"Needless to say, the default btsync@.service doesn't work without some tweaking."

This is expected behavior - configuration steps are being provided at post-install steps. If you want get king of automatic setup, try installing btsync-autoconfig package.

oats commented on 2013-11-24 12:18

@ava1r, Thanks. I didn't notice the other service.

Needless to say, the default btsync@.service doesn't work without some tweaking.

oats commented on 2013-11-24 12:17

@ava1r, Thanks. I didn't notice the other service.

ava1ar commented on 2013-11-23 02:34

tb01110100,

Making User=root for btsync@.service makes this unit-file useless, because it is intended to execute btsync as normal user, but not root (to run as root, just use btsync.service).

What about error about accessing pid file - be sure to update "pid_file" value to user-readable location in /home/ava1ar/.config/btsync/btsync.conf

oats commented on 2013-11-23 02:24

The included btsync@.service does not work correctly for me. I have to modify it per user to get it to work. Here's the one for my user:

[Unit]
Description=Bittorent Sync service for %i
After=network.target

[Service]
User=root
ExecStart=/usr/bin/btsync --config /home/thomas/.config/btsync/btsync.conf --nodaemon
Restart=on-abort

[Install]
WantedBy=multi-user.target

Otherwise, the service fails with an error about not being able to read the pid file.

oats commented on 2013-11-23 02:22

The included btsync@.service does not work correctly for me. I have to modify it per user to get it to work. Here's the one for my user:

[Unit]
Description=Bittorent Sync service for %i
After=network.target

[Service]
User=root
ExecStart=/usr/bin/btsync --config /home/thomas/.config/btsync/btsync.conf --nodaemon
Restart=on-abort

[Install]
WantedBy=multi-user.target

ava1ar commented on 2013-11-17 23:40

freestyler7, thx, will fix it.

freestyler7 commented on 2013-11-17 23:38

Thanks for the package.
Just some syntax that needs fixing on the next release:

"To autostart btsync on systm start, excute"

ava1ar commented on 2013-11-17 17:09

btsync.install updated with more detailed post-install instructions, postupgrade and postinstall steps are now different.

ava1ar commented on 2013-11-17 16:38

benoliver999, u r welcome. Enjoy the software :)

benoliver999 commented on 2013-11-17 16:38

Step 2 did it!

Thanks for your help.

ava1ar commented on 2013-11-17 16:33

This kind of error happens when systemd can not locate unit file. Please do the following:
1. Ensure, /usr/lib/systemd/system/btsync@.service file exists
2. Perform sudo systemctl daemon-reload
3. Retry start and status commands

benoliver999 commented on 2013-11-17 16:27

[ben@BenNetbook ~]$ sudo systemctl status btsync@ben
btsync@ben.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

ava1ar commented on 2013-11-17 16:26

Can you please share output of

sudo systemctl status btsync@ben

after you do

sudo systemctl start btsync@ben

benoliver999 commented on 2013-11-17 16:17

@ava1ar

I copied the .conf to ~/.confing/btsync/btsync.conf then changed the storage dir, PID location to user directories, and changed user/pass.

ava1ar commented on 2013-11-17 16:10

benoliver999

Did you perform post-install configuration, following steps showed after package installation?

benoliver999 commented on 2013-11-17 16:09

I'm getting the following:

[ben@BenNetbook ~]$ sudo systemctl start btsync@ben
Failed to issue method call: Unit btsync@ben.service failed to load: No such file or directory.

It runs without the @user, but obvious then I get permissions problems with the files.

jpaechnatz commented on 2013-11-14 06:39

1.2.70 is out. 107b4be0d78f3be3acf8106cf0dab0b1d09303f7

giowck commented on 2013-11-12 16:45

Starting the service gives an error:

[giowck@archlinux-macbook ~]$ systemctl status btsync@giowck
btsync@giowck.service - Bittorent Sync service for giowck
Loaded: loaded (/usr/lib/systemd/system/btsync@.service; enabled)
Active: failed (Result: exit-code) since Di 2013-11-12 17:35:11 CET; 48s ago
Process: 362 ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf --nodaemon (code=exited, status=1/FAILURE)
Main PID: 362 (code=exited, status=1/FAILURE)

The problem is that running "/usr/bin/btsync --config %h/.config/btsync/btsync.conf" from cmd line says that the home directory doesn't exist, because the "%h" is not replaced with the home directory, instead it is just appended... Strange thing...

Solved by using the btsync service without the user part...

pilin commented on 2013-11-08 10:54

Please add "armv6h" to the platforms array.
1. You already list arm*h platforms in the source link selection.
2. I've just installed btsync on RPi with armv6h platform and it works.

asaaki commented on 2013-11-06 14:37

They released version 1.2.68, so the checksums are not correct anymore.

SHA1 checksums:

tested
linux x86_64: 762641594714f02ff966dd0dd0665bfc8247056e

untested
linux i368: 1394d9436e392bc9cb5ddb6e5ee40290e4e80dd7
linux arm: 130880d2201f61a1de3d0c3ad8f19d9d87098939

ava1ar commented on 2013-11-06 14:17

Hm, this is strange. Will check this.

dhaines commented on 2013-11-06 14:16

I too am getting the failed checksum.

Mr.Burns commented on 2013-11-06 14:07

Checksums seemed to fail.

==> Validating source files with sha1sums...
btsync.service ... Passed
btsync@.service ... Passed
btsync_x64-1.2.67.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
:: btsync cleaned

ForeverYoung commented on 2013-11-06 06:42

What about adding armv6h (PI) and armv7h (e.g. cubie-board) to PKGBUILD?

ava1ar commented on 2013-11-06 04:19

Package was updated, please report issues here if any. Thanks.

joepalma commented on 2013-11-06 01:21

Version 1.2.67 released: http://forum.bittorrent.com/topic/24781-new-1267-build/

skimm commented on 2013-10-31 19:28

hendry: add armv6h to the arch array in the PKGBUILD

hendry commented on 2013-10-30 09:59

Any hints to get a version of this running on a 'armv6h' PI?

emlun commented on 2013-10-23 14:08

WonderWoofy: Sure. I haven't yet filed a removal request since I wanted to give people a chance to update and see the post_install message. I plan on requesting removal in a few days, but I guess I could just as well request a merge.

WonderWoofy commented on 2013-10-22 14:15

If the below is the case, then should this package be removed? Possibly with votes and comments merged with the btsync package?

emlun commented on 2013-10-21 13:38

TheMadMechanic: Try checking journalctl -xn20 after trying to start bsync, that might give you an idea what's wrong.

emlun commented on 2013-10-21 13:31

TheMadMechanic: Ok, then I'm afraid I don't know what the problem is. By the way, the storage_path configured in the config file is where sync metadata is stored, not the synced files themselves. Where your synced folders go is specified in the WebGUI on a per-folder basis, completely independently of the storage_path setting.

TheMadMechanic commented on 2013-10-21 13:03

Lorde I created ~/btsync and that is where I plan on nesting everything I want to share with bittorrent sync. That's why the path is set as it is.

emlun commented on 2013-10-19 16:00

TheMadMechanic: Does ~/btsync exist? Or did you intend to set storage_path: ~/.config/btsync ?

TheMadMechanic commented on 2013-10-19 13:18

I'm having trouble getting this to work. I had tried installing the bittorrent-sync package from AUR but then it got superceded.That's fine, I uninstalled it then installed this package. As you spell out in your post-install instructions I:

mkdir -p ~/.config/btsync
cp /etc/btsync.conf ~/.config/btsync/btsync.conf

Here is a link to my users config (I hashed a few things for privacy)
http://pastie.org/8414302

When I run systemctl start btsync@##### I get the following error:
"Failed to issue method call: Unit btsync@#####.service failed to load: No such file or directory."

I'm not sure where to go from here because it still isn't working for me.

emlun commented on 2013-10-19 09:44

This package has now been superseded by the btsync and btsync-autoconfig packages. From now on, btsync will provide BitTorrent Sync itself (the executable and systemd devides) while btsync-autoconfig will be an optional dependency that provides on-demand automatic creation of config files when btsync@.service starts.

emlun commented on 2013-10-18 18:57

TheMadMechanic: You'll want to use `systemctl start btsync@username`, not the plain `btsync` call. Enabling the service only creates the symlinks, without starting the service, like most other systemd services.

Trivia: the raw btsync executable will attempt to save its metadata in .sync/ relative to the directory where the executable is located (/usr/bin in this case). I don't know where those double /s came from. :s

TheMadMechanic commented on 2013-10-18 17:02

I installed this package and edited the username, password, and port in /etc/btsync.conf. I also created and edited the config at ~/.config/btsync/btsync.conf (In my case, both configs are identical.)

I did systemctl enable btsync@username and it listed the links it created as expected.

I then attempted to go to http://localhost:8888/gui/en/index.html in Firefox and I get a "problem loading page" issue.
I tried to start btsync by simply running 'btsync' in terminal and it also threw errors. "Can't open pid file /usr/bin/.sync//sync.pid. No such file or directory"

right away that looks suspect for two reasons, first off the double / between .sync and sync.pid and also because the pid (according to the wiki) is handled automatically.

Any thoughts on where to go from here?

emlun commented on 2013-10-17 06:17

petko10: I'm sorry, I don't understand the problem...

ava1ar commented on 2013-10-13 18:19

Lorde, thanks for clarification. I will think what can be done to automate this steps, keeping package simple.

emlun commented on 2013-10-13 16:51

Sorry, I didn't provide the clarification you requested. The btsync@.service in bittorrent-sync runs btsync-wrapper, which checks if ~/.config/btsync/btsync.conf exists, creates it (using btsync-makeconfig) if necessary, and then runs btsync. The btsync.service does not use btsync-wrapper since a default config file for that service is included in the package.

btsync-makeconfig is just an option-driven frontend to `btsync --dump-sample-config | sed 's/foo/bar/' | sed 's/boo/far' | ...`

emlun commented on 2013-10-13 16:44

ava1ar: The use case I imagined is that the user that installs the package may not be the only one that will use it. alice installs it and follows the post-install instructions, runs systemctl start btsync@alice and everything is well and good. But when bob notices that btsync is available on the system and does systemctl start btsync@bob, it fails silently. Of course, he could just look in journalctl and see that the config file could not be read, google how to create one and do so.

I agree that we do not *need* the script, but I can imagine that more than just a few people would find it handy, and thus there is reason for it to exist in AUR. But, like I said, it would probably be better off in an optional add-on package. I'll see if I can pull that off using only clever systemd definitions, and no modifications to this package. If so, then I'll probably refactor the bittorrent-sync package to only provide the config creator script, and delegate the core functionality to this package.

ava1ar commented on 2013-10-12 21:11

Lorde,

Thanks for pointing out LICENSE.TXT file - I updated package to use it, instead of file copies.

What about additional scripts for creation ~/.config/btsync/btsync.conf, can you please clarify, what exactly they are creating there and why can't this be done manually once, rigth after first install? I have all required steps listed in .install file, you need just copy and run command from there and then adjust file content as per settings you need - is it so difficult? I can even add sample setting to this install file, but I still disagree, that we need separate script to do this one-time action.

petko10 commented on 2013-10-12 19:06

On both my machines btsync started with systemd does not work properly - for some reason the service starts properly , but just does not connect with other machines (I suppose it needs other survices (for ex. networking) started at nearly the same time ) . When I reastart it with systemctl everything is ok . My desktop is GNOME . Workaround : start the application with startup programs through the gnome-session-properties configuration tool with the line /usr/bin/btsync --config... etc. from the systemd service (for reference see systemctl status btsync@.. ) .
Edit : that doesn't solve it either ... (at least not every boot) . Any ideas on troubleshooting the problem ?

petko10 commented on 2013-10-12 18:40

On both my machines btsync started with systemd does not work properly - for some reason the service starts properly , but just does not connect with other machines (I suppose it needs other survices (for ex. networking) started at nearly the same time ) . When I reastart it with systemctl everything is ok . My desktop is GNOME . Workaround : start the application with startup programs through the gnome-session-properties configuration tool with the line /usr/bin/btsync --config... etc. from the systemd service (for reference see systemctl status btsync@.. ) .

emlun commented on 2013-10-12 11:59

Oh, and one more thing: my opinion is that the LICENSE.TXT distributed with the executable should be included in the package. Perhaps the privacy policy too, but both it and the terms of use are referenced in LICENSE.TXT.

emlun commented on 2013-10-12 11:47

ava1ar: The garbage is, functionally, exactly one thing: auto-creation of a ~/.config/btsync/btsync.conf if it doesn't exist. That said, you have a very valid point, this is much more in line with the Arch Way. Part of me now wants to drop bittorrent-sync, but it'd be a shame to let the work put into the garbage go to waste (no pun intended :P). Perhaps we could devise a way for the garbage to be available as an add-on for those who want it, and let this KISS package be the default?

bobwya commented on 2013-10-08 17:56

Could I suggest adding at least
Nice=19
in the systemd service units... This is supported under both the standard CFS and the alternative BFS kernels...

The service is, in my experience, a real CPU hog!!

ava1ar commented on 2013-10-02 18:15

ottomodinos, good catch. Let me check this and come back with the answer.

ottomodinos commented on 2013-10-02 16:41

Shouldn't the shell for the btsync user be something like /bin/nologin? Is there any need for it to be /bin/sh?

ava1ar commented on 2013-09-29 17:23

Why was this flagged out-of-date? Is there new version out?

emlun commented on 2013-09-29 10:01

@RubenKelevra: I don't see how that could happen, since /etc/btsync.conf is included in the package. Unless you deleted it yourself. ;P

Anonymous comment on 2013-09-18 21:10

@Lorde: ahh, I see. I didn't actually write that util, but I also never tested it on a clean install! My bad!!! I'll check it out later tonight & see if I can get this fixed. Thanks for letting me know!

emlun commented on 2013-09-18 21:00

@serialhex: Sorry, I meant 49. In build(), the btsync-makeconfig.sh script is executed. This in turn does `cat /usr/share/bittorrent-sync/btsync.conf.doc` on line 136. I haven't actually tried building on a clean system recently, so I can't be completely sure, but it shouldn't matter whether btsync.conf.doc is in the archive or not - when building the package on a clean system the file is not installed in that location.

Anonymous comment on 2013-09-18 03:21

@Lorde: I just got a chance to take a look, and on line 29 of neither of those files is there any reference to btsync.conf.doc and it should get installed with everything else. It's right there in the archive along with everything else... I'm releasing a new version today anyway, so try again. It's just a few updates & such.

emlun commented on 2013-09-17 14:02

@ava1ar, serialhex the error (one I made!) is on line 29 in PKGBUILD. btsync-makeconfig.sh expects the /usr/share/bittorrent-sync/btsync.conf.doc file to exist, but of course it doesn't on a clean system. I might file a pull request in a day or two if no-one beats me to it.

emlun commented on 2013-09-17 13:56

@serialhex Unless I'm mistaken, the `systemctl start btsync` call will run it as the "btsync" user. There is supposed to be a corresponding group, so setting `chown -R user:btsync /dir/to/sync && chmod -R g+rwx /dir/to/sync` or something like it should work too.

Anonymous comment on 2013-09-17 12:57

@ava1ar: I'm looking into it, I'll let you know when I find something out, but maybe try re-downloading everything, as it works just fine everywhere else I (and other people) have installed it.

@zeltak: It still sounds like a btsync issue & not an arch packaging issue. The dir(s) you are trying to synchronize, are there a bunch of files in them? Is your HDD thrashing while it's running? If so, try starting it as you again, but with no shared dirs and see what happens. Also it is possible to run as root (systemctl start btsync) and sync stuff from your home dir, just that all the files will be owned by root (though a simple `sudo chown -R zeltak:user` will fix that).

zeltak commented on 2013-09-17 10:39

also Re my last comment, if i start it as system user how does one choose to sync folders from my home dir? it seems i cant do that unless i start it as my own user (but then the cpu goes to 100% again)

best

z

zeltak commented on 2013-09-17 07:31

So this is interesting..

after having to stop using it since it spiked the cpu to 100% constant i tried running it as system user rather then own use (IE instead of systemctl start btsync@zeltak i used systemctl start btsync) and the cpu load is 0.6%

serialhex, is it still a btsync issue or an arch issue? i posted this issue on the BT-sync forum without great success so far, any ideas?

best

ava1ar commented on 2013-09-17 03:12

Uploaded again, since https://aur.archlinux.org/packages/bittorrent-sync/ package now has lot of garbage (wrappers, dummy configs, etc). I prefer KISS - this package doesn't have anything besides:
- license
- btsync binary
- service files for systemd (per-system and per-user)

All other required stuff generated on the fly. Post-install instruction describes how to created per-user config.

ava1ar commented on 2013-09-17 02:25

Package failed to build on clean system:

cat: /usr/share/bittorrent-sync/btsync.conf.doc: No such file or directory
./btsync-makeconfig.sh: line 146: btsync: command not found

Fix please

emlun commented on 2013-09-13 11:33

@RubenKelevra looks to me like insufficient privileges. Are you running `systemctl start btsync` as root?

RubenKelevra commented on 2013-09-13 02:46

Sep 13 04:45:41 i3 logger[30063]: Using config file path: /etc/btsync.conf
Sep 13 04:45:41 i3 logger[30064]: Config file does not exist - will create it
Sep 13 04:45:41 i3 btsync-wrapper[30061]: /usr/bin/btsync-wrapper: Zeile 60: /etc/btsync.conf: Keine Berechtigung
Sep 13 04:45:41 i3 logger[30068]: Could not create config at /etc/btsync.conf -

kevincox commented on 2013-09-13 00:30

Thanks @Lorde.

I have subscribed to the pull request (https://github.com/serialhex/bittorrent-sync/pull/5) it looks good to me.

emlun commented on 2013-09-13 00:28

@kevincox Very good suggestions, easy to implement too. :) Pull request submitted!

kevincox commented on 2013-09-12 20:21

Great package, I just have a couple of suggestions.

Since btsync supports the `--nodaemon` flag it is best to use it with systemd. Simply add that to the `btsync-wrapper` commandline and remove the Type and PIDFile lines.

Also, the `btsync-wrapper` should exec `btsync` at the end so that you don't have an extra bash script in memory.

Anonymous comment on 2013-08-28 21:42

@hendry: I don't use vim (heathen that I am :P ) so I don't have a use for any such change. There is a GitHub repository you can fork & edit & pull-request though: https://github.com/serialhex/bittorrent-sync

@everybody-with-problems: Unless it's an installation problem or something else related to the BTS package itself, I can't help you. This isn't necessarily me passing the buck, more like letting you know where to get the most effective help, as these are binary packages that get downloaded & beta software. The best place to get help is the BTS forum: http://forum.bittorrent.com/forum/56-bittorrent-sync/ If there *IS* a problem with the package let me know though, I'll do my best to correct it ASAP! (Also, I try to stay on top of new releases, so I don't necessarily need to be reminded by someone flagging the package out-of-date, give me a day or so...)

-serialhex

hendry commented on 2013-08-28 07:20

Could
// vim: set ft=javascript:

please be prepended to the generated conf via btsync-makeconfig.sh ?

I lost quite a bit of time not realising storage_path was commented out! :/

zeltak commented on 2013-08-22 14:21

Hi

im having the same issues as donniezazen. IE system gets hot, cpu at 100%. does anyone else have these issues?


z

rabidfurby commented on 2013-08-03 19:46

I was running into an issue where 'sudo systemctl start btsync@zack' fails after about a minute with a timeout, but in that time, btsync was running quite happily (as evidenced by ps output, and by other machines on my network starting to sync with it).

The issue ended up being that my btsync.conf (from a previous install) had a different path for the PID file that the systemd btsync@.service file. This caused systemd to wait around thinking that btsync hadn't started yet, even though it had.

If anyone else runs into this issue - make sure that the pid_file parameter in your btsync.conf matches PIDFile in /usr/lib/systemd/system/btsync@.service.

Anonymous comment on 2013-07-30 01:38

@donniezazen - there isn't anything I can help you with when it comes to things like that. The best thing you can do is go to the BTS forums & see if anyone else is having the same problem &| post your problem & see if they will fix it.

http://forum.bittorrent.com/forum/56-bittorrent-sync/

donniezazen commented on 2013-07-29 21:57

As soon as I run btsync daemon, my system temperature goes crazy high. I doesn't look like it's transferring file though two devices are connected.

libercv commented on 2013-07-29 21:37

Thank you, @serialhex! I will use github from now on.

Anonymous comment on 2013-07-29 20:23

@libercv - updated the PKGBUILD. If you have a GitHub account you (or anyone else) can send pull reqs directly from the repo: https://github.com/serialhex/bittorrent-sync

(doing that makes it easier to attribute work to ppl also, and I like doing so even if it's a simple change like this)

libercv commented on 2013-07-29 09:39

Thank you @serialhex!
I've tested it with armv7h and it works too. Could you add support for this arch? Here's a possible diff for it: http://pastebin.com/CvvFGHJ1
Thanks again, Liberto.

Anonymous comment on 2013-07-21 12:02

@serialhex - thank you, its working great!

emlun commented on 2013-07-21 11:29

@boina No, BitTorrent only distributes the raw btsync executable which doesn't provide anything else than the WebGUI at this time. All this package does right now is provide systemd service definitions and some utility scripts for generating default config files.

Regarding the username/homedir thing: The btsync@.service uses the %h variable provided by systemd to expand the user's home directory, so I suppose if you run `systemctl start btsync@alice` then systemd will look for alice in /etc/passwd and expand the %h variable to the home directory stated there. So if the alice user does not exist or does not have a home directory, that will probably fail.

boina commented on 2013-07-20 23:41

Great!!! Thanks for your help, didn't realize that I should have the same user name as my home directory. All worked out now!!! I didn't know this as previously I did run bittorrent but with ./bsync from the download directory.
One last question, it doesn't have an icon on the systray to know what is doing at any moment?

Thanks to you all!!!

emlun commented on 2013-07-20 23:25

@boina (I suppose the boina user also needs to have a home directory if btsync@.service is to work as-is)

senorsmile commented on 2013-07-20 23:24

@boina, try running this
sudo journalctl -f

then, in another terminal try
sudo systemctl start btsync@boina

and see what it spits out.

emlun commented on 2013-07-20 23:23

@boina does the user "boina" exist on your system? (judging by your prompt, it looks like the current $USER is "netlak")

boina commented on 2013-07-20 23:19

Checked and all files posted bi @sensorsmile are in place. and journalctl seem to trow lots of thing but none related to btsync.
On the error log found this:

Jul 20 19:46:53 localhost systemd[1]: [/usr/lib/systemd/system/btsync@.service:10] Failed to resolve unit specifiers on %h/.config/btsync/sync.pid. Ignoring.

Jul 20 19:46:53 localhost systemd[1]: [/usr/lib/systemd/system/btsync@.service:10] Not an absolute path, ignoring: %h/.config/btsync/sync.pid

Thanks!!

senorsmile commented on 2013-07-20 22:44

@boina, I was getting the exact same thing happening. It ended up being that the ~/.config/btsync/ folder wasn't populating properly, due to an older version I had previously installed before going with this aur package. I set it up on another computer and saw 7 files that are supposed to be there:

btsync.conf
settings.dat
settings.dat.old
sync.dat
sync.log
sync.pid
webui.zip

I copied them from the other machine and all is working well.

emlun commented on 2013-07-20 22:40

@boina what's a `journalctl -xn30` say? (Be sure to call it before the log gets bumed by other processes)

boina commented on 2013-07-20 22:26

Hi there!!! Thanks for this package!!
I have a problem tought, when trying to start the deamon I get the following:

[netlak@jamming Descargas]$ sudo systemctl start btsync@boina
[sudo] password for netlak:
Job for btsync@boina.service failed. See 'systemctl status btsync@boina.service' and 'journalctl -xn' for details.

[netlak@jamming Descargas]$ systemctl status btsync@boina.service
btsync@boina.service - BitTorrent Sync service for boina
Loaded: loaded (/usr/lib/systemd/system/btsync@.service; disabled)
Active: failed (Result: resources)

Any ideas??

zeltak commented on 2013-07-20 10:33

Hi all

im using btsync with a laptop and it seems like after a resume from sleep/hibernate sycing is halted until i manually restart bysync. anyone else having this issue?

best

Z

kozec commented on 2013-07-19 22:30

serialhex: What Arch dev wants and what Arch user does stopped be same thing sometime near Big Python2 Wreckage :p

I'm still happily using rc scripts, but I understand and don't except You to package my script (although it would make my life easier). I provided script in case there is other other rc.d user trying to use bittorrent sync.

Anonymous comment on 2013-07-19 21:45

@kozec: I appreciate the work, but unfortunately rc.d scripts have gone the way of the Dodo in Arch, since Oct 2012! So I'm not going to add your script to the PKGBUILD. Again, thank you for the work though.

https://www.archlinux.org/news/systemd-is-now-the-default-on-new-installations/

kozec commented on 2013-07-19 21:05

Thanks for the package!

rc.d service script - http://pastebin.com/aa3j0Djh

Anonymous comment on 2013-07-19 18:34

@crabman: it doesn't mess anything up in any real sense, I just don't see why it's needed other than legacy reasons... and if that's all I'd rather get rid of it if I can.

crabman commented on 2013-07-19 17:39

@serialhex: because when this package was started, bittorrent-sync had no version number, which is why the former packager used the date. And 20130401 is "newer" than 1.1.13, so the epoch had to be increased. Note that these versioning changes are exactly what the epoch variable is for.

What does the epoch mess up exactly?

Anonymous comment on 2013-07-19 16:10

aszkid - if you started it up with the `sudo systemctl start btsync@aszkid` then the username you need to use is `aszkid` (or whatever your username is).

Anonymous comment on 2013-07-19 15:18

I'm not able to access the WebUI using the default credentials on the /etc/btsync.conf file (admin - password). Do i have to change them before starting?

Anonymous comment on 2013-07-19 14:04

crabman: why was it put there in the first place? there was no reason for it, and i loathe to put it back in as it is unnecessary cruft that messes with things. i would rather everyone upgrade & get a version w/o the epoch...

is there any way to change this besides putting the epoch variable back in?

crabman commented on 2013-07-18 18:49

serialhex: i am the one who put the epoch=1 there. And its _very_ important. With it removed, everybody using an AUR manager (such as yaourt) will be stuck with version 1:1.1.27 because the manager thinks that version 1:1.1.27 is newer than version 1.1.42. Please readd it.

crabman, aka Kilian Lackhove

roguewolf commented on 2013-07-18 14:06

Thanks serialhex, that's done the trick.

Anonymous comment on 2013-07-18 13:48

@roguewolf I just uploaded it again, the SHA256 on the uploaded package was wrong. You should be able to get it to work now, sorry for the trouble!

roguewolf commented on 2013-07-18 13:32

I've just tried again with the same result (SHA256 sum of downloaded copy of btsync_i386-1.1.42.tar.gz is ecc84e88db5fe3054306b1901fb437bf868df9b8ede5dfbc22b79105dd2a8e2b):

$ wget https://aur.archlinux.org/packages/bi/bittorrent-sync/bittorrent-sync.tar.gz
--2013-07-18 14:21:41-- https://aur.archlinux.org/packages/bi/bittorrent-sync/bittorrent-sync.tar.gz
Resolving aur.archlinux.org (aur.archlinux.org)... 78.46.78.247, 2a01:4f8:120:34c2::2
Connecting to aur.archlinux.org (aur.archlinux.org)|78.46.78.247|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 4955 (4.8K) [application/x-gzip]
Saving to: ‘bittorrent-sync.tar.gz’

100%[======================================================================================================================>] 4,955 --.-K/s in 0s

2013-07-18 14:21:41 (312 MB/s) - ‘bittorrent-sync.tar.gz’ saved [4955/4955]

$ tar -xvzf bittorrent-sync.tar.gz
bittorrent-sync/
bittorrent-sync/PKGBUILD
bittorrent-sync/bittorrent-sync.install
bittorrent-sync/btsync.service
bittorrent-sync/btsync@.service
bittorrent-sync/btsync-makeconfig.sh
bittorrent-sync/btsync-wrapper.sh
bittorrent-sync/btsync.conf.doc

$ cd bittorrent-sync/
bittorrent-sync$ makepkg
==> Making package: bittorrent-sync 1.1.42-1 (Thu 18 Jul 14:23:26 BST 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found bittorrent-sync.install
-> Found btsync.service
-> Found btsync@.service
-> Found btsync-makeconfig.sh
-> Found btsync-wrapper.sh
-> Found btsync.conf.doc
-> Found terms-of-use.html
-> Found privacy-policy.html
-> Found btsync_i386-1.1.42.tar.gz
==> Validating source files with sha256sums...
bittorrent-sync.install ... Passed
btsync.service ... Passed
btsync@.service ... Passed
btsync-makeconfig.sh ... Passed
btsync-wrapper.sh ... Passed
btsync.conf.doc ... Passed
terms-of-use.html ... Skipped
privacy-policy.html ... Skipped
btsync_i386-1.1.42.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

Anonymous comment on 2013-07-18 13:17

@roguewolf I just double-checked the checksum on that file and it checks out, maybe you downloaded a bad copy & should try again?

emlun commented on 2013-07-18 11:51

In any case, the service (/usr/lib/systemd/system/btsync@.service) assumes that the PID file is at ~/.config/btsync/sync.pid. Unless you explicitly set the "pid_file" setting in your config file, the sync.pid file is created in the "storage_path" directory. If you've changed either of those settings, you'll need to update the PIDFile setting in the service accordingly.

emlun commented on 2013-07-18 11:49

@senorsmile Did you change the "storage_path" or "pid_file" settings in your config file?

roguewolf commented on 2013-07-18 06:42

btsync_i386-1.1.42.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

senorsmile commented on 2013-07-18 02:03

I just uninstalled the other aur package (btsync) and installed this one. I am getting an error I can't seem to resolve trying to start the btsync@user service: PID file /home/shaun/.config/btsync/sync.pid not readable (yet?) after start. I tried creating it and applying various permission, but it either complains it can't reach it, or just fails with no error. Any one else transitioned from the other package?

Anonymous comment on 2013-07-16 23:23

Tried later, now it works... (yes, very much EEBKAC :P )

Anonymous comment on 2013-07-16 23:05

Updated the package to 1.1.42, but the AUR doesn't seem to let me upload right now... I'll try later.

simonsd commented on 2013-07-16 19:05

1.1.42 is out
This build renames the SyncArchive folder to the intended .SyncArchive (replacement for .SyncTrash)

Link to updated pkgbuild: http://pastie.org/pastes/8146588/text
(bumped the version, updated the sha256 sums)

Anonymous comment on 2013-07-16 01:23

Updated to 1.1.40 - some of the problems people are having may be resolved by updating... try it and see!

rukolonist commented on 2013-07-15 19:27

@geric
Now I have the same issue. It described here: http://forum.bittorrent.com/topic/20580-infinite-syncing/

Anonymous comment on 2013-07-15 02:32

zeltak: I think you might want to bring this up on the official Bittorrent Sync pages, as it sounds like something involving that directly...

a link to their forum: http://forum.bittorrent.com/forum/56-bittorrent-sync/

zeltak commented on 2013-07-15 01:35

btw another intresting fact. if i uninstall it, reinstall and start the service it works ok. as soon as i reboot it comes back at 99% cpu. stoping and starting the service dosent help

Z

zeltak commented on 2013-07-14 19:14

thx Lorde

but here it dosent seem like its indexing and its still at 100% cpu, see image:

https://paste.xinu.at/SBRh/

it seems in the webGUI that its idle, have no cluem and its 100% of the time like this

best

Z

zeltak commented on 2013-07-14 19:08

thx Lorde

but here it dosent seem like its indexing and its still at 100% cpu, see image:

https://paste.xinu.at/SBRh/

it seems in the webGUI that its idle, have no cluem and its 100% of the time like this

best

Z

geric commented on 2013-07-14 19:06

Since the last update my Btsync client refuses to sync. The up-to-date client knows the other client is out of sync and says that its uploading data, but the other client doesn't GET data and the "UP:/Down:" counter shows 0.00Kbs.

Already wiped and reset Bittorrent on both machines

emlun commented on 2013-07-14 17:48

Actually, I just observed mine do just that - the WebGUI said "indexing" on one of my folders, and top reported btsync using 94% processor. Then the indexing finished and CPU usage promptly sank to practically zero, so I think that is the cause. I would suspect and hope that btsync runs this at low priority, though.

emlun commented on 2013-07-14 16:49

@zeltak

That's odd. The only thing I can think of right away is that the daemon is indexing files. I think that this involves computing a lot of checksums or the like, so if you have a lot of data in a directory which hasn't yet been fully indexed (the WebGUI says "indexing"), then that might be the cause.

rukolonist commented on 2013-07-14 15:39

serialhex
Thanks. The problem was in custom pid file location. I removed my custom location and now it works fine.

zeltak commented on 2013-07-13 18:59

hi serialhex

since V 1.27 and also with latest (1.33) get 100% cpu usage whenever the deamon is running.

im running it like this:

sudo systemctl stop btsync@zeltak

anyone else having theses issues? what can i do to try and solve it

best

Z

Anonymous comment on 2013-07-12 13:26

TheRealSoup: I removed it because it wasn't needed. Unfortunately I was not the person who originally wrote the PKGBUILD so I haven't a clue why it was there to begin with. Doing a --force upgrade should fix it. I'm still very new to maintaining a package, and I would like to fix any errors in the previous packaging so that it works better overall, so try not to flame me too much :P

TheRealSoup commented on 2013-07-12 11:58

Why was the epoch removed? Once you go epoch; you don't go back.

warning: bittorrent-sync: local (1:1.1.27-1) is newer than mypkgs (1.1.33-1)

Anonymous comment on 2013-07-11 18:12

granted: thanks for letting me know. None of my installations said anything about a newer version, and I've got Windows & Linux installs (it's nice that BtS is there to help keep my Google Drive in sync between Windows and Linux :P ) I'm updating it all now.

DrZingo commented on 2013-07-11 17:26

Two newer versions out:
http://syncapp.bittorrent.com/1.1.30/btsync_x64-1.1.30.tar.gz
http://syncapp.bittorrent.com/1.1.33/btsync_x64-1.1.33.tar.gz
Latest can always be found here:
http://forum.bittorrent.com/topic/19228-latest-sync-build-1133/
Thnx for maintaining.

Anonymous comment on 2013-07-10 20:56

fukawi2 & rukolonist, try `source /usr/share/bittorrent-sync/btsync-makeconfig.sh > ~/.config/btsync/btsync.conf` or if you have a `~/.btsync` dir move it to `~/.config/btsync`... if the `~/.config/btsync/btsync.conf` does not exist it will give that error, so just double-check that is there.

rukolonist commented on 2013-07-10 17:37

I have the same problem as fukawi2.

fukawi2 commented on 2013-07-10 08:31

I stand corrected, it dies after CTRL+C

Starting it manually works fine:
~ $ btsync --config ~/.config/btsync/btsync.conf
BitTorrent Sync forked to background. pid = 8828

fukawi2 commented on 2013-07-10 08:30

btsync@fukawi2.service - BitTorrent Sync service for fukawi2
Loaded: loaded (/usr/lib/systemd/system/btsync@.service; disabled)
Active: failed (Result: timeout) since Wed 2013-07-10 18:29:30 EST; 21s ago
Process: 8724 ExecStart=/usr/bin/btsync --config %h/.config/btsync/btsync.conf (code=exited, status=0/SUCCESS)

fukawi2 commented on 2013-07-10 08:29

For some reason systemctl never returns after starting the user daemon:

~ $ sudo systemctl start btsync@fukawi2
^C

Daemon starts fine and keeps running after pressing CTRL+C.

Anonymous comment on 2013-07-08 21:38

Just updated package. Lots of updates from Lorde! Remember to update your .config/btsync/btsync.conf file as per the upgrade message (or change things to how it suits you).

Anonymous comment on 2013-07-07 17:43

hey, got the comments, ive got a few things that i will be fixing (or will accept as pull reqs if other ppl want to contrib). the running as root thing is one thing, and also the fact that you all now have a /home/user dir, that is probably empty except a .btsync dir with a default config. i dont have my computer with me today, but i will start the changes tonight.

again, pull requests are welcome (even if its just removing the epoch line :P )

emlun commented on 2013-07-07 17:22

By the way, why is the epoch set in the PKGBUILD? I'm new to building AUR packages, and ArchWiki says "Do not use this unless you know what you are doing" about the epoch variable. :)

emlun commented on 2013-07-07 17:14

I've submitted a pull request that allows running the service as any user: "systemctl start btsync@username"

mazzolino commented on 2013-07-07 14:36

The btsync service is installed to run as user "btsync". The btsync user needs "rwx" permissions for the folder to share and "rx" permissions for all of its direct parent folders. You might "chgrp" all those folders to the "btsync" group in order to be able to use those permissions.

It would be easier to manage if the service ran as root. But that might not be a good solution from a security standpoint. Ideally, it would be started by the user itself. But I don't know if we could use systemd for that.

simonsd commented on 2013-07-07 12:57

@teek: what user are you using to run these commands?
You could try creating a debug.txt file with content 'FFFF' in your storage_path (check your config file for the correct path).
This will give you more debug output in the sync.log file which is also located in your storage_path.

zeltak commented on 2013-07-07 11:54

Hi serialhex

thx for picking up the package!
one thing though, i cant see to add local folder (under /home) using the webgui (it says cannot open folder). maybe its me being an idiot but am i missing something?

best

Z

Anonymous comment on 2013-07-06 22:01

Picked up package after Ninja-1 dropped it, new GitHub repo for bugfixes & such: https://github.com/serialhex/bittorrent-sync

Ninja-1 commented on 2013-07-06 16:28

Dropped package because I don't have time to maintain it and don't want to hold it up.

teek commented on 2013-07-05 10:55

(Also, 1.1.27 is out)

teek commented on 2013-07-05 10:54

Stangely:

==
# /usr/bin/btsync --config /etc/btsync.conf
By using this application, you agree to our Privacy Policy and Terms.
http://www.bittorrent.com/legal/privacy
http://www.bittorrent.com/legal/terms-of-use

BitTorrent Sync forked to background. pid = 1612
==

This work perfectly! What could be wrong with the "init-script?"

teek commented on 2013-07-04 18:44

locate btsync.service
/etc/systemd/system/multi-user.target.wants/btsync.service
/usr/lib/systemd/system/btsync.service

Could it be that I have problems because before I had this installed: https://aur.archlinux.org/packages/btsync/
?

teek commented on 2013-07-04 18:34

systemctl start btsync.service
Failed to issue method call: Unit btsync.service failed to load: No such file or directory. See system logs and 'systemctl status btsync.service' for details.

==

xxx systemd[1]: Starting BTSync service...
Jul 04 20:16:54 xxx systemd-coredump[4868]: Process 4858 (btsync) dumped core.
Jul 04 20:26:37 xxx systemd[1]: Stopping BTSync service...
Jul 04 20:26:43 xxx systemd[1]: Stopped BTSync service.

What does it mean?

xjpvictor commented on 2013-06-26 11:07

I would suggest chown /etc/btsync.conf to btsync:btsync and then chmod 600 because it contains password for gui access. It's important when used on a server.

And I get the error "/run/btsync/ not exist". Maybe install a directory as btsync:btsync when installing the package?

Ninja-1 commented on 2013-06-16 18:26

That's what I get for writing that if statement while I'm tired, lol. Updated.

unlimitedbacon commented on 2013-06-16 00:14

/tmp/alpm_FLQeCF/.INSTALL: line 2: [: !=: unary operator expected
chown: invalid user: ‘btsync:btsync’

I think the line in the install script should be...
if [ "$(grep btsync /etc/passwd)" != "" ]; then

Ninja-1 commented on 2013-06-15 17:19

Updated with a check to see if user exists before creating the btsync user.

Package source is on GitHub here now, easier to submit pull requests this way: https://github.com/Ninja-1/bittorrent-sync

alphazo commented on 2013-06-14 15:29

1.1.15 is out!

Ninja-1 commented on 2013-06-14 05:37

You have to set up your config in /etc/btsync.conf and run btsync with your config.

Anonymous comment on 2013-06-14 04:36

I get the following error when trying to run the binary on the command line.
# btsync
Can't open pid file /usr/bin/.sync//sync.pid. No such file or directory

crabman commented on 2013-06-07 20:18

Good point. I used pacmans epoch variable which is recommended for version number changes. The new version string is now "1:1.0.134-1":

https://dl.dropboxusercontent.com/u/62595384/bittorrent-sync-1%3A1.0.134-1.src.tar.gz

I am just testing the bittorrent client right now and problaby wont be using (regularly) it in the future. But ill be happy to assist maintaining it.

Ninja-1 commented on 2013-06-07 16:54

I only see one problem, changing the version number would mean a forced downgrade for those who have it installed.

You've put more work into this than I have, if you'd like to take ownership of this package just let me know and I'll drop it.

crabman commented on 2013-06-07 13:02

@Ninja-1: thanks for the adjustments. However, this package still has some flaws:
- By default, btsync is run as root, which might impose a security risc
- The config file is created in the install file which is really bad (the config is overwritten after every update)
- the service file is named bittorrent-sync while all the other files are named btsync
- there is no version number
- a LICENSE file wasnt packaed, which is mandatory for custom LICENSE packages
- no arm version

I tried to fix that by:
- creating a new user 'btsync' who runs the program. Drawback: 'btsync' must be able to access your files
- adding the LICENSE.txt file
-creating the config file during package creation, now its properly backed up on upgrade and works out of the box
-renaming the systemd-file to "btsync.sercvice"
-adding arm and armv6h versions (for rapberry pi users)

you can find my PKGBUILD here: https://dl.dropboxusercontent.com/u/62595384/bittorrent-sync-1.0.134-1.src.tar.gz

crabman commented on 2013-06-07 12:53

This package stidd has some flaws:
- By default, btsync is run as root, which might impose a security risc
- The config file is created in the install file which is really bad (the config is overwritten after every update)
- the service file is named bittorrent-sync while all the other files are named btsync
- there is no version number
- no arm version
I tried to fix that by:

Ninja-1 commented on 2013-05-20 00:33

When that happens, you can just mark the package out of date. Unfortunately, BitTorrent didn't give us many version numbers.

kaipee commented on 2013-05-19 15:07

Hey guys I'm getting the following erro

==> Validating source files with sha256sums...
bittorrent-sync.install ... Passed
bittorrent-sync.service ... Passed
btsync_x64.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

Ninja-1 commented on 2013-04-29 15:21

After starting, the web ui is at http://localhost:8888/gui

liums commented on 2013-04-27 14:23

I've miss something or with this we can't manage setting from the WebUI ?

liums commented on 2013-04-27 14:12

I've miss something or with this we can't manage setting from the WebUI ?

Ninja-1 commented on 2013-04-24 15:33

Updated as per crabman and maveonair's suggestions.

Anonymous comment on 2013-04-24 12:20

@Crabman
Thanks for your gist, I have changed the configuration to your suggestion.

crabman commented on 2013-04-24 11:24

i changed the systemd service file according to my suggestions:
https://gist.github.com/crabmanX/5451440

crabman commented on 2013-04-24 11:21

i forked maveonairs repo and changed the service file acccording to my suggestions:
https://github.com/crabmanX/bittorrent-sync-archlinux-pkg

Anonymous comment on 2013-04-24 10:22

I modified your package to install bittorrent-sync on Archlinux ARM. Furthermore, I have changed the way to create the btsync.conf according to the suggestion from crabman.

The modifications can be found on https://github.com/maveonair/bittorrent-sync-archlinux-pkg.

crabman commented on 2013-04-24 07:41

Thanks for the PKGBUILD. I noticed some issues:

could you add the "armv6h" architecture for raspberry pi? The corresponding tar.gz is http://btsync.s3-website-us-east-1.amazonaws.com/btsync_arm.tar.gz

Please dont create files in /etc in the install file. You can generate that file during build time and add it to the backup variable: https://wiki.archlinux.org/index.php/Pkgbuild#backup

You should use the --no-daemon option in the .service file. Thats the preferred systemd-way and allows you to remove the Type, ExecStop and ExecReload directives.

Ninja-1 commented on 2013-04-24 02:12

Updated with service file symlink fix. Switched to 'install' from 'mv'.

justin8 commented on 2013-04-24 01:42

Definitely broken; as serialhex said, it is just symlinking the service file to /usr/lib/systemd/system from the build directory...

Anonymous comment on 2013-04-23 22:29

For some reason it symlinks the `bittorrent-sync.service` file instead of moving it. To fix, I installed it completely once, then started the install again, went to where the `bittorrent-sync.service` file is (I use yaourt so under `/tmp/yaourt-my-user`), moved the file to `/usr/lib/systemd/system` as root, made sure permissions were okay, and then cancelled the 2nd install. Hopefully this will be fixed soon so my wonky hack won't be needed!! :D

Thanks for the package though! It's really appreciated!!

Ninja-1 commented on 2013-04-23 20:34

Updated with sample config, systemd service file, and instructions to use them after install/upgrade.

Ninja-1 commented on 2013-04-23 18:40

Yes, I'm working on that.

aaronfischer commented on 2013-04-23 17:32

It would be nice if this package brings a systemd startup script and a default configuration with.