tuxpoldo

Debian And Ubuntu Legacy Desktop Unofficial Packages For Bittorrent Sync

Recommended Posts

 

This seems really to be a problem related to the environment of your OS. I think that the next step should be to post an issue on the project page of btsyncindicator.py.

 

UPDATE: The warning seems not to have any side effect on Debian Wheezy. In any case I posted Issue #41 - The problem is still unclear: the "sort of number 1 inside" (in fact it's an exclamation point) means that there is no connection to the btsync agent (or it is paused from the indicator menu that is basically the same). The reason why nemo crashes, is not really clear.

 

Which distribution are you using?

 

linux mint 16 petra and ubuntu 13.10 with cinnamon de

Share this post


Link to post
Share on other sites

 

This seems really to be a problem related to the environment of your OS. I think that the next step should be to post an issue on the project page of btsyncindicator.py.

 

UPDATE: The warning seems not to have any side effect on Debian Wheezy. In any case I posted Issue #41 - The problem is still unclear: the "sort of number 1 inside" (in fact it's an exclamation point) means that there is no connection to the btsync agent (or it is paused from the indicator menu that is basically the same). The reason why nemo crashes, is not really clear.

 

Which distribution are you using?

 

thank you tuxpoldo, i hope someone resolve this problem because i really like bitsync

Share this post


Link to post
Share on other sites

Some news: after a few weeks from the latest release, it seems that some users encounter under certain circumstances problems with the autostart of btsync after login. The problem is described in Issue #60. Please take a look there, and tell me, if you find some clue for me....

 

Currently it is totally unclear what is the cause of this problem and under which circumstances it happens....

Share this post


Link to post
Share on other sites

 

Some news: after a few weeks from the latest release, it seems that some users encounter under certain circumstances problems with the autostart of btsync after login. The problem is described in Issue #60. Please take a look there, and tell me, if you find some clue for me....

 

Currently it is totally unclear what is the cause of this problem and under which circumstances it happens....

 

i think this issue is the same of mine, sometime the icon is ok, sometime there is an exclamation mark and other time there is no icon at all

ask at other users if they use cinnamon or just nemo because i have the same problem in ubuntu 13.10 with cinnamon (and linux mint 16)

i want to help, if you explain in the issue page how to help (consider my english is bad and i am not a geek)

Share this post


Link to post
Share on other sites

I have the same startup problem in Ubuntu 12.04.

Until this is solved, I´ve made a temporarily poor man´s workaround script which seems to work for me.

Run this script on boot with Ubuntu´s "Startup Applications" (Also deactivate for the time the regular Btsync boot/start command in  "Startup Applications" )

#!/bin/sh/usr/lib/btsync-user/btsync-startersleep 10/usr/lib/btsync-user/btsync-stopper sleep 10btsync start

Grz Eric

Share this post


Link to post
Share on other sites

OK Ladies and Gentlemen,

 

sorry for the delay in solving this. I promise that tomorrow I will publish a modified /usr/lib/btsync-user/btsync-starter that produces meaningful logging output to debug these annoying issues with instructions how to apply it. I hope that we will find the cause for these problems....

 

I have also some good news: I'm working on something new. It's to early to tell about it, but I'm quite sure, that you will like it ;-)

Share this post


Link to post
Share on other sites

I just released version 1.13.1-1 of btsync-user. This version contains the promised logging for the wrapper script that coordinates the launch and runtime of btsync.

 

I would kindly ask those of you experiencing the problems reported during the startup phase, to activate logging by issuing the command

 

btsync debug 0000
 

It does not matter, which debug flags you specify (0000 to FFFF) - as soon as logging is activated, the startup script logs everything. The logging facility creates the logfile

 

~/.btsync/btsync-user.log

 

If you encounter the forementioned problems (mainly startup problems after first boot), please post here the relevant part of the log file. TNX!!!!

Share this post


Link to post
Share on other sites

I just released version 1.13.1-1 of btsync-user. This version contains the promised logging for the wrapper script that coordinates the launch and runtime of btsync.

 

I would kindly ask those of you experiencing the problems reported during the startup phase, to activate logging by issuing the command

 

btsync debug 0000
 

It does not matter, which debug flags you specify (0000 to FFFF) - as soon as logging is activated, the startup script logs everything. The logging facility creates the logfile

 

~/.btsync/btsync-user.log

 

If you encounter the forementioned problems (mainly startup problems after first boot), please post here the relevant part of the log file. TNX!!!!

 

 

sorry tuxpoldo

updated to 1.13.1-1, restarting the system → btsync debug 0000 but the logging file has not be created

i created it manually and restarting btsync but it remains empty so i deleted it

Share this post


Link to post
Share on other sites

I just released version 1.13.1-1 of btsync-user. This version contains the promised logging for the wrapper script that coordinates the launch and runtime of btsync.

 

I would kindly ask those of you experiencing the problems reported during the startup phase, to activate logging by issuing the command

 

btsync debug 0000
 

It does not matter, which debug flags you specify (0000 to FFFF) - as soon as logging is activated, the startup script logs everything. The logging facility creates the logfile

 

~/.btsync/btsync-user.log

 

If you encounter the forementioned problems (mainly startup problems after first boot), please post here the relevant part of the log file. TNX!!!!

 

 

There was this in the btsync-user.log (after booting with btsync debug 0000):

2014-02-18 10:55:22+01:00 User specific files and directories created2014-02-18 10:55:22+01:00 start_frontend: begin2014-02-18 10:55:22+01:00 start_frontend: starting frontend with default config file /home/eric/.config/btsync/btsync-auto.conf2014-02-18 10:55:22+01:00 start_frontend: end2014-02-18 10:55:22+01:00 btsync-starter: btsync-agent paused

So nothing special, it was paused. But btsync indicator didn´t show up on my ubuntu 12.04.

After starting manually with btsync start. nothing changed in the log. 

But the following showed up in the terminal:

WARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392717328.94WARNING:root:Connection Error caught, displaying error message

Then exit btsync again and restarted. Then works fine after the restart.

 

Hope this helps.

 

Grz Eric

Edited by Eric0

Share this post


Link to post
Share on other sites

l, it was paused. But btsync indicator didn´t show up on my ubuntu 12.04.

After starting manually with btsync start. nothing changed in the log. 

But the following showed up in the terminal:

WARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392717328.94WARNING:root:Connection Error caught, displaying error message

Then exit btsync again and restarted. Then works fine after the restart.

 

Hope this helps.

 

Grz Eric

 

actually, after the last update on my Xubuntu 12.04 system, I get

- an exclamation mark in the indicator symbol

- an error message in the indicator (Communication error 401),

- the option to open the web interface is disabled (but is running),

- and if I try to restart, I keep getting the Error caught message:

 

$ BitTorrent Sync forked to background. pid = 23114
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
...
 
 
Has anything gone wrong with the last update?

Share this post


Link to post
Share on other sites

sorry tuxpoldo

updated to 1.13.1-1, restarting the system → btsync debug 0000 but the logging file has not be created

i created it manually and restarting btsync but it remains empty so i deleted it

 

After executing

 

btsync debug 0000

 

there will be a file ~/.btsync/debug.txt containing 0000

 

The startup and runtime script will check for the existence of this file in every call to the logging routine, so there MUST be a debug output file. But you really have to reboot your machine, to get the new startup and runtime script to be executed.

There was this in the btsync-user.log (after booting with btsync debug 0000):

...

So nothing special, it was paused. But btsync indicator didn´t show up on my ubuntu 12.04.

Can you please check in this EXACT state, if the process is running or not? You can do this by executing:

pgrep -u $(id -u) -f btsyncindicator.py
If it is running, the PID (a numerical value) will be shown. If not, nothing is shown.

After starting manually with btsync start. nothing changed in the log.

This is totally impossible. The script is full of logging statements and every logging statement writes via a single redirection in the log file. Are you sure, that you REopened the log file? The best was to follow the changes is to open a separate console with the command:

tail -f ~/.btsync/btsync-user.log

But the following showed up in the terminal:

WARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392717328.94WARNING:root:Connection Error caught, displaying error message
Then exit btsync again and restarted. Then works fine after the restart.

 

Hope this helps.

 

Grz Eric

I have no explanation for that. I also get sometimes this error message on my systems, but it has absolutely no effect on functionality... But I'm still investigating.

The main problem, is that I am absolutely not able to reproduce the described effects on any of my systems... What the hell may be the difference between them?!?!

 

actually, after the last update on my Xubuntu 12.04 system, I get

- an exclamation mark in the indicator symbol

- an error message in the indicator (Communication error 401),

- the option to open the web interface is disabled (but is running),

- and if I try to restart, I keep getting the Error caught message:

 

$ BitTorrent Sync forked to background. pid = 23114
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
WARNING:root:Communication Error caught, displaying error message
...
 
 
Has anything gone wrong with the last update?

 

 

(Communication error 401) => HTTP 401 is "Unauthorized"

 

This is really strange. Do you have set any credentials on your btsync? There is a way to break it: If you have set any credentials, either by putting them directly in the config file or by entering them in the Web UI, there is no way back to remove them. If you removed the credentials from the config file, they are still in effect since btsync stores them in an internal database. The only way to solve the problem, is to set credentiuals in the config file AND LEAVE THEM THERE. The credentials in the config file will alsoway overwrite former credentials set in the internal database and btsyncindicator will then use them in order to connect to the system.

Share this post


Link to post
Share on other sites

Ok, I´ve tried the following again.

 

When I boot with

btsync debug 0000

There is no process starting.

 

Executing this after this boot:

pgrep -u $(id -u) -f btsyncindicator.py

Gives no number.

 

The file ~./btsync/debug.txt was created with the boot timestamp.

The logfile ~./btsync-user.log was unchanged! (timestamp from before the boot)

 

 

Now: when I boot with:

btsync start

The following is noticed:

pgrep -u $(id -u) -f btsyncindicator.py

It gives a pid nr. So it is running but with an exclamation mark.

 

The logfile ~./btsync-user.log changed. The following text was added.

2014-02-19 08:38:09+01:00 User specific files and directories created2014-02-19 08:38:10+01:00 start_frontend: begin2014-02-19 08:38:10+01:00 start_frontend: starting frontend with default config file /home/eric/.config/btsync/btsync-auto.conf2014-02-19 08:38:10+01:00 start_frontend: end2014-02-19 08:38:10+01:00 btsync-starter: btsync-agent paused

Next thing I tried was starting with the little script I made:

#!/bin/sh/usr/lib/btsync-user/btsync-startersleep 10/usr/lib/btsync-user/btsync-stopper sleep 10btsync start

Then the indicator shows a normal status.

To the logfile was added (I selected the debugging option in the indicator):

2014-02-19 08:32:33+01:00 User specific files and directories created2014-02-19 08:32:33+01:00 start_frontend: begin2014-02-19 08:32:33+01:00 start_frontend: starting frontend with default config file /home/eric/.config/btsync/btsync-auto.conf2014-02-19 08:32:33+01:00 start_frontend: end2014-02-19 08:32:33+01:00 btsync-starter: btsync-agent paused2014-02-19 08:32:54+01:00 User specific files and directories created2014-02-19 08:32:54+01:00 start_frontend: begin2014-02-19 08:32:54+01:00 start_frontend: starting frontend with default config file /home/eric/.config/btsync/btsync-auto.conf2014-02-19 08:32:54+01:00 start_frontend: end2014-02-19 08:32:54+01:00 btsync-starter: forking runner...2014-02-19 08:32:54+01:00 btsync-starter: end2014-02-19 08:32:54+01:00 agent_runner: begin2014-02-19 08:32:54+01:00 agent_runner: starting up components...2014-02-19 08:32:54+01:00 User specific files and directories created2014-02-19 08:32:54+01:00 start_frontend: begin2014-02-19 08:32:54+01:00 start_frontend: end2014-02-19 08:32:54+01:00 start_agent: begin2014-02-19 08:32:54+01:00 start_agent: starting agent with default config file /home/eric/.config/btsync/btsync-auto.conf

Last thing:

When I boot with btsync debug 0000, nothing happened as said before.

But when I open a terminal and to manually execute:

btsync start

The indicator shows up with this exclamation mark.

In the terminal the following text is looping:

WARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392797019.99WARNING:root:Connection Error caught, displaying error messageWARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392797022.0WARNING:root:Connection Error caught, displaying error messageWARNING:requests.packages.urllib3.connectionpool:Retrying (0 attempts remain) after connection broken by 'error(111, 'Connection refused')': /gui/token.html?t=1392797024.0WARNING:root:Connection Error caught, displaying error messageetc...

Then I end the process and execute btsync start in the same terminal. Everything is fine then.

Share this post


Link to post
Share on other sites

