Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

btsync-gui: Unknown gui issue #160

Open
meoso opened this issue Sep 15, 2014 · 8 comments
Open

btsync-gui: Unknown gui issue #160

meoso opened this issue Sep 15, 2014 · 8 comments

Comments

@meoso
Copy link

meoso commented Sep 15, 2014

i was running 1.3 without issue for about a month. v1.4 came out ; today i'm having gui freeze / complete desktop freeze. my only option is to ssh in and sudo kill btsync-gui and btsync-core. i cannot run btsync at this time. (deb http://debian.yeasoft.net/btsync jessie main)

here is my /var/log/messages: http://pastebin.com/8t4k5Kv6

Linux skynet 3.14-2-amd64 #1 SMP Debian 3.14.15-2 (2014-08-09) x86_64 GNU/Linux
XFCE 4.10

@tuxpoldo
Copy link
Owner

Two questions:

  1. How many shared folders and how many peers per folder approx.?
  2. Have you tested to access the BitTorrent Sync engine via the Web UI? Was it still running?

@tuxpoldo tuxpoldo changed the title unknown gui issue btsync-gui: Unknown gui issue Sep 15, 2014
@meoso
Copy link
Author

meoso commented Sep 15, 2014

client to 2 shared folders. (very large subset of files/folders 22GB w/ 3peers & 52GB w/2 peers)
webui still running and therefore btsync operational.

panel's icon no response (freeze).

after multiple tests, i found the "whole desktop" freeze only occurs if i try to use the panel icon within the first few seconds. (before the first "rotating" animation)

@tuxpoldo
Copy link
Owner

BTW: This is a duplicate of #139 - but since you provided more information, we should continue the discussion here. Can you please try to run the GUI from the command line with

btsync-gui --log DEBUG

until the freeze happens? I would like to know the adjusted timings. You see them in lines like:

DEBUG:root:Last cycle duration was 32 msec - Adaptive timeout changed to 1000 msec to avoid API flooding
DEBUG:root:Last cycle duration was 34 msec

@tuxpoldo
Copy link
Owner

If you launch btsync-gui from the console, you can see all the messages on the console. Nevertheless there is also a log file. It should be located in ~/.btsync

You can send the file by E-Mail.

@meoso
Copy link
Author

meoso commented Sep 15, 2014

not much output before crash (tried twice):

2014-09-15 15:54:23,312 - INFO - Starting btsync agent...
2014-09-15 15:54:24,861 - DEBUG - Converted retries value: 0 -> Retry(total=0, connect=None, read=None, redirect=0)
2014-09-15 15:54:24,861 - INFO - Starting new HTTP connection (1): localhost
2014-09-15 16:01:18,613 - INFO - Starting btsync agent...
2014-09-15 16:01:20,168 - DEBUG - Converted retries value: 0 -> Retry(total=0, connect=None, read=None, redirect=0)
2014-09-15 16:01:20,168 - INFO - Starting new HTTP connection (1): localhost

@tuxpoldo
Copy link
Owner

OK - Tomorrow I will analyse the code and see what could be happening. One question more: on which platform are you running (CPU/MEM)?

@meoso
Copy link
Author

meoso commented Sep 16, 2014

from lshw -short
15GiB System memory
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz

pastebin of /proc/cpuinfo and /proc/meminfo http://pastebin.com/q8ADXMmw

running Debian Jessie 64bit with XFCE 4.10

@meoso
Copy link
Author

meoso commented Sep 16, 2014

i found that the official cli-only btsync also produces the kernel trace dumps (/var/log/messages), therefore those are unrelated to the gui issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants