tuxpoldo

Debian And Ubuntu Legacy Desktop Unofficial Packages For Bittorrent Sync

Recommended Posts

Did you add a new version to the repo yet? I just apt-get update && apt-get dist-upgrade but I didn't get a new version. Also, you said that this problem occurse only on old version like 12.04 but I'm running 14.04 and having the same issue.

 

Get:1 http://debian.yeasoft.net/btsync/ trusty/main btsync-user all 1.14.2-1 [41.9 kB]

:~$ btsync start:~$ BitTorrent Sync forked to background. pid = 12695WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message

Share this post


Link to post
Share on other sites

 

Mark found the problem and I think tomorrow we will publish a fix. The problem occurs only on systems with an old requests library (like in Ubuntu 12.04...)

 

sorry, i don't think so

this morning exclamation mark again, update to new version yesterday

2014-02-25 08:27:56+01:00 btsync-starter: start

2014-02-25 08:27:57+01:00 make_user_files: User specific files and directories created

2014-02-25 08:27:57+01:00 start_frontend: begin

2014-02-25 08:27:57+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it

2014-02-25 08:27:57+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-25 08:27:57+01:00 start_frontend: process is NOT running!!!! Something went wrong!

2014-02-25 08:27:57+01:00 start_frontend: end

2014-02-25 08:27:57+01:00 btsync-starter: no running statefile detected - forking runner...

2014-02-25 08:27:57+01:00 btsync-starter: end

2014-02-25 08:27:57+01:00 agent_runner: begin

2014-02-25 08:27:57+01:00 agent_runner: starting up components...

2014-02-25 08:27:58+01:00 make_user_files: User specific files and directories created

2014-02-25 08:27:58+01:00 start_frontend: begin

2014-02-25 08:27:58+01:00 start_frontend: process is running with pid 1964

2014-02-25 08:27:58+01:00 start_frontend: end

2014-02-25 08:27:58+01:00 start_agent: begin

2014-02-25 08:27:58+01:00 start_agent: starting agent with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-25 08:27:59+01:00 start_agent: end

2014-02-25 08:39:32+01:00 btsync-starter: start

2014-02-25 08:39:32+01:00 make_user_files: User specific files and directories created

2014-02-25 08:39:32+01:00 start_frontend: begin

2014-02-25 08:39:32+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it

2014-02-25 08:39:32+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-25 08:39:32+01:00 start_frontend: process is NOT running!!!! Something went wrong!

2014-02-25 08:39:32+01:00 start_frontend: end

2014-02-25 08:39:32+01:00 btsync-starter: running statefile detected

2014-02-25 08:39:33+01:00 btsync-starter: btsync-agent paused - forked runner present - use indicator or commandline to unpause it

2014-02-25 08:39:33+01:00 btsync-starter: end

yesterday i have had the same problem (before the update) on semplice linux 6

this is an openbox debian jessie distro in which i installed nemo 1.8.x from the jessie repository

after 4 or 5 minutes nemo has crashed

Share this post


Link to post
Share on other sites

 

Did you add a new version to the repo yet? I just apt-get update && apt-get dist-upgrade but I didn't get a new version. Also, you said that this problem occurse only on old version like 12.04 but I'm running 14.04 and having the same issue.

 

Get:1 http://debian.yeasoft.net/btsync/ trusty/main btsync-user all 1.14.2-1 [41.9 kB]

:~$ btsync start:~$ BitTorrent Sync forked to background. pid = 12695WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message

 

If you have 1.14.2-1 on your system, you have the latest version. You can verify this also by typing:

 

sudo dpkg -l btsync-user

 

Sometimes you can get some communication errors during startup, if the btsync-agent needs more time to startup. The most interesting question is: does it work, or does it not work?

 

This version fixes this problem described by jenhsun

 

Traceback (most recent call last):  File "/usr/lib/btsync-user/btsyncindicator.py", line 254, in setup_session    self.info[a] = response.json()AttributeError: 'Response' object has no attribute 'json'

Share this post


Link to post
Share on other sites

no it doesn't work.... no matter how long I keep it running, there's the exclamation mark in the systemtray icon and the warning above just keeps appearing. Tried to access the wui anyway but no luck.

 

2014-02-25 11:40:15+01:00 btsync-starter: start2014-02-25 11:40:15+01:00 make_user_files: User specific files and directories created2014-02-25 11:40:15+01:00 start_frontend: begin2014-02-25 11:40:15+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-25 11:40:15+01:00 start_frontend: starting frontend with default config file /home/hyper/.config/btsync/btsync-auto.conf2014-02-25 11:40:15+01:00 start_frontend: process is NOT running!!!! Something went wrong!2014-02-25 11:40:15+01:00 start_frontend: end2014-02-25 11:40:15+01:00 btsync-starter: no running statefile detected - forking runner...2014-02-25 11:40:15+01:00 btsync-starter: end2014-02-25 11:40:15+01:00 agent_runner: begin2014-02-25 11:40:15+01:00 agent_runner: starting up components...2014-02-25 11:40:15+01:00 make_user_files: User specific files and directories created2014-02-25 11:40:15+01:00 start_frontend: begin2014-02-25 11:40:15+01:00 start_frontend: process is running with pid 277692014-02-25 11:40:15+01:00 start_frontend: end2014-02-25 11:40:15+01:00 start_agent: begin2014-02-25 11:40:15+01:00 start_agent: starting agent with default config file /home/hyper/.config/btsync/btsync-auto.conf2014-02-25 11:40:15+01:00 start_agent: end

Share this post


Link to post
Share on other sites

no it doesn't work.... no matter how long I keep it running, there's the exclamation mark in the systemtray icon and the warning above just keeps appearing. Tried to access the wui anyway but no luck.

OK - this means: the btsync engine itself is not running. Please delete any old logging file...

rm -f ~/.btsync/btsync-user.log
then activate debug logging...

btsync debug 0000
and than restart the whole thing:

btsync restart
and then post the log in ~/.btsync/btsync-user.log here.

Share this post


Link to post
Share on other sites

cat .btsync/btsync-user.log 2014-02-25 11:46:36+01:00 btsync-starter: start2014-02-25 11:46:36+01:00 make_user_files: User specific files and directories created2014-02-25 11:46:36+01:00 start_frontend: begin2014-02-25 11:46:36+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-25 11:46:36+01:00 start_frontend: starting frontend with default config file /home/hyper/.config/btsync/btsync-auto.conf2014-02-25 11:46:36+01:00 start_frontend: process is NOT running!!!! Something went wrong!2014-02-25 11:46:36+01:00 start_frontend: end2014-02-25 11:46:36+01:00 btsync-starter: no running statefile detected - forking runner...2014-02-25 11:46:36+01:00 agent_runner: begin2014-02-25 11:46:36+01:00 btsync-starter: end2014-02-25 11:46:36+01:00 agent_runner: starting up components...2014-02-25 11:46:36+01:00 make_user_files: User specific files and directories created2014-02-25 11:46:36+01:00 start_frontend: begin2014-02-25 11:46:36+01:00 start_frontend: process is running with pid 286182014-02-25 11:46:36+01:00 start_frontend: end2014-02-25 11:46:36+01:00 start_agent: begin2014-02-25 11:46:36+01:00 start_agent: starting agent with default config file /home/hyper/.config/btsync/btsync-auto.conf2014-02-25 11:46:36+01:00 start_agent: end
cat .btsync/debug.txt 0000
hyper@subi:~$ rm -f ~/.btsync/btsync-user.loghyper@subi:~$ btsync debug 0000Enabling verbose logging (Mask: 0000)hyper@subi:~$ btsync restarthyper@subi:~$ BitTorrent Sync forked to background. pid = 28653WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message

no luck.

Share this post


Link to post
Share on other sites

sorry, i don't think so

I definitively think so. As described previously, the fix addresses a problem described by other users and definitively not yours.

 

this morning exclamation mark again, update to new version yesterday

Let's make some analysis:

2014-02-25 08:27:56+01:00 btsync-starter: start

...

2014-02-25 08:27:57+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-25 08:27:57+01:00 start_frontend: process is NOT running!!!! Something went wrong!

2014-02-25 08:27:57+01:00 start_frontend: end

 

Uppps!!!! No btsyncindicator????

 

2014-02-25 08:27:57+01:00 btsync-starter: no running statefile detected - forking runner...

2014-02-25 08:27:57+01:00 btsync-starter: end

 

btsync itself has started....

2014-02-25 08:27:57+01:00 agent_runner: begin

2014-02-25 08:27:57+01:00 agent_runner: starting up components...

2014-02-25 08:27:58+01:00 make_user_files: User specific files and directories created

 

try to start btsyncindicator again....

 

2014-02-25 08:27:58+01:00 start_frontend: begin

2014-02-25 08:27:58+01:00 start_frontend: process is running with pid 1964

2014-02-25 08:27:58+01:00 start_frontend: end

 

sucess!

 

2014-02-25 08:27:58+01:00 start_agent: begin

2014-02-25 08:27:58+01:00 start_agent: starting agent with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-25 08:27:59+01:00 start_agent: end

 

So we learned:

  • On your machine the indicator applet fails to start on the first try. This may be interesting in order to understand what's wrong. In any case the delayed start seems to succeed...
  • The exclamation mark means that the indicator is not able to communicate with btsync. This can have several reasons. Often the indicator shows on the commandline messages, if is was started from there. Please try a btsync restart on the command line and post here the visible output in the terminal in case the exclamation mark shows again

yesterday i have had the same problem (before the update) on semplice linux 6

this is an openbox debian jessie distro in which i installed nemo 1.8.x from the jessie repository

after 4 or 5 minutes nemo has crashed

 

Unfortunately it is not simple to test applications like these on every available distribution and combination of desktions/applications... Since you are using a very special combination of components, you should take in consideration the possibility that there may be real incompatibilities between components like python-requests or libindicator with your toolchain.

hyper@subi:~$ rm -f ~/.btsync/btsync-user.loghyper@subi:~$ btsync debug 0000Enabling verbose logging (Mask: 0000)hyper@subi:~$ btsync restarthyper@subi:~$ BitTorrent Sync forked to background. pid = 28653WARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error messageWARNING:root:Communication Error caught, displaying error message
no luck.

Mhhh. Can you please test if btsync itself is running?

 

pgrep -u $(id -u) -x btsync-agent
If it outputs a number (the PID) it is running. If it outputs nothing, it is NOT running... I should add this test also to the logging facility...

Share this post


Link to post
Share on other sites

maybe that's also of use:

 

ps aux | grep btsynchyper    30124  2.2  0.1 431204 29236 pts/16   Sl   12:00   0:00 python /usr/lib/btsync-user/btsyncindicator.py --config /home/hyper/.config/btsync/btsync-auto.conf --iconpath /usr/share/icons/hicolor/22x22/statushyper    30134  0.0  0.0   4444   368 pts/16   S    12:00   0:00 /bin/sh /usr/lib/btsync-user/btsync-starterhyper    30161 93.7  0.5 445608 85208 ?        Ssl  12:00   0:09 /usr/lib/btsync-user/btsync-agent --config /home/hyper/.config/btsync/btsync-auto.confhyper    30232  0.0  0.0  13236   920 pts/17   S+   12:00   0:00 grep --color=auto btsync

pgrep -u $(id -u) -x btsync-agent30161

 

WUI not accessible


I think I found the problem... or part to it

 

the config file in ~/.config/btsync/btsync-auto.conf uses a different port than the config file in ~/.btsync/config.json

 

The weird thing is the config file in the .config folder has no login data set...

However the config file in .btsync does have.

 

When using the port from .config and the user login from .btsync I manage to loging.

 

Could the python indicator also use the wrong port?

Share this post


Link to post
Share on other sites

maybe that's also of use:

ps aux | grep btsynchyper    30124  2.2  0.1 431204 29236 pts/16   Sl   12:00   0:00 python /usr/lib/btsync-user/btsyncindicator.py --config /home/hyper/.config/btsync/btsync-auto.conf --iconpath /usr/share/icons/hicolor/22x22/statushyper    30134  0.0  0.0   4444   368 pts/16   S    12:00   0:00 /bin/sh /usr/lib/btsync-user/btsync-starterhyper    30161 93.7  0.5 445608 85208 ?        Ssl  12:00   0:09 /usr/lib/btsync-user/btsync-agent --config /home/hyper/.config/btsync/btsync-auto.confhyper    30232  0.0  0.0  13236   920 pts/17   S+   12:00   0:00 grep --color=auto btsync
pgrep -u $(id -u) -x btsync-agent30161

WUI not accessible

I think I found the problem... or part to it

 

the config file in ~/.config/btsync/btsync-auto.conf uses a different port than the config file in ~/.btsync/config.json

 

The weird thing is the config file in the .config folder has no login data set...

However the config file in .btsync does have.

 

When using the port from .config and the user login from .btsync I manage to loging.

 

Could the python indicator also use the wrong port?

 

 