Hi,

 

 

The main problem, is that I am absolutely not able to reproduce the described effects on any of my systems... What the hell may be the difference between them?!?!

 

(Communication error 401) => HTTP 401 is "Unauthorized"

 

This is really strange. Do you have set any credentials on your btsync? There is a way to break it: If you have set any credentials, either by putting them directly in the config file or by entering them in the Web UI, there is no way back to remove them. If you removed the credentials from the config file, they are still in effect since btsync stores them in an internal database. The only way to solve the problem, is to set credentiuals in the config file AND LEAVE THEM THERE. The credentials in the config file will alsoway overwrite former credentials set in the internal database and btsyncindicator will then use them in order to connect to the system.

 

ok, yes, I have credentials, and setting the credentials in the config -as you proposed- is a workaround that solves this issue.

 

Two things:

1) The setup with the credentials somewhere else had been working for months without any problems. The problems have started after the last update.

2) I guess most of the users don't like passwords stored in the clear somewhere in their filesystem.

 

Is it likely that we will get an update for this soon?

 

Thanks and regards,

tomsam

Share this post


Link to post
Share on other sites

Hi folks!

 

some days ago, I announced that I'm working on something new. Although it's too early to announce it, I would like to give you some hint. Take a look here... and here... and here... and here. Maybe with a little bit of luck, the braves may have a chance to test it in 7-8 days....

Share this post


Link to post
Share on other sites

Enabled debug.

btsync debug 0000
reboot
cat debug.txt

0000

cat 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: end

Indicator 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.lock

rm /home/benbt/.btsync/indicator.lock
btsync restart

BitTorrent Sync forked to background. pid = 7464

Now 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

Share this post


Link to post
Share on other sites

Ladies and Gentleman,

 

thank you a lot for the log files you posted here. Unfortunately the information is still not enough, to fully understand the nature of the problems on some systems. Because of this, I prepared a new version with more detailed logging and also some additional code that intercepts a particular situation that should not happen, but happens due to a non fully correct implementation of the context handler in btsyncindicator.py. I would kindly ask you to update to the new version, and send me more log files. In order to avoid the pollution of the forum, it would be nice, if you can send me the log files as private messages.

 

Here the changelog of the new version:

btsync-user (1.13.2-1) unstable; urgency=low   * Updated man page to reflect recent changes in file and    directory structure  * Added more logging to the startup script  * Updated comment block in btsync-starter to reflect recent    changes in file and directory structure  * Improved handling of context manager lock file that will    not be automatically deleted on indicator stop (what should    happen but does not) -- Leo Moll <leo.moll@yeasoft.com>  Fri, 21 Feb 2014 11:38:10 +0100 

On my debian wheezy test system, I installed the new version, stopped anything, deleted the old log file and than rebooted the system. After reboot and logging in, everything was working fine. Then I logged out, and logged in again and again everything was working fine. Here the log file of such a session:

2014-02-21 12:35:49+01:00 btsync-starter: start2014-02-21 12:35:49+01:00 make_user_files: User specific files and directories created2014-02-21 12:35:49+01:00 start_frontend: begin2014-02-21 12:35:49+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-21 12:35:49+01:00 start_frontend: starting frontend with default config file /home/leo/.config/btsync/btsync-auto.conf2014-02-21 12:35:49+01:00 start_frontend: process is running with pid 160502014-02-21 12:35:49+01:00 start_frontend: end2014-02-21 12:35:49+01:00 btsync-starter: no running statefile detected - forking runner...2014-02-21 12:35:49+01:00 agent_runner: begin2014-02-21 12:35:49+01:00 agent_runner: starting up components...2014-02-21 12:35:49+01:00 btsync-starter: end2014-02-21 12:35:49+01:00 make_user_files: User specific files and directories created2014-02-21 12:35:49+01:00 start_frontend: begin2014-02-21 12:35:49+01:00 start_frontend: process is running with pid 160502014-02-21 12:35:49+01:00 start_frontend: end2014-02-21 12:35:49+01:00 start_agent: begin2014-02-21 12:35:49+01:00 start_agent: starting agent with default config file /home/leo/.config/btsync/btsync-auto.conf2014-02-21 12:35:49+01:00 start_agent: end2014-02-21 12:36:46+01:00 btsync-starter: start2014-02-21 12:36:46+01:00 make_user_files: User specific files and directories created2014-02-21 12:36:46+01:00 start_frontend: begin2014-02-21 12:36:46+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-21 12:36:46+01:00 start_frontend: starting frontend with default config file /home/leo/.config/btsync/btsync-auto.conf2014-02-21 12:36:46+01:00 start_frontend: process is running with pid 166722014-02-21 12:36:46+01:00 start_frontend: end2014-02-21 12:36:46+01:00 btsync-starter: btsync-agent already running - nothing to do

