knireis

Members
  • Posts

    152
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by knireis

  1. That's great, since I was not able to create a builder environment for jessie (there is still an error with debootstrap).

    It runs on a headless server. I use the desktop version on my pc's running LMDE without issues.

    I restarted btsync and it seems to run fine but no return on netsat command:

    root@fileserver:~# service btsync restart

    [....] Stopping P2P file synchronisation daemon(s)...[....] Stopping btsync in[ ok e 'debconf-default':.

    [ ok ] Stopping btsync instance 'user':.

    [....] Starting P2P file synchronisation daemon(s)...[....] Autostarting btsync instance 'debconf-default':[....] Autostarting btsync instance 'user':root@fileserver:~# netstat -tlpen | grep btsync

    root@fileserver:~#

  2. SID installs btsync fine.

    Now my last question, how to run it as user and make it available with gui.

    I made following config file in /etc/btsync with name user.sierink.conf



    //!/usr/sbin/btsync-daemon --config
    //
    // (c) 2013 YeaSoft Int'l - Leo Moll
    //
    // This btsync configuration file shows how to configure a btsync
    // instance running under specific user credentials.
    // Credentials can be embeded in the filename of the configuration
    // file:
    //
    // filename.conf - no credential specified. The
    // instance will run as root:root
    // filename.<user>.conf - Instance will run as <user> with
    // the primary group of <user>
    // filename.<user>.<group>.conf - Instance will run as user:group
    //
    // This example will launch an instance running under the credentials
    // of the user "jdoe"
    // The internal data of the btsync daemon will be written in
    // /home/jdoe/.btsync
    // Since the web gui is disabled, the user cannot configure anything.
    // The instance offers one replicated directory located in
    // /home/jdoe/syncdir
    //
    {
    "device_name": "fileserver",
    "listening_port" : 0,
    "storage_path" : "/home/sierink/.btsync",
    "check_for_updates" : false,
    "use_upnp" : true,
    "download_limit" : 0,
    "upload_limit" : 0,
    "webui" :
    {
    "listen" : "192.168.1.17:9999"
    }
    }


  3. One thing more: please send me the result of executing the following commands (sorry - I have no jessie installed):


    basename /var/run/btsync.debconf-default.pid | cut -c8-
    BASENAME=$(basename /var/run/btsync.debconf-default.pid | cut -c8-); echo ${BASENAME%%.pid}

    root@fileserver:~# basename /var/run/btsync.debconf-default.pid | cut -c8-

    debconf-default.pid

    root@fileserver:~# BASENAME=$(basename /var/run/btsync.debconf-default.pid | cut -c8-); echo ${BASENAME%%.pid}

    debconf-default

  4. Please tell me if this has solved your problem. In the meantime I will try to find out, why the script tries to delete the wrong pid-file under certain circumstances.

    I can now start and stop it, the pidfile can be from another instance of btsync i used before installing your package.

    I guess btsync was not running because the grep command gave:

    root@fileserver:~# ps ax | grep btsync

    31175 pts/0 S+ 0:00 grep btsync

  5. One more please:


    ls -la /var/run/

    I suppose, that your instance of btsync was not running when you entered the command?

    root@fileserver:~# ls -la /var/run/

    total 48

    drwxr-xr-x 12 root root 540 May 27 08:05 .

    drwxr-xr-x 21 root root 4096 May 26 21:16 ..

    -rw-r--r-- 1 root root 5 May 26 16:50 atd.pid

    -rw-r--r-- 1 root root 5 May 26 19:14 btsync.debconf-default.pid

    -rw-r--r-- 1 root root 5 May 26 16:50 crond.pid

    ---------- 1 root root 0 May 26 16:50 crond.reboot

    drwxr-xr-x 2 messagebus messagebus 80 May 26 16:50 dbus

    prw------- 1 root root 0 May 26 16:50 initctl

    drwxrwxrwt 2 root root 60 May 26 21:20 lock

    -rw-r--r-- 1 root root 73 May 26 16:50 motd.dynamic

    drwxr-xr-x 2 root root 80 May 26 21:29 mount

    drwxr-xr-x 2 root root 60 May 26 16:50 network

    drwxr-xr-x 2 root root 60 May 26 22:28 pound

    -rw------- 1 root root 6 May 26 22:28 pound.pid

    drwxr-xr-x 2 root root 80 May 26 16:50 rpcbind

    -r--r--r-- 1 root root 0 May 26 16:50 rpcbind.lock

    -rw-r--r-- 1 root root 4 May 26 16:50 rpcbind.pid

    srw-rw-rw- 1 root root 0 May 26 16:50 rpcbind.sock

    -rw-r--r-- 1 statd nogroup 6 May 26 21:29 rpc.statd.pid

    -rw-r--r-- 1 root root 5 May 26 16:50 rsyslogd.pid

    drwxr-xr-x 2 root root 340 May 27 06:25 samba

    drwxr-xr-x 2 root root 100 May 26 21:29 sendsigs.omit.d

    drwxrwxrwt 2 root root 60 May 26 16:50 shm

    -rw------- 1 root root 5 May 26 16:50 sm-notify.pid

    drwxr-xr-x 2 root root 40 May 26 16:50 sshd

    -rw-r--r-- 1 root root 5 May 26 16:50 sshd.pid

    -rw-rw-r-- 1 root utmp 2304 May 27 13:07 utmp

    Sorry, don't know if it runs. There is no webinterface.

  6. OK. As I can see, the stop routine is trying to stop two intances (one named 'btsync', the other named 'debconf-default.pid'), but according to your config files, you should only have the instance named 'btsync' running. Can you please show me the contents of your /var/run directory?

    root@fileserver:~# ls -la /var/run

    lrwxrwxrwx 1 sierink sierink 4 Apr 8 21:49 /var/run -> /run

    root@fileserver:~# ls -la /var/run/btsync.*.pid

    -rw-r--r-- 1 root root 5 May 26 19:14 /var/run/btsync.debconf-default.pid

  7. That's really interesting. I am trying to reproduce the error, but I am not able to do so. It seems that the decomposition of the name does not work correctly:

    pi btsync 1.0.134-4~wheezy i386 Private network P2P file synchronisation daemon(s)

    root@fileserver:~# service btsync stop

    [ ok ] Stopping P2P file synchronisation daemon(s)...[....] Stopping btsync instance 'btsync':.

    [....] Stopping btsync instance 'debconf-default.pid':rm: cannot remove `/var/run/btsync.debconf-default.pid.pid': No such file or directory

    root@fileserver:~# ls -la /etc/btsync

    total 16

    drwxr-xr-x 3 root root 4096 May 26 19:39 .

    drwxr-xr-x 70 root root 4096 May 26 21:44 ..

    -rw-r--r-- 1 root root 1185 May 26 19:39 btsync.sierink.conf

    drwxr-xr-x 2 root root 4096 May 26 19:30 samples

    Your upgrade is on ubuntu, mine on debian jessie, with the btsync wheezy package (there seems to be no jessie package yet).

  8. I updated my server to debian 'jessie'. Some packages updated fine but others don't upgrade because the system wants to remove btsync. However the removing gives an error:

    Reading changelogs... Done

    Extracting templates from packages: 100%

    Preconfiguring packages ...

    (Reading database ... 45729 files and directories currently installed.)

    Removing btsync ...

    [ ok ] Stopping P2P file synchronisation daemon(s)...[....] Stopping btsync instance 'btsync':.

    [....] Stopping btsync instance 'debconf-default.pid':rm: cannot remove `/var/run/btsync.debconf-default.pid.pid': No such file or directory

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

    dpkg: error processing btsync (--purge):

    subprocess installed pre-removal script returned error exit status 1

    [....] Starting P2P file synchronisation daemon(s)...[....] Autostarting btsync instance 'btsync':Errors were encountered while processing:

    btsync

    E: Sub-process /usr/bin/dpkg returned an error code (1)

    E: Some packages could not be upgraded.

  9. I tried this version on debian wheezy, first i purged the previous 'server' version. It seems to install fine, but during install there is not the configuration steps. It does not start either.

    As i just noticed your message above i tried to run the commands but i get an error:

    laptop ~ # /usr/lib/btsync/btsync-agent --config /etc/btsync-user/btsync-user.conf

    bash: /usr/lib/btsync/btsync-agent: file or folder does not exist

  10. This is weird but I believe that it's start-stop-daemon's fault, somehow.

    How you found that 10 seconds is the disk access interval?

    Running btsync --config from the command line shows the same symptom?

    I use this (http://code.google.com/p/spindown/) to spindown and monitor the disks. When i stop the deamon with your script disk accessing is stopped, when i start the deamon, disks are accessed again about every 10 seconds.

    Running the deamon with btsync --config spins tje disks up every 10 minutes as programmed by the developers to scan for file changes.

  11. I don't want to start a discussion whether it is good practice to spin your disks down or not, but some of my disks contain data which is not used daily and i let these disks spindown.

    However the Sync App acesses the folder/files every 10 minutes so the disks spinup again.

    It would be nice to have a setting how often the app checks the files for changes. Preferably per folder setting because some folder are changed more frequently than others. Or maybe even an option to set a daily or twice daily scan time.