OK - that is REALLY interesting! The big issue is the strange implementation of configuration management in btsync. Btsync itself is planned as a gui application with its internal configuration store. Since the unix version is basically headless, you need the possibility to configure some things on start, and that's the reason they added configuration file support - but in a very strange way.

 

From observations, I understood that btsync is working this way:

  1. load meaningful defaults into the configuration data structure
  2. if a config file is supplied, overwrite the defaults with the data in the config file
  3. look if storage_path exists, and if yes, load stored configuration data from the json file stored there
  4. if a config file is supplied, overwrite the config data AGAIN with the data in the config file

 

This explains the behaviour of btsync in certain situations. There is a way you can break it:

  1. btsnyc-user creates by default a config file with no credentials set
  2. Now you open the web interface and you define credentials
  3. btsyncindicator stops working (excalmation point) since it does not know the credentials to use
  4. The credentials are stored into the internal json file
  5. On the next start, the credentials are loaded from the json file AND NOT OVERWRITTEN by the config file, since the config file does not define any credentials
  6. btsnycindicator still shows the exclamation point

pi3tr0? Does this sound familiar? Could this be the reason for YOUR problems?

 

You can solve the issue by defining a user defined config file that specifies credentials. In that case, the credentials you may set in the web interface are overwritten on each start and the indicator will use the credentials supplied into the config file.

 

BTW: the port thing is interesting... But maybe the same story.

@pi3tr0: maybe you are a good candidate for testing the new btsync gui implementation I'm working on. Stay tuned since I will make available the first alpha release in the next days... (Update: It's available now - follow the previous link)

Share this post


Link to post
Share on other sites

So, where do I need to add credentials now? also to the file in .config?

And shall I make both ports the same?


Hmmm, I amended the .config/btsync/btsync-auto.conf with the credentials but still the python icon doesn't like it. I also set the same port in .btsync/config.json


no luck though.


looking again at the btsync-auto.conf I noticed all chages were overwriten.

Share this post


Link to post
Share on other sites

So, where do I need to add credentials now? also to the file in .config?

And shall I make both ports the same?

Hmmm, I amended the .config/btsync/btsync-auto.conf with the credentials but still the python icon doesn't like it. I also set the same port in .btsync/config.json

no luck though.

looking again at the btsync-auto.conf I noticed all chages were overwriten.

 

Sorry for the late answer. The last hours I was driving towards Italy to meet my parents. Now I'm there and I have network ;-)

 

It makes no sense to edit btsync-auto.conf, since this file (as you noticed) is rewritten/auto-generated at each start. But there is a way to supply your own configuration file. You must create a file named btsync-user.conf in the same directory. If such a file is there, it is taken instead of btsync-auto.conf.

 

So the best way is:

 

  1. Copy btsync-auto.conf to btsync-user.conf
  2. Edit btsync-user.conf to your needs
  3. restart btsync

Please let me know it this solved your problem.

 

BTW: this behaviour is documented in the initial posting

Share this post


Link to post
Share on other sites

Tuxpoldo,

 

Excellent work with packaging this--thanks!

 

I'm installing btsync-user on a 10.04 (Lucid), and getting unmet dependencies:

$ sudo apt-get install btsync-userReading package lists... DoneBuilding dependency tree       Reading 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 to resolve the situation:The following packages have unmet dependencies:  btsync-user: Depends: python-requests but it is not installableE: Broken packages

The system is up-to-date, I've installed requests based on the instructions I could find...

$ pip install requestsRequirement already satisfied (use --upgrade to upgrade): requests in /usr/local/lib/python2.6/dist-packagesCleaning up...

I've also installed python 2.7,

apt-cache show python2.7Package: python2.7Priority: optionalSection: pythonInstalled-Size: 9656Maintainer: Felix Krull <f_krull@gmx.de>Architecture: i386Version: 2.7.6-2+lucid1Suggests: python2.7-doc, binutilsProvides: python2.7-celementtree, python2.7-cjkcodecs, python2.7-ctypes, python2.7-elementtree, python2.7-plistlib, python2.7-profiler, python2.7-wsgirefDepends: python2.7-minimal (= 2.7.6-2+lucid1), mime-support, libbz2-1.0, libc6 (>= 2.11), libdb4.8, libexpat1 (>= 1.95.8), libncursesw5 (>= 5.6+20071006-3), libreadline6 (>= 6.0), libsqlite3-0 (>= 3.6.22)Filename: pool/main/p/python2.7/python2.7_2.7.6-2+lucid1_i386.deb

