benbt

Members
  • Content Count

    5
  • Joined

  • Last visited

About benbt

  • Rank
    New User

Profile Information

  • Gender
    Not Telling
  1. Enabled debug. btsync debug 0000 reboot cat debug.txt 0000cat btsync-user.log 2014-02-20 22:58:10+01:00 stop_agent: begin2014-02-20 22:58:10+01:00 stop_agent: end - exiting...2014-02-20 22:59:10+01:00 User specific files and directories created2014-02-20 22:59:10+01:00 start_frontend: begin2014-02-20 22:59:10+01:00 start_frontend: starting frontend with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 22:59:10+01:00 start_frontend: end2014-02-20 22:59:10+01:00 btsync-starter: forking runner...2014-02-20 22:59:10+01:00 btsync-starter: end2014-02-20 22:59:10+01:00 agent_runner: begin2014-02-20 22:59:10+01:00 agent_runner: starting up components...2014-02-20 22:59:10+01:00 User specific files and directories created2014-02-20 22:59:10+01:00 start_frontend: begin2014-02-20 22:59:10+01:00 start_frontend: end2014-02-20 22:59:10+01:00 start_agent: begin2014-02-20 22:59:10+01:00 start_agent: starting agent with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 22:59:11+01:00 start_agent: endIndicator is not showing. btsync restart BitTorrent Sync forked to background. pid = 7077Only one indicator can run at once. Indicator is locked with /home/benbt/.btsync/indicator.lockrm /home/benbt/.btsync/indicator.lock btsync restart BitTorrent Sync forked to background. pid = 7464Now indicator and daemon are running. cat btsync-user.log 2014-02-20 23:07:41+01:00 agent_runner: agent terminated...2014-02-20 23:07:41+01:00 agent_runner: pause requested. Stopping agent...2014-02-20 23:07:41+01:00 stop_agent: begin2014-02-20 23:07:41+01:00 stop_agent: end - exiting...2014-02-20 23:07:43+01:00 User specific files and directories created2014-02-20 23:07:43+01:00 start_frontend: begin2014-02-20 23:07:43+01:00 start_frontend: starting frontend with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 23:07:43+01:00 start_frontend: end2014-02-20 23:07:43+01:00 btsync-starter: forking runner...2014-02-20 23:07:43+01:00 btsync-starter: end2014-02-20 23:07:43+01:00 agent_runner: begin2014-02-20 23:07:43+01:00 agent_runner: starting up components...2014-02-20 23:07:44+01:00 User specific files and directories created2014-02-20 23:07:44+01:00 start_frontend: begin2014-02-20 23:07:44+01:00 start_frontend: end2014-02-20 23:07:44+01:00 start_agent: begin2014-02-20 23:07:44+01:00 start_agent: starting agent with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 23:07:44+01:00 start_agent: end2014-02-20 23:09:21+01:00 agent_runner: agent terminated...2014-02-20 23:09:21+01:00 agent_runner: pause requested. Stopping agent...2014-02-20 23:09:21+01:00 stop_agent: begin2014-02-20 23:09:21+01:00 stop_agent: end - exiting...2014-02-20 23:09:23+01:00 User specific files and directories created2014-02-20 23:09:23+01:00 start_frontend: begin2014-02-20 23:09:23+01:00 start_frontend: starting frontend with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 23:09:23+01:00 start_frontend: end2014-02-20 23:09:23+01:00 btsync-starter: forking runner...2014-02-20 23:09:23+01:00 btsync-starter: end2014-02-20 23:09:23+01:00 agent_runner: begin2014-02-20 23:09:23+01:00 agent_runner: starting up components...2014-02-20 23:09:23+01:00 User specific files and directories created2014-02-20 23:09:23+01:00 start_frontend: begin2014-02-20 23:09:23+01:00 start_frontend: end2014-02-20 23:09:23+01:00 start_agent: begin2014-02-20 23:09:23+01:00 start_agent: starting agent with default config file /home/benbt/.config/btsync/btsync-auto.conf2014-02-20 23:09:23+01:00 start_agent: end
  2. Hi tuxpoldo After booting and logging into a standard user account, the indicator starts, but not the daemon. After logging auto and back into another user account, neigther the indicator nor the daemon starts. Opening a terminal and executing 'btsync start' leads to "WARNING:root:Connection Error caught, displaying error message". Then there is the indicator present, but the daemon is not running. If you execute 'btsync restart' afterwards, the indicator and the daemon start fine with "BitTorrent Sync forked to background.". Reinstallation of the package did not have any effect. How to debug this issue further?
  3. All PCs are running Ubuntu 13.10 and the current tuxpoldo-desktop-package. After the last update the following issues occured. ** PC-01 ** On PC-01 the indicator does not start/ show, but the btsync daemon starts and works. The GUI is hosted on port 9999. The file '/etc/btsync-user/btsync-agent.desktop' is present. ** PC-02, PC-03 ** On PC-02 and PC-03 the indicator starts/ shows, but instead the btsync daemon does not start. If you invoke a 'btsync stop' and afterwards 'btsync start', the indicator and daemon are staring as supposed. In some cases you have to delete '.btsync/indicator.lock' first. The GUI here is hosted on port 10000. The file '/etc/btsync-user/btsync-agent.desktop' is missing on both systems. Recreating the file does not seem to have any impact. How can I fix the issue regarding the daemon on PC-02 and PC-03? Why does the same package behave differently on the same Ubuntu version?
  4. Network Profiles per Synced Folder I attached a scenario where network profiles per synced folder could be helpful. I would like to restrict when and to which networks nodes sync and how much bandwidth is consumed. I guess part of this scenario can be realised with the current features available (search LAN only and predefined hosts). Network detection and corresponding network profiles would be helpful to enable differing behaviour per network or to differentiate client and server nodes by their sync behaviour. As far as I can see, besides the obvious advantage of this feature it would also be unique. Other authors have already requested similar features as listed below. MonoTouch, 28 Feb 2013: detection of the network to exclude networks where p2p traffic is not allowed erkr, 31 March 2013: need for more control on bandwidth and number of connections MRACHINI, 09 April 2013: demand for scheduled sync eseelke, 16 April 2013: likes to see schedule feature TheQuank, 18. April 2013: likes to have more logic in sync behaviour, which could be based on the evaluation of network profiles intrigued-user, 24. April 2013: restrict which networks BitTorrent Sync will make use of photogeek54, 24. April 2013: give preference to transferring files to other computers on a higher speed (usually LAN) network before transferring over a slower WAN exodeus, 25. April 2013: LAN only mode mustermanus, 25. April 2013: speed limitation only for external (internet) transfers kanine, 29. April 2013: schedules per sync folder jpw0617, 29. April 2013: control feature where you can tell it to use more bandwidth at certain times of day maks-k, 30. April 2013: scheduled sync and sync on demand yottabit, 06 May 2013: bandwidth limiter exactly like is present in uTorrent PacketRacket, 23. Mai 2013: limit bandwidth on a per folder/share basis X6tus, 31. May 2013: scheduled sync goli, 05. June 2012: control on sync traffic by restrictions Open the sources under a free licence as tribute to so many people offering their ideas for free. Additional wishes: - Rights management per user to enable revocation of access gratification in teams (e.g., intrigued-user, 24. April 2013) - Keep last x versions of synced files - Nested sync folders as already proposed by multiple others