Debian And Ubuntu Server Unofficial Packages For Bittorrent Sync

[AbsolutelyNoOne]

I have the btsync package installed in two machines, one is Ubuntu Server and another is Ubuntu Desktop, both 14.04.

 

The btsync-daemon refuses to keep running after the machines are booted or when I restart the service.

Right after restarting the service, its status is "running". A few seconds after, it's "not running".

When I remove sync.pid and restart the service, it runs normally.

 

This behavior happens on both machines and is happening for some time now.

 

Any tips on this issue?

[tuxpoldo]

I never encountered a problem like this, but I must admit, that I have no 14.04 machines currently in my infrastructure. In any case a question:

 

which PID file are you talking about? The init script of the server package generates two PID file for each instance (one maintained by btsync itself, the other by the daemon manager). The PID file maintained by btsync is normally found in the storage_directory (with the default instance in /var/lib/btsync), the PID file maintained by the daemon manager is stored in /var/run.

 

Which one must be deleted in order to make it work?

[Imnotatroll]

Damn!! I just restarted my Debian Wheezy server:

 

I have started btsync. I bound it to localhost and to have the username "a" with no password.

 

Now when I visit localhost to view the webui it asks me for my username and password. It does NOT allow me to login!! It keeps asking for my username and password multiple times. Even though it is correct.

 

Any ideas as to a fix for this?

 

EDIT:

 

solved.

 

For some reason btsync decided to give me the password 'a' :-s So I logged in with username 'a' and password 'a'. (even though I set no password).

[tuxpoldo]

Damn!! I just restarted my Debian Wheezy server:

...

solved.

For some reason btsync decided to give me the password 'a' :-s So I logged in with username 'a' and password 'a'. (even though I set no password).

Perhaps you have played around with the "Change username or password"-Function of the Web UI. At every restart, the internally stored settings are overwritten by the settings specified in the config file except if you have no credentials configured in the config file. In this case, the internally stored settings will win.

HOWTO

If you have configured your web UI with no authentication and subsequently changed the credentials in the Web UI and forgot it or want to revert to not asking any credentials, you must do the following to reset them:

1. Set the credentials of the Web UI to something known using dpkg-reconfigure btsync
2. Log in into the Web UI using the known credentials.
3. Remove credentials by specifying an empty password in "Change username or password"
4. DO NOT RESTART btsync
5. Remove also the credentials using dpkg-reconfigure btsync

[AbsolutelyNoOne]

Actually, I don't think it's related to a specific version of Ubuntu. When I said it is happening for some time now, I meant to say it happens since the very beginning of the package deployment (I'm an "early adopter" of the packaged btsync). I'm not sure if I began using it with 13.04 or 13.10.

 

The pidfile I'm deleting in order to get btsync working again is the one in storage_directory.

[tuxpoldo]

Actually, I don't think it's related to a specific version of Ubuntu. When I said it is happening for some time now, I meant to say it happens since the very beginning of the package deployment (I'm an "early adopter" of the packaged btsync). I'm not sure if I began using it with 13.04 or 13.10.

 

The pidfile I'm deleting in order to get btsync working again is the one in storage_directory.

 

OK. It's the one maintained by the BitTorrent Sync executable itself. Since you are the only one reporting this kind of problem, I would try to find out, if there are some special environmental situations on your machines like special permissions or similar. Can you reproduce this behaviour on a freshly installed machine? Is there any chance we can have a collaborative session on one of your machines trying to analyze the problem?

[AbsolutelyNoOne]

OK, I'm going to test it in a KVM virtual machine running Ubuntu 14.04.

 

No collaborative session, though. Network policies of my company prevent me from doing this...

[AbsolutelyNoOne]

After installing btsync in a new virtual machine I compared the configuration files. Mine has DAEMON_GID set up, so I decided to remove it and give a try. Now btsync is working as expected. Maybe I misunderstood the meaning of this variable, assigning my username.

 

Also, it wasn't working on the other machine because I scp'ed this "faulty" configuration to save some time.

 

Thanks for the support. Keep this good work up!

[raveur]

Sorry if this has already been asked.   I searched but couldn't find any answer.

Is it possible to create a read-only key so that btsync only sends changes from the Debian box to a Mac and not the other way around?

[tuxpoldo]

Sorry if this has already been asked.   I searched but couldn't find any answer.

Is it possible to create a read-only key so that btsync only sends changes from the Debian box to a Mac and not the other way around?

 

Create the share first on the Debian box. Then you can get the read only key from the web interface. Now you can create the share on the Mac specifying the read only key.

[benplumley]

Something odd has been happening to BTSync on my Pi these last couple of days. After a day or two of running normally, the btsync-daemon process crashes or is killed. I don't know how I'd go about diagnosing this, is this a known bug in a recent release?

 

More detail: I run btsync as root because running it as other accounts gives an "insufficient privileges" error in the Size column of the web UI.

 

Here is the entire /var/log/messages file since the most recent reboot

  GNU nano 2.2.6                                                File: messagesJul  6 06:25:09 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1838" x-info="http://www.rsyslog.com"] rsyslogd was HUPedJul  6 07:48:01 raspberrypi kernel: [56351.953042] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1Jul  6 22:36:32 raspberrypi shutdown[3736]: shutting down for system rebootJul  6 22:36:54 raspberrypi kernel: imklog 5.8.11, log source = /proc/kmsg started.Jul  6 22:36:54 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1863" x-info="http://www.rsyslog.com"] startJul  6 22:36:54 raspberrypi kernel: [    0.000000] Booting Linux on physical CPU 0x0Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Initializing cgroup subsys cpuJul  6 22:36:54 raspberrypi kernel: [    0.000000] Initializing cgroup subsys cpuacctJul  6 22:36:54 raspberrypi kernel: [    0.000000] Linux version 3.12.22+ (dc4@dc4-arm-01) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GC$Jul  6 22:36:54 raspberrypi kernel: [    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387dJul  6 22:36:54 raspberrypi kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cacheJul  6 22:36:54 raspberrypi kernel: [    0.000000] Machine: BCM2708Jul  6 22:36:54 raspberrypi kernel: [    0.000000] cma: CMA: reserved 8 MiB at 0b800000Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Memory policy: ECC disabled, Data cache writebackJul  6 22:36:54 raspberrypi kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 48768Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0x2 bcm2708.serial=0xd5$Jul  6 22:36:54 raspberrypi kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Memory: 179768K/196608K available (4376K kernel code, 238K rwdata, 1340K rodata, 143K init, 701K bss, 16840K reserved)Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Virtual kernel memory layout:Jul  6 22:36:54 raspberrypi kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]     vmalloc : 0xcc800000 - 0xff000000   ( 808 MB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xcc000000   ( 192 MB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]       .text : 0xc0008000 - 0xc059d54c   (5718 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]       .init : 0xc059e000 - 0xc05c1ee4   ( 144 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]       .data : 0xc05c2000 - 0xc05fd900   ( 239 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000]        .bss : 0xc05fd90c - 0xc06ad0f8   ( 702 kB)Jul  6 22:36:54 raspberrypi kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1Jul  6 22:36:54 raspberrypi kernel: [    0.000000] Preemptible hierarchical RCU implementation.Jul  6 22:36:54 raspberrypi kernel: [    0.000000] NR_IRQS:394Jul  6 22:36:54 raspberrypi kernel: [    0.000000] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 4294967msJul  6 22:36:54 raspberrypi kernel: [    0.000000] Switching to timer-based delay loopJul  6 22:36:54 raspberrypi kernel: [    0.000000] Console: colour dummy device 80x30Jul  6 22:36:54 raspberrypi kernel: [    0.000000] console [tty1] enabledJul  6 22:36:54 raspberrypi kernel: [    0.001275] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)Jul  6 22:36:54 raspberrypi kernel: [    0.001337] pid_max: default: 32768 minimum: 301Jul  6 22:36:54 raspberrypi kernel: [    0.001825] Mount-cache hash table entries: 512Jul  6 22:36:54 raspberrypi kernel: [    0.002654] Initializing cgroup subsys memoryJul  6 22:36:54 raspberrypi kernel: [    0.002762] Initializing cgroup subsys devicesJul  6 22:36:54 raspberrypi kernel: [    0.002800] Initializing cgroup subsys freezerJul  6 22:36:54 raspberrypi kernel: [    0.002833] Initializing cgroup subsys blkioJul  6 22:36:54 raspberrypi kernel: [    0.002978] CPU: Testing write buffer coherency: okJul  6 22:36:54 raspberrypi kernel: [    0.003452] Setting up static identity map for 0xc0427670 - 0xc04276ccJul  6 22:36:54 raspberrypi kernel: [    0.005368] devtmpfs: initializedJul  6 22:36:54 raspberrypi kernel: [    0.022156] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5Jul  6 22:36:54 raspberrypi kernel: [    0.023758] NET: Registered protocol family 16Jul  6 22:36:54 raspberrypi kernel: [    0.029150] DMA: preallocated 4096 KiB pool for atomic coherent allocationsJul  6 22:36:54 raspberrypi kernel: [    0.029823] cpuidle: using governor ladderJul  6 22:36:54 raspberrypi kernel: [    0.029150] DMA: preallocated 4096 KiB pool for atomic coherent allocationsJul  6 22:36:54 raspberrypi kernel: [    0.029823] cpuidle: using governor ladderJul  6 22:36:54 raspberrypi kernel: [    0.029870] cpuidle: using governor menuJul  6 22:36:54 raspberrypi kernel: [    0.030506] bcm2708.uart_clock = 0Jul  6 22:36:54 raspberrypi kernel: [    0.032329] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.Jul  6 22:36:54 raspberrypi kernel: [    0.032382] hw-breakpoint: maximum watchpoint size is 4 bytes.Jul  6 22:36:54 raspberrypi kernel: [    0.032418] mailbox: Broadcom VideoCore Mailbox driverJul  6 22:36:54 raspberrypi kernel: [    0.032518] bcm2708_vcio: mailbox at f200b880Jul  6 22:36:54 raspberrypi kernel: [    0.032625] bcm_power: Broadcom power driverJul  6 22:36:54 raspberrypi kernel: [    0.032663] bcm_power_open() -> 0Jul  6 22:36:54 raspberrypi kernel: [    0.032690] bcm_power_request(0, 8)Jul  6 22:36:54 raspberrypi kernel: [    0.533417] bcm_mailbox_read -> 00000080, 0Jul  6 22:36:54 raspberrypi kernel: [    0.533457] bcm_power_request -> 0Jul  6 22:36:54 raspberrypi kernel: [    0.533690] Serial: AMBA PL011 UART driverJul  6 22:36:54 raspberrypi kernel: [    0.533861] dev:f1: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev3Jul  6 22:36:54 raspberrypi kernel: [    0.893743] console [ttyAMA0] enabledJul  6 22:36:54 raspberrypi kernel: [    0.920685] bio: create slab <bio-0> at 0Jul  6 22:36:54 raspberrypi kernel: [    0.926209] SCSI subsystem initializedJul  6 22:36:54 raspberrypi kernel: [    0.930206] usbcore: registered new interface driver usbfsJul  6 22:36:54 raspberrypi kernel: [    0.935910] usbcore: registered new interface driver hubJul  6 22:36:54 raspberrypi kernel: [    0.941473] usbcore: registered new device driver usbJul  6 22:36:54 raspberrypi kernel: [    0.948139] Switched to clocksource stcJul  6 22:36:54 raspberrypi kernel: [    0.952385] FS-Cache: LoadedJul  6 22:36:54 raspberrypi kernel: [    0.955540] CacheFiles: LoadedJul  6 22:36:54 raspberrypi kernel: [    0.971297] NET: Registered protocol family 2Jul  6 22:36:54 raspberrypi kernel: [    0.976797] TCP established hash table entries: 2048 (order: 2, 16384 bytes)Jul  6 22:36:54 raspberrypi kernel: [    0.984150] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)Jul  6 22:36:54 raspberrypi kernel: [    0.990603] TCP: Hash tables configured (established 2048 bind 2048)Jul  6 22:36:54 raspberrypi kernel: [    0.997054] TCP: reno registeredJul  6 22:36:54 raspberrypi kernel: [    1.000355] UDP hash table entries: 256 (order: 0, 4096 bytes)Jul  6 22:36:54 raspberrypi kernel: [    1.006228] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)Jul  6 22:36:54 raspberrypi kernel: [    1.012987] NET: Registered protocol family 1Jul  6 22:36:54 raspberrypi kernel: [    1.017911] RPC: Registered named UNIX socket transport module.Jul  6 22:36:54 raspberrypi kernel: [    1.023968] RPC: Registered udp transport module.Jul  6 22:36:54 raspberrypi kernel: [    1.028728] RPC: Registered tcp transport module.Jul  6 22:36:54 raspberrypi kernel: [    1.033447] RPC: Registered tcp NFSv4.1 backchannel transport module.Jul  6 22:36:54 raspberrypi kernel: [    1.040858] bcm2708_dma: DMA manager at f2007000Jul  6 22:36:54 raspberrypi kernel: [    1.045597] bcm2708_gpio: bcm2708_gpio_probe c05cfed0Jul  6 22:36:54 raspberrypi kernel: [    1.051170] vc-mem: phys_addr:0x00000000 mem_base=0x0ec00000 mem_size:0x10000000(256 MiB)Jul  6 22:36:54 raspberrypi kernel: [    1.060782] audit: initializing netlink socket (disabled)Jul  6 22:36:54 raspberrypi kernel: [    1.066285] type=2000 audit(0.910:1): initializedJul  6 22:36:54 raspberrypi kernel: [    1.232948] VFS: Disk quotas dquot_6.5.2Jul  6 22:36:54 raspberrypi kernel: [    1.237220] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)Jul  6 22:36:54 raspberrypi kernel: [    1.246215] FS-Cache: Netfs 'nfs' registered for cachingJul  6 22:36:54 raspberrypi kernel: [    1.253177] NFS: Registering the id_resolver key typeJul  6 22:36:54 raspberrypi kernel: [    1.258461] Key type id_resolver registeredJul  6 22:36:54 raspberrypi kernel: [    1.262669] Key type id_legacy registeredJul  6 22:36:54 raspberrypi kernel: [    1.267432] msgmni has been set to 367Jul  6 22:36:54 raspberrypi kernel: [    1.273237] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)Jul  6 22:36:54 raspberrypi kernel: [    1.281099] io scheduler noop registeredJul  6 22:36:54 raspberrypi kernel: [    1.285053] io scheduler deadline registered (default)Jul  6 22:36:54 raspberrypi kernel: [    1.281099] io scheduler noop registeredJul  6 22:36:54 raspberrypi kernel: [    1.285053] io scheduler deadline registered (default)Jul  6 22:36:54 raspberrypi kernel: [    1.290647] io scheduler cfq registeredJul  6 22:36:54 raspberrypi kernel: [    1.295804] BCM2708FB: allocated DMA memory 4bc00000Jul  6 22:36:54 raspberrypi kernel: [    1.300988] BCM2708FB: allocated DMA channel 0 @ f2007000Jul  6 22:36:54 raspberrypi kernel: [    1.326513] Console: switching to colour frame buffer device 82x26Jul  6 22:36:54 raspberrypi kernel: [    1.336698] uart-pl011 dev:f1: no DMA platform dataJul  6 22:36:54 raspberrypi kernel: [    1.343128] kgdb: Registered I/O driver kgdboc.Jul  6 22:36:54 raspberrypi kernel: [    1.349758] vc-cma: Videocore CMA driverJul  6 22:36:54 raspberrypi kernel: [    1.355040] vc-cma: vc_cma_base      = 0x00000000Jul  6 22:36:54 raspberrypi kernel: [    1.361071] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)Jul  6 22:36:54 raspberrypi kernel: [    1.367725] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)Jul  6 22:36:54 raspberrypi kernel: [    1.383825] brd: module loadedJul  6 22:36:54 raspberrypi kernel: [    1.393502] loop: module loadedJul  6 22:36:54 raspberrypi kernel: [    1.398223] vchiq: vchiq_init_state: slot_zero = 0xcb800000, is_master = 0Jul  6 22:36:54 raspberrypi kernel: [    1.407317] Loading iSCSI transport class v2.0-870.Jul  6 22:36:54 raspberrypi kernel: [    1.414786] usbcore: registered new interface driver smsc95xxJul  6 22:36:54 raspberrypi kernel: [    1.422363] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)Jul  6 22:36:54 raspberrypi kernel: [    1.629655] Core Release: 2.80aJul  6 22:36:54 raspberrypi kernel: [    1.634069] Setting default values for core paramsJul  6 22:36:54 raspberrypi kernel: [    1.640158] Finished setting default values for core paramsJul  6 22:36:54 raspberrypi kernel: [    1.847131] Using Buffer DMA modeJul  6 22:36:54 raspberrypi kernel: [    1.851726] Periodic Transfer Interrupt Enhancement - disabledJul  6 22:36:54 raspberrypi kernel: [    1.858844] Multiprocessor Interrupt Enhancement - disabledJul  6 22:36:54 raspberrypi kernel: [    1.865662] OTG VER PARAM: 0, OTG VER FLAG: 0Jul  6 22:36:54 raspberrypi kernel: [    1.871305] Dedicated Tx FIFOs modeJul  6 22:36:54 raspberrypi kernel: [    1.876352] WARN::dwc_otg_hcd_init:1042: FIQ DMA bounce buffers: virt = 0xcbc14000 dma = 0x4bc14000 len=9024Jul  6 22:36:54 raspberrypi kernel: [    1.888799] FIQ FSM acceleration enabled for :Jul  6 22:36:54 raspberrypi kernel: [    1.888799] Non-periodic Split TransactionsJul  6 22:36:54 raspberrypi kernel: [    1.888799] Periodic Split TransactionsJul  6 22:36:54 raspberrypi kernel: [    1.888799] High-Speed Isochronous EndpointsJul  6 22:36:54 raspberrypi kernel: [    1.910811] WARN::hcd_init:473: FIQ at 0xc03080ccJul  6 22:36:54 raspberrypi kernel: [    1.916879] WARN::hcd_init:474: FIQ ASM at 0xc0308348 length 36Jul  6 22:36:54 raspberrypi kernel: [    1.924210] WARN::hcd_init:500: MPHI regs_base at 0xcc806000Jul  6 22:36:54 raspberrypi kernel: [    1.931252] dwc_otg bcm2708_usb: DWC OTG ControllerJul  6 22:36:54 raspberrypi kernel: [    1.937483] dwc_otg bcm2708_usb: new USB bus registered, assigned bus number 1Jul  6 22:36:54 raspberrypi kernel: [    1.946134] dwc_otg bcm2708_usb: irq 32, io mem 0x00000000Jul  6 22:36:54 raspberrypi kernel: [    1.953009] Init: Port Power? op_state=1Jul  6 22:36:54 raspberrypi kernel: [    1.958259] Init: Power Port (0)Jul  6 22:36:54 raspberrypi kernel: [    1.963019] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002Jul  6 22:36:54 raspberrypi kernel: [    1.971188] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1Jul  6 22:36:54 raspberrypi kernel: [    1.979764] usb usb1: Product: DWC OTG ControllerJul  6 22:36:54 raspberrypi kernel: [    1.985752] usb usb1: Manufacturer: Linux 3.12.22+ dwc_otg_hcdJul  6 22:36:54 raspberrypi kernel: [    1.992899] usb usb1: SerialNumber: bcm2708_usbJul  6 22:36:54 raspberrypi kernel: [    1.999577] hub 1-0:1.0: USB hub foundJul  6 22:36:54 raspberrypi kernel: [    2.004722] hub 1-0:1.0: 1 port detectedJul  6 22:36:54 raspberrypi kernel: [    2.010913] usbcore: registered new interface driver usb-storageJul  6 22:36:54 raspberrypi kernel: [    2.018664] mousedev: PS/2 mouse device common for all miceJul  6 22:36:54 raspberrypi kernel: [    2.026122] bcm2835-cpufreq: min=700000 max=700000 cur=700000Jul  6 22:36:54 raspberrypi kernel: [    2.033344] bcm2835-cpufreq: switching to governor powersaveJul  6 22:36:54 raspberrypi kernel: [    2.040354] bcm2835-cpufreq: switching to governor powersaveJul  6 22:36:54 raspberrypi kernel: [    2.033344] bcm2835-cpufreq: switching to governor powersaveJul  6 22:36:54 raspberrypi kernel: [    2.040354] bcm2835-cpufreq: switching to governor powersaveJul  6 22:36:54 raspberrypi kernel: [    2.047356] sdhci: Secure Digital Host Controller Interface driverJul  6 22:36:54 raspberrypi kernel: [    2.054827] sdhci: Copyright(c) Pierre OssmanJul  6 22:36:54 raspberrypi kernel: [    2.060544] sdhci: Enable low-latency modeJul  6 22:36:54 raspberrypi kernel: [    2.108384] mmc0: SDHCI controller on BCM2708_Arasan [platform] using platform's DMAJul  6 22:36:54 raspberrypi kernel: [    2.118936] mmc0: BCM2708 SDHC host at 0x20300000 DMA 2 IRQ 77Jul  6 22:36:54 raspberrypi kernel: [    2.126189] sdhci-pltfm: SDHCI platform and OF driver helperJul  6 22:36:54 raspberrypi kernel: [    2.133359] ledtrig-cpu: registered to indicate activity on CPUsJul  6 22:36:54 raspberrypi kernel: [    2.143012] hidraw: raw HID events driver (C) Jiri KosinaJul  6 22:36:54 raspberrypi kernel: [    2.157364] usbcore: registered new interface driver usbhidJul  6 22:36:54 raspberrypi kernel: [    2.164443] usbhid: USB HID core driverJul  6 22:36:54 raspberrypi kernel: [    2.174337] TCP: cubic registeredJul  6 22:36:54 raspberrypi kernel: [    2.181126] Initializing XFRM netlink socketJul  6 22:36:54 raspberrypi kernel: [    2.188876] NET: Registered protocol family 17Jul  6 22:36:54 raspberrypi kernel: [    2.194890] Key type dns_resolver registeredJul  6 22:36:54 raspberrypi kernel: [    2.208372] Indeed it is in host mode hprt0 = 00021501Jul  6 22:36:54 raspberrypi kernel: [    2.218334] registered taskstats version 1Jul  6 22:36:54 raspberrypi kernel: [    2.228849] Waiting for root device /dev/mmcblk0p2...Jul  6 22:36:54 raspberrypi kernel: [    2.258284] mmc0: new high speed SDHC card at address 968fJul  6 22:36:54 raspberrypi kernel: [    2.278418] mmcblk0: mmc0:968f SU08G 7.40 GiBJul  6 22:36:54 raspberrypi kernel: [    2.286351]  mmcblk0: p1 p2Jul  6 22:36:54 raspberrypi kernel: [    2.355308] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)Jul  6 22:36:54 raspberrypi kernel: [    2.366532] VFS: Mounted root (ext4 filesystem) on device 179:2.Jul  6 22:36:54 raspberrypi kernel: [    2.384724] devtmpfs: mountedJul  6 22:36:54 raspberrypi kernel: [    2.389682] Freeing unused kernel memory: 140K (c059e000 - c05c1000)Jul  6 22:36:54 raspberrypi kernel: [    2.418302] usb 1-1: new high-speed USB device number 2 using dwc_otgJul  6 22:36:54 raspberrypi kernel: [    2.426414] Indeed it is in host mode hprt0 = 00001101Jul  6 22:36:54 raspberrypi kernel: [    2.628700] usb 1-1: New USB device found, idVendor=0424, idProduct=9512Jul  6 22:36:54 raspberrypi kernel: [    2.637225] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0Jul  6 22:36:54 raspberrypi kernel: [    2.648339] hub 1-1:1.0: USB hub foundJul  6 22:36:54 raspberrypi kernel: [    2.653735] hub 1-1:1.0: 3 ports detectedJul  6 22:36:54 raspberrypi kernel: [    2.938447] usb 1-1.1: new high-speed USB device number 3 using dwc_otgJul  6 22:36:54 raspberrypi kernel: [    3.058825] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00Jul  6 22:36:54 raspberrypi kernel: [    3.067344] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0Jul  6 22:36:54 raspberrypi kernel: [    3.093512] smsc95xx v1.0.4Jul  6 22:36:54 raspberrypi kernel: [    3.163580] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:97:3d:3bJul  6 22:36:54 raspberrypi kernel: [    6.020590] bcm2708-i2s bcm2708-i2s.0: Failed to create debugfs directoryJul  6 22:36:54 raspberrypi kernel: [   14.693238] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)Jul  6 22:36:54 raspberrypi kernel: [   15.506935] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)Jul  6 22:36:54 raspberrypi kernel: [   21.080523] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.Jul  6 22:36:54 raspberrypi kernel: [   23.861144] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeupJul  6 22:36:54 raspberrypi kernel: [   25.424891] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1Jul  6 22:36:58 raspberrypi btsync.debconf-default: btsync instance debconf-default started successfullyJul  6 22:36:59 raspberrypi kernel: [   31.963469] Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k SSFSJul  7 06:25:07 raspberrypi rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1863" x-info="http://www.rsyslog.com"] rsyslogd was HUPed

[g3blv]

Hi,

 

I have installed btsync-user from the PPA. It is up and running fine and I can access through the Web GUI. With older versions I was able to connect to the Web GUI from other computers than the computer btsync-user was running on. Have that been disabled now?

[tuxpoldo]

I have installed btsync-user from the PPA. It is up and running fine and I can access through the Web GUI. With older versions I was able to connect to the Web GUI from other computers than the computer btsync-user was running on. Have that been disabled now?

 

Are you sure? The standard installation of btsync-user (BTW: Issues regarding btsync-user have their own thread)  has never allowed to connect to the Web UI from other computers. But there is a way you can achieve that, of you want: you can create a a custom configuration file that allows connections from any computer. See the initial posting of the btsync-user thread for more information on how to create a custom configuration file.

[paulpreston85]

Sorry if this is in the wrong place but I accidentally removed BTSync from startup and can't get it to auto start.

 

I've tried creating a new startup item with the command btsync-core (not sure if that's right) and other various commands but can't get anything to work. 

The box to tick 'start  btsync when Linux starts' is greyed out in the GUI so I can't use that method.

I've tried re-installing but it doesn't create the startup item. It also seems to remember my previous synced folders so there must be some config file stored somewhere that I can't find. Can someone please help??

Running btsync-gui on Ubuntu 14.04

I'm very new at Linux so please be kind

[tuxpoldo]

Something odd has been happening to BTSync on my Pi these last couple of days. After a day or two of running normally, the btsync-daemon process crashes or is killed. I don't know how I'd go about diagnosing this, is this a known bug in a recent release?

I also noticed that the current version of btsync sometimes crashes - but this has never happened with one of my Linux servers. The crashes were mainly happening on my Mac OSX machines. If you would like to send some more information to the btsync developers, you should take the btsync log file and not the syslog since you will not find any useful information there. You can find the log file in the storage_path and it is named sync.log. See this topic for more details.

 

More detail: I run btsync as root because running it as other accounts gives an "insufficient privileges" error in the Size column of the web UI.

I suppose that the the credentials btsync was using previously had not the required access privileges to the folders you were sharing. One solution is to run it as root (but in this case also all newly created files and directories will be owned by root), the other solution is to adjust the access privileges of the folders to allow the user btsync is running to do what it needs to do.

[kroe]

For me in the very end it failed:

 

/var/lib/dpkg/info/btsync-common.postinst: line 21: 18625 Killed                  ${DAEMON} --help > /dev/null 2> /dev/null

/var/lib/dpkg/info/btsync-common.postinst: line 21: 18629 Killed                  ${DAEMON} --dump-sample-config >> ${SAMPLECFG}

Setting up btsync (1.3.1-1) ...

Adding system user `btsync' (UID 105) ...

Adding new group `btsync' (GID 108) ...

Adding new user `btsync' (UID 105) with group `btsync' ...

Not creating home directory `/var/lib/btsync'.

[....] Autostarting btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 18804 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to start btsync instance debconf-default - please check the configuration file /etc/btsync/debconf-default.conf ... failed!

Did it again, but using "root" as user for btsync, and it failed again:

 

fatty:~# `which sudo` dpkg-reconfigure btsync

[....] Stopping btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 19794 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to stop btsync instance debconf-default ... failed!

[....] Autostarting btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 20288 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to start btsync instance debconf-default - please check the configuration file /etc/btsync/debconf-default.conf ... failed!

[benplumley]

I also noticed that the current version of btsync sometimes crashes - but this has never happened with one of my Linux servers. The crashes were mainly happening on my Mac OSX machines. If you would like to send some more information to the btsync developers, you should take the btsync log file and not the syslog since you will not find any useful information there. You can find the log file in the storage_path and it is named sync.log. See this topic for more details.

I'm trying to take a debug log but it's all different since this is a package. They say 

 

 

create file debug.txt with contents of FFFF in the .sync folder. You can find the .sync folder in the same directory where the btsync binary is located

but on my system, btsync-daemon (the btsync binary) is the only file in its directory, there is no .sync folder. Where do I put debug.txt and where will I find sync.log?

[paulpreston85]

Sorry if this is in the wrong place but I accidentally removed BTSync from startup and can't get it to auto start.

 

I've tried creating a new startup item with the command btsync-core (not sure if that's right) and other various commands but can't get anything to work. 

The box to tick 'start  btsync when Linux starts' is greyed out in the GUI so I can't use that method.

I've tried re-installing but it doesn't create the startup item. It also seems to remember my previous synced folders so there must be some config file stored somewhere that I can't find. Can someone please help??

Running btsync-gui on Ubuntu 14.04

I'm very new at Linux so please be kind

Got it guys. command was btsync-gui

 

[benplumley]

I also noticed that the current version of btsync sometimes crashes - but this has never happened with one of my Linux servers. The crashes were mainly happening on my Mac OSX machines. If you would like to send some more information to the btsync developers, you should take the btsync log file and not the syslog since you will not find any useful information there. You can find the log file in the storage_path and it is named sync.log. See this topic for more details.

They've told me the opposite, that it's a problem with your package not their binaries. Oh well, it looks like I'm the only one with the issue anyway so I'll go back to using the official builds.

[jcouture]

Thanks for maintaining this package, it is simply awesome!

 

I recently got my hands on a Mac Mini G4 (PowerPC) on which I promptly installed Ubuntu 14.04 (server). I proceeded to add your PPA and did a `sudo apt-get update`. I then tried to install btsync using `sudo apt-get install btsync` and got the following output:

Reading package lists... DoneBuilding dependency treeReading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help resolve the situation:The following packages have unmet dependencies: btsync : Depends: btsync-common (>= 1.3.67-1) but it is not installableE: Unable to correct problems, you have held broken packages.

Would it be because the `btsync-common` package is not PowerPC-compatible?

 

If so, how can I help you to make it compatible? I would love to be able to use your package!

 

Best regards,

[tuxpoldo]

Hi Folks,

 

just back from holiday. I see a lot of new posts here - let's try to give some advice...

 

 

 

For me in the very end it failed:

 

/var/lib/dpkg/info/btsync-common.postinst: line 21: 18625 Killed                  ${DAEMON} --help > /dev/null 2> /dev/null

/var/lib/dpkg/info/btsync-common.postinst: line 21: 18629 Killed                  ${DAEMON} --dump-sample-config >> ${SAMPLECFG}

Setting up btsync (1.3.1-1) ...

Adding system user `btsync' (UID 105) ...

Adding new group `btsync' (GID 108) ...

Adding new user `btsync' (UID 105) with group `btsync' ...

Not creating home directory `/var/lib/btsync'.

[....] Autostarting btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 18804 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to start btsync instance debconf-default - please check the configuration file /etc/btsync/debconf-default.conf ... failed!

Did it again, but using "root" as user for btsync, and it failed again:

 

fatty:~# `which sudo` dpkg-reconfigure btsync

[....] Stopping btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 19794 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to stop btsync instance debconf-default ... failed!

[....] Autostarting btsync instance 'debconf-default':/etc/init.d/btsync: line 230: 20288 Killed                  $DAEMON --help > /dev/null 2> /dev/null

[FAIL] Failed to start btsync instance debconf-default - please check the configuration file /etc/btsync/debconf-default.conf ... failed!

 

 

OK - The line numbers in the error messages definitively are wrong. But it seems that the error occurs every time a line similar to

 

if ! $DAEMON --help > /dev/null 2> /dev/null; then

 

or

 

if [ -f /usr/lib/btsync-common/btsync-core-i686 ]; then

 

is executed. This indicates that there is something different as in any other debian-derived systems it was tested before. Perhaps a different default shell? Please tell us:

 

1. Which specific distribution are you using?
2. Which shell are you using? Is this also set as the system default shell?

I'm trying to take a debug log but it's all different since this is a package. They say 

but on my system, btsync-daemon (the btsync binary) is the only file in its directory, there is no .sync folder. Where do I put debug.txt and where will I find sync.log?

 

The .btsync directory is the default storage_path is no configuration file is present. This is not the case when installing the btsync package. Each instance must have a unique storage_path that will be defined in the corresponding configuration file. If you have a default instance configured by debconf, the storage_path is /var/lib/btsync

Thanks for maintaining this package, it is simply awesome!

 

I recently got my hands on a Mac Mini G4 (PowerPC) on which I promptly installed Ubuntu 14.04 (server). I proceeded to add your PPA and did a `sudo apt-get update`. I then tried to install btsync using `sudo apt-get install btsync` and got the following output:

Reading package lists... DoneBuilding dependency treeReading state information... DoneSome packages could not be installed. This may mean that you haverequested an impossible situation or if you are using the unstabledistribution that some required packages have not yet been createdor been moved out of Incoming.The following information may help resolve the situation:The following packages have unmet dependencies: btsync : Depends: btsync-common (>= 1.3.67-1) but it is not installableE: Unable to correct problems, you have held broken packages.

Would it be because the `btsync-common` package is not PowerPC-compatible?

 

If so, how can I help you to make it compatible? I would love to be able to use your package!

 

Best regards,

 

Which repository are you using? The PPA does not provide support for PowerPC, so there is no btsync-common package for PowerPC - that's the reason for the error message. All other packages are platform independent, since they contain only scripts or interpreted/jitted languages.

 

If you want to install the PowerPC version, you have to use the YeaSoft-Repository (See initial posting of this thread).

 

Question: where do you get an Ubuntu 14.04 for PowerPC from? On the download page I see that only amd64 is supported....

[trevellyan]

Question: where do you get an Ubuntu 14.04 for PowerPC from? On the download page I see that only amd64 is supported....

 

Go to http://www.ubuntu.com/download/alternative-downloads, then scroll down to Other Images and choose a mirror. You should find PPC listed there.

[tuxpoldo]

Go to http://www.ubuntu.com/download/alternative-downloads, then scroll down to Other Images and choose a mirror. You should find PPC listed there.

 

I tried one of the mirrors ( http://de.releases.ubuntu.com/trusty/ ) but I see no PPC there. Am I visually impaired? In any case you have to use the YeaSoft Repository since the LaunchPad PPA does not provide binaries for PPC.

[trevellyan]

This mirror has PPC:

http://mirror.anl.gov/pub/ubuntu-iso/DVDs/ubuntu/14.04.1/release/

[tuxpoldo]

This mirror has PPC:

http://mirror.anl.gov/pub/ubuntu-iso/DVDs/ubuntu/14.04.1/release/

 

Interesting. And did you solve the missing package problem?