Skip to content
This repository has been archived by the owner on Dec 3, 2024. It is now read-only.

FR : Properly killed syncthing binary #96

Closed
blurmonk opened this issue Aug 21, 2014 · 7 comments
Closed

FR : Properly killed syncthing binary #96

blurmonk opened this issue Aug 21, 2014 · 7 comments

Comments

@blurmonk
Copy link

Hi

One of the main issue I have with this tool is that it never kills its own process when exiting or restarting it. Restarting it via the gui is almost useless because it never restarts properly and at times I have to just restart my tablet which is an inconvenience. Not a life threatening issue for sure but it would be nice if restarting is done properly so we could test things out much easier.

Sometimes I kill the process using android`s running apps but then it is not a solution because recurrent restarts of this app ends up in crash at start with some message

"
Syncthing Binary Crashed
The syncthing binary has exited with error code 2.
If this error persists, try reinstalling the app and restarting your devic

It seems like when a health ST restart is needed, the best way is to restart the tablet.

I hope that the dev could address this issue so that we could test out versions with a nicer setup

thanks

@Nutomic
Copy link
Contributor

Nutomic commented Aug 21, 2014

This error shouldn't usually occur, and restarts/exits work fine for me.

What device and Android version do you have? Logcat would also be helpful.

@blurmonk
Copy link
Author

I will get back to you about this.

I have this issue with multiple devices, it has been there since I started testing ST for android for couple months.

thanks

@firecat53
Copy link

I've noticed this when trying to restart the GUI too quickly. If I wait 15-20 seconds before restarting it seems to be fine.

Scott

@the-solipsist
Copy link

I've experienced the same problem. At times the app has hung (with very high CPU usage) while displaying the "Waiting for API" message. Despite waiting a few minutes nothing happens.

Then I:

  1. SSH into my phone and use htop to track processes.
  2. "Force stop" Syncthing using the GUI (System > Apps > Running Apps)
    -> Nothing happens.
  3. At the terminal I do: # killall libsyncthing.so
  4. The process respawns and hogs the processor even more (up to 160% CPU).

At the end, I have no choice but to restart the phone.

@Nutomic Nutomic added the bug label Oct 7, 2014
@ovizii
Copy link

ovizii commented Oct 8, 2014

I'Ve experienced the "Waiting for API" hanging quote often but didn't go as far as yourself to track it down so I cannot contribute any insights.

@Nutomic
Copy link
Contributor

Nutomic commented Oct 12, 2014

This should not happen any more with 0.5.x, because any leftover syncthing instance is killed on start. Only if there's another app or another syncthing instance (with different API key) running, this could still happen. But then a device restart should fix it.

But it will only be properly fixed by #46.

@ovizii Could you post a logcat please?

@ovizii
Copy link

ovizii commented Oct 12, 2014

Sure but keep in mind it's working fine right now. http://pastebin.com/acjW5QpX

Zillode added a commit to Zillode/syncthing-android that referenced this issue Mar 28, 2015
Zillode added a commit to Zillode/syncthing-android that referenced this issue Mar 31, 2015
@Zillode Zillode closed this as completed in 65e090f Apr 1, 2015
@syncthing syncthing locked and limited conversation to collaborators Nov 9, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants