knireis

Members
  • Posts

    152
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by knireis

  1. I have a weird issue which might not be related to your package but i'll ask anyway.

     

    First i ran without login details, the webinterface did not ask for it.

    Then i added the login details to the config file and the webinterface did start asking for them.

    Now i removed the login details again from the config file and the webinterface still asks for the login details, even after restarting the server.

     

    By the way, i'm not the only one with this issue: http://forum.bittorrent.com/topic/25291-disable-webui-authorization/

     

    for solution: http://forum.bittorrent.com/topic/25291-solved-disable-webui-authorization

    is probably a bug in BTSync

  2. I'm having same issue.

    First i ran without login details, the webinterface did not ask for it.

    Then i added the login details to the config file and the webinterface did start asking for them.

    Now i removed the login details again from the config file and the webinterface still asks for them.

     

    I'll also ask this question to the debian package maintainer

  3. from the sticky on the forum:

     

    Step 1. Turn on Debug Logging.
    Windows and Mac: click on SyncApp icon and select "Enable Debug Logging".
    Linux: 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.

     

    Should i create a .sync folder in urs/lib/btsync ? And put the debug.txt in the folder.

  4.  

    Sorry - I forgot to answer: it is totally straightforward. The debug mode of btsync can be enabled as described in the posting from the btsync guys: simply create a text file named debug.txt in the storage_path of the btsync instance you want to enable debug mode. The default instance (the one maintained by debconf) defines its storage_path as /var/lib/btsync

     

    The following command executed from a root shell should enable debug mode for the default instance:

    echo FFFF > /var/lib/btsync/debug.txt

     

    I already tried that but there is nothing in the log. I don't use the default instance, and put the debug.txt in the storage path as defined in the config file. Made it all writable for the user but nothing appears in sync.log

  5. Is anybody out here able to reproduce this and collect some additional information? All my machines (i386, amd64 (Ubuntu 12.04 LTS) and armhf (Raspbian)) did the update and automatically restarted the daemon during the update... After the update the web interface was reachable and displayed 1.2.68

     

    One question to knireis: What do you mean, when you say "restart the server"? Does this mean, that after the update the web interface was not reachable and you had to reboot your server or you had to restart btsync because the web interface was not reachable any more?

     

    during upgrade when btsync starts again, it gives a fail.

    i think only after server restart btsync would start. 

  6.  

    Please give me more details! I tested it here both on my i386 and amd64 machines and it worked perfectly. Which platform? Which error message when trying to start manually by invoking it directly on the command line:

    sudo /usr/lib/btsync/btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf

     

    you need to restart the computer, then it is ok

    the error is that btsync is running already and it can't lock a PID file

  7. You are right! Sorry. I forgot but it was logical: the daemon must at least be able to access his configuration file ;-)

    ....and since the file contains security relevant information (the access data to the web interface), it is always a good idea to make it owned by the uid and gid under which the btsync daemon runs AND limit the access rights to only that user (sudo chmod 400 /etc/btsync/acmodeu.conf). Don't worry. root will always be able to access the file...

     

    Maybe you can add this to the opening post. I ran in the same issue.

  8. Hi Everybody!

     

    Since the Debian and Ubuntu Server Packages for BitTorrent Sync are now quite stable, I think that's time for starting the localisation of the interactive installation procedure powered by debconf. I'm searching for volunteers that would translate a handful of strings used during the installation.

     

    In order to make the work as easy as possible, I created an online localisation project. If you like to contribute, go to the PO Editor btsync-deb project and follow the instructions

     

    I created tables for German, Italian, French and Spanish, but if you like to translate the strings to another language, please let me know - I will add it.

     

    Thank you very much in advance for your help!

    I can do the translation in Dutch.