IMPORTANT ADDITIONAL INFORMATION FOR THOSE OF YOU USING UBUNTU RARING:

 

Launchpad has ceased support for Ubuntu Raring (13.04). Because of this I'm not able to publish new versions of the packages for Raring. If you are still using raring and want to keep your system up to date, you should remove the ppa and add the alternative ppa by using the instructions for Debian as described in the initial posting.

Share this post


Link to post
Share on other sites

 

After executing

 

btsync debug 0000
 

there will be a file ~/.btsync/debug.txt containing 0000

you're right, i was searcching in .config/btsync folder

but the file have only 4 0 and nothing else, today i updated to the new version and reboot the system, the icon should not appear, so i executed btsync restart but the debug file have only for zeros

Share this post


Link to post
Share on other sites

After executing

 

btsync debug 0000
there will be a file ~/.btsync/debug.txt containing 0000

This is exactly what is expected to happen.

 

you're right, i was searcching in .config/btsync folder but the file have only 4 0 and nothing else, today i updated to the new version and reboot the system, the icon should not appear, so i executed btsync restart but the debug file have only for zeros

This is exactly what is expected to happen.

I suppose you were looking for the log file. The log file is named ~/.btsync/btsync-user.log

Share this post


Link to post
Share on other sites

 

This is exactly what is expected to happen.

 

This is exactly what is expected to happen.

I suppose you were looking for the log file. The log file is named ~/.btsync/btsync-user.log

 

now the icon is working after the boot, this is the btsync-user.log

2014-02-21 18:37:24+01:00 btsync-starter: start

2014-02-21 18:37:24+01:00 make_user_files: User specific files and directories created

2014-02-21 18:37:24+01:00 start_frontend: begin

2014-02-21 18:37:24+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it

2014-02-21 18:37:24+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 18:37:24+01:00 start_frontend: process is NOT running!!!! Something went wrong!

2014-02-21 18:37:24+01:00 start_frontend: end

2014-02-21 18:37:24+01:00 btsync-starter: no running statefile detected - forking runner...

2014-02-21 18:37:24+01:00 btsync-starter: end

2014-02-21 18:37:24+01:00 agent_runner: begin

2014-02-21 18:37:24+01:00 agent_runner: starting up components...

2014-02-21 18:37:24+01:00 make_user_files: User specific files and directories created

2014-02-21 18:37:24+01:00 start_frontend: begin

2014-02-21 18:37:24+01:00 start_frontend: process is running with pid 1954

2014-02-21 18:37:24+01:00 start_frontend: end

2014-02-21 18:37:24+01:00 start_agent: begin

2014-02-21 18:37:24+01:00 start_agent: starting agent with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 18:37:26+01:00 start_agent: end

Share this post


Link to post
Share on other sites

and this is the user.log when the icon has the exclamation mark

2014-02-21 23:03:35+01:00 btsync-starter: start

2014-02-21 23:03:36+01:00 make_user_files: User specific files and directories created

2014-02-21 23:03:36+01:00 start_frontend: begin

2014-02-21 23:03:36+01:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it

2014-02-21 23:03:36+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 23:03:36+01:00 start_frontend: process is NOT running!!!! Something went wrong!

2014-02-21 23:03:36+01:00 start_frontend: end

2014-02-21 23:03:36+01:00 btsync-starter: running statefile detected

2014-02-21 23:03:36+01:00 btsync-starter: btsync-agent paused - forked runner present - use indicator or commandline to unpause it

2014-02-21 23:03:36+01:00 btsync-starter: end

now i have rebooted into semplice linux (debian jessie)

2014-02-21 23:09:53+01:00 User specific files and directories created

2014-02-21 23:09:53+01:00 start_frontend: begin

2014-02-21 23:09:53+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 23:09:53+01:00 start_frontend: end

2014-02-21 23:09:54+01:00 btsync-starter: btsync-agent paused