but either it doesn't help, or it isn't linked where the btsync-user package is looking for it.  I can't find a package "python-requests" for 10.04.

 

Any suggestions?

 

Thanks much

Share this post


Link to post
Share on other sites

I know it's coming...I'm trying to stave off the inevitable.

 

 

Ahem..... I must admit, that adding btsync-user to the lucid repository was a mistake... at least after Mark's btsyncindicator was added since it depends on python-requests, which is not included in lucid. I removed the btsync-user package both from Launchpad and from the YeaSoft repository in order to avoid such problems in future. Sorry - but Lucid is really near end of life, and I cannot spend too much time supporting things that will not work... I do not want to encourage people on using Lucid for Desktop systems. Headless servers are OK, and it is absolutely no problem installing the server version, but if you are using a desktop system, you should really stay up to date...

 

But if you really really want to make it work... you should look if you find a python-request port in Launchpad for lucid.... maybe you are lucky. But in any case you have now to download the debs for btsync-user manually.... and install them with dpkg -i

Share this post


Link to post
Share on other sites

Before you ask: the btsync-common package for 1.2.91 will come tomorrow, since I will get tomorrow the custom build for AMD Geode that will be included there....

Share this post


Link to post
Share on other sites

Finally the update...
 

btsync-common (1.2.91-2) unstable; urgency=low   * Added support for AMD Geode CPU -- Leo Moll <leo.moll@yeasoft.com>  Fri, 07 Mar 2014 16:27:01 +0100 btsync-common (1.2.91-1) unstable; urgency=low   * New upstream release  * Added support for btsync-gui when updating -- Leo Moll <leo.moll@yeasoft.com>  Fri, 07 Mar 2014 13:37:33 +0100

 
1.2.91-2 is available only on debian.yeasoft.net since the Geode change is not relevant for Ubuntu (Ubuntu has no Kernel that runs on Geode machines).

As usual people using the Launchpad PPA have to wait a few hours (perhaps you may take in consideration moving from the PPA to debian.yeasoft.net).

One thing more: unfortunately Launchpad does not permit to update packages for outdated Ubuntu versions in the PPA. Because of this, there is no way to update the packages for Ubuntu Raring since the support has ceased. People using unsupported Ubuntu version must update to the debian.yeasoft.net repository if they want to stay up to date.

Share this post


Link to post
Share on other sites

@pi3tr0: maybe you are a good candidate for testing the new btsync gui implementation I'm working on. Stay tuned since I will make available the first alpha release in the next days... (Update: It's available now - follow the previous link)

sorry, i have been busy in the past 2 weeks

 

i have moved from mint 16 to ubuntu 14.04 because rhythmbox tested in 14.04 have changed my music and podcast database

 

so now i have installed the experimental repo and the new btsync in ubuntu gnome 14.04 with the cinnamon DE

 

if this will work i will install also in 14.04 with mate DE e debian jessie with openbox DE

Share this post


Link to post
Share on other sites

Hi there,

 

today I found an explanation for the strange "cannot connect" bug that several people encounters on startup. It seems that on some systems all processes are brutally killed on logout/shutdown leaving a lot of state files around. The following version should fix it (I hope). Please let me know. Here the changelog:

 

btsync-user (1.14.3-1) unstable; urgency=low  * New forked release 0.14.2 of btsyncindicator    - Fixed TypeError on Debian Wheezy      (Would close #btsyncindicator/45)  * Fix handling of brutaly killed processes    (Closes #60) and (Closes #94) -- Leo Moll <leo.moll@yeasoft.com>   Wed, 12 Mar 2014 18:54:22 +0100

Share this post


Link to post
Share on other sites

Ladies and Gentlemen,

 

after the release of 1.3.67 I made some tests and discovered that basically the release seems to work both with the server as the desktop GUI and user package. Nevertheless I noticed some different behaviour (much slower API access) and I'm a little bit afraid in publishing the new release without any tests made by more persons. Because of this, I will release the binary package for 1.3.67 today only on the YeaSoft repository and not on the Launchpad PPA (this will affect only about 30% of the users).

If there will be no really serious problems reported until tomorrow, I will publish the package tomorrow also on the Launchpad PPA.

 

btsync-common (1.3.67-1) unstable; urgency=low  * New upstream release -- Leo Moll <leo.moll@yeasoft.com>  Wed, 25 Mar 2014 15:25:12 +0100
Have fun and let's hope everything works as expected....

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.