after a btsynch restart

2014-02-21 23:11:32+01:00 User specific files and directories created

2014-02-21 23:11:32+01:00 start_frontend: begin

2014-02-21 23:11:32+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 23:11:32+01:00 start_frontend: end

2014-02-21 23:11:32+01:00 btsync-starter: forking runner...

2014-02-21 23:11:32+01:00 btsync-starter: end

2014-02-21 23:11:32+01:00 agent_runner: begin

2014-02-21 23:11:32+01:00 agent_runner: starting up components...

2014-02-21 23:11:32+01:00 User specific files and directories created

2014-02-21 23:11:32+01:00 start_frontend: begin

2014-02-21 23:11:32+01:00 start_frontend: end

2014-02-21 23:11:32+01:00 start_agent: begin

2014-02-21 23:11:32+01:00 start_agent: starting agent with default config file /home/pit/.config/btsync/btsync-auto.conf

2014-02-21 23:11:32+01:00 start_agent: end

Share this post


Link to post
Share on other sites

And again a new version. Thanks to Mark for the new version - every people from non english speaking countries will be happy since the internationalization issues seem to be all solved!

 

btsync-user (1.14.1-1) unstable; urgency=low   * New upstream release 0.14 of btsyncindicator    - Implemented support for unicode characters in folder      and file names (Closes #btsyncindicator/32)    - Implemented support for web ui set in non english      language (Closes #btsyncindicator/24)    - Officially fixed the syntax error in exception      handler (Closes #btsyncidicator/39)    - Made officially compatible with Ubuntu 13.10      (Closes #btsyncindicator/9)    - Modified lockfile checking method -- Leo Moll <leo.moll@yeasoft.com>  Sat, 22 Feb 2014 18:23:42 +0100 

Share this post


Link to post
Share on other sites

RhxJue4.png

 

The same error happened again after newest update (1.14.1-1) because of btsyncindicator.py. That btsyncindicator.py internal error popup all the time before the version of 1.13.0-1. So I can say that 1.13.0-1 fix btsyncindicator.py internal problem to me.
 
Anyway, here is from terminal messages:
$btsync debug 1230Enabling verbose logging (Mask: 1230)$btsync startBitTorrent Sync forked to background. pid = 17292Traceback (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'$pgrep -u $(id -u) -f btsyncindicator.py17250

debug.txt

1230
 
btsync.pid
17292
 
and btsync-user.log
2014-02-23 13:06:02+08:00 btsync-starter: start2014-02-23 13:06:02+08:00 make_user_files: User specific files and directories created2014-02-23 13:06:02+08:00 start_frontend: begin2014-02-23 13:06:02+08:00 start_frontend: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it2014-02-23 13:06:02+08:00 start_frontend: starting frontend with default config file /home/jenhsun/.config/btsync/btsync-auto.conf2014-02-23 13:06:02+08:00 start_frontend: process is running with pid 172502014-02-23 13:06:02+08:00 start_frontend: end2014-02-23 13:06:02+08:00 btsync-starter: no running statefile detected - forking runner...2014-02-23 13:06:02+08:00 agent_runner: begin2014-02-23 13:06:02+08:00 agent_runner: starting up components...2014-02-23 13:06:02+08:00 btsync-starter: end2014-02-23 13:06:02+08:00 make_user_files: User specific files and directories created2014-02-23 13:06:02+08:00 start_frontend: begin2014-02-23 13:06:02+08:00 start_frontend: process is running with pid 172502014-02-23 13:06:02+08:00 start_frontend: end2014-02-23 13:06:02+08:00 start_agent: begin2014-02-23 13:06:02+08:00 start_agent: starting agent with default config file /home/jenhsun/.config/btsync/btsync-auto.conf2014-02-23 13:06:02+08:00 start_agent: end
 
btsyncindicator.py directly show internal error after the update. Hopefully it will be fixed soon.

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...)

Share this post


Link to post
Share on other sites

And again a new version. Should solve the problems with older Ubuntu/Debian versions.

 

btsync-user (1.14.2-1) unstable; urgency=low  * New upstream release 0.14.1 of btsyncindicator    - Restored compatibility to old versions of requests      library (Closes #btsyncindicator/43) -- Leo Moll <leo.moll@yeasoft.com>  Mon, 24 Feb 2014 11:29:04 +0100

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.