This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
Syncthing Binary Crashed - error code 2 #92
Labels
Comments
alexxtasi
changed the title
|
Could you post a logcat? |
|
I don't know how to do that... is there any file somewhere stored? explain me a way and I ll provide logs.. |
|
Here's a guide, there should also be lots of info on Google ;) |
|
using catlog... the message appeared more than once so the log I am providing is big... |
|
Your phone needs ARMv5, I checked the binary in the armeabi apk and it's correct. Do you get the same error with the armeabi apk from Github? |
|
I installed syncthing-android-armeabi-release.apk as you suggested (tried both installing it and unistalling the prior version and then installing) but the same thing happen (not sure for the error code No.) Then tried the same with syncthing-android-armeabi_v7a-release.apk and error code 127 came up. In this case catlog says : |
|
Your device is ARMv6, so it can't run the armeabi-v7a apk (although the logcat contains nothing about that). But the error code for the armeabi (not v7a) apk would be the most interesting. |
|
so I did
the same happens with error code 2 I hope this helps more... |
|
Okay weird. @calmh Could you have a look at this? ( |
|
Mmmyeah, so how is the binary built (is it mine from a release)? There's some trickiness about building for ARM that I might have screwed up in the latest release(s), where if you're not careful the binary is built for for example armv6, but the standard library is built for armv7 anyway. |
|
I build with this build script. I can make an apk with your binaries to test, though. |
|
Try it, to see if there's a difference. Otherwise, the thing I was thinking about was making sure GOARM=5 is set when compiling the Go toolchain for ARM. |
|
Okay, try this one. |
|
Just tested the apk you sugested. Syncthing starts with no errors, but seems to not work well... (no api preperation popup, menus don't work well, no announce server or CPU/RAM usage, no web gui...). I don't know if this .apk is intended to work so... anyway this is the log file at first run after installation: |
|
Looks like it doesn't execute the binary (but I don't see an error about that, only that it can't reach the API). Could you try uninstalling, then rebooting and installing again? (if you haven't done that already). |
|
Sorry I was away for some days... don't know if it's useful ... this is the log while installing the .apk : |
|
Yeah, I see no syncthing log data in there unfortunately :( |
|
Yeah the log messages all seem to be about the fact that it can't reach the Rest API. If you grab a syncthing binary and run it on your phone via shell, what happens? |
|
Hi again well I tried to run syncthing as a binary from command line with no success.
I am probably doing it the wrong way so please correct me... |
|
The binary might not be executable if it's on sdcard (not sure, you can try If you have root, you can just |
|
I have the same issue. Using the shell commands you suggested, I get this: http://pastie.org/private/uat4ljoeacz0frmxoxt64a |
|
Hi again, also I can't set the config file ? |
|
Ah you need to run |
|
thanks Nutomic and nothing else was shown in the terminal!! the log file is : seems like syncthing is not running !! |
|
If you run it directly like this, you won't get any logcat (that's redirected by java). You'll just have to wait for the keys to be generated, and it should run normally after that. |
|
finally !! :-) but the gui was still not working well (eg no announce server or cpu info) and when trying to create a new repository this came out "The syncthing binary has exited with error code 1." and crashed. Hope this is more helpful at last..... |
|
v0.9.5? o_O |
|
actually I used syncthing-android-armeabi-debug-issue-92.apk as Nutomic suggested. It's v0.5.0-beta1 (probably using syncthing-v0.9.5 ??), but your are right... he's suggestion was many days ago (I am too slow ;-)). I will install the latest release from google play and run the command again. |
|
so I have
|
|
Okay this is a different issue than before, looks like I did something wrong in the Java code. Will fix. |
|
Actually, I read the log wrong. This apk should not crash when creating the notification, and then I'll need a log of tag |
|
It just hangs while "Generating keys. This may take a while." !! and the log is: does this help ? |
|
Damn I just noticed that I built with Go 1.3.1 when there's already 1.3.3 out. Could you also try this apk please: Sorry for all the trouble :/ |
|
no bother the log (filter = and running again after forcing the app to close is: |
|
I'm sorry but I think the previous apk was wrong, could you try this one, too? I promise this will be the last before I report it to golang :s |
|
success!! don't you think ? ;-) |
|
The latest APK you posted worked for me as well. |
|
Can't figure out the changes you made and what the problem was.... but I see this apk works!!! thanks Nutomic !! |
|
I updated the Go compiler from 1.3 to 1.3.3 ;) Glad it worked! |
|
Hi again I am running the same syncthing version as before (latest apk file you posted) and this happens:
Have to say that the message regards |
|
Seems like it happens when restarting syncthing after network connectivity changes, and maybe the old instance isn't fully shut down yet. I'll make an apk with extra debugging so we see if that's really what's happening. |
|
Also, can you still access |
|
I'll try it again and report |
|
Here's an apk with additional logging It should print a message (with tag Edit: You can also just install 0.5.9 from Google Play or F-Droid ;) |
|
for your question... I'll install the new apk and test as soon as possible. |
|
I provide two log files. 1st - the 2nd - In both cases I can't see what do you thing ? |
|
Ah it could also happen because you set "Always run in background" and have "Sync only when chargin" checked, and then change the charging state. In some way, it seems to start a new instance before the old one is shut down. Can you figure out any specific steps to reproduce, including your current settings? Otherwise I'll try to log some timings for the starting and stopping. |
|
Actually I have not done any changes in the configuration. I have not set "Always run in background" or "Sync only when charging" checked. Just while the test (coping the log) my phone was charging ! (by the way, these options seem to be disabled - cannot check the box) Can not find out any steps to reproduce, sorry In my configuration, I have just setup a node and a shared directory (with about 25 mp3 or ogg files there), which was setup and synced at the first place (since my first syncthing installation). Maybe at the end, this is minor (sometimes happens sometimes not)... I will report again if I find any steps for this |
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
acolomb
pushed a commit
to acolomb/syncthing-android
that referenced
this issue
Nov 12, 2023
syncthing#92) (syncthing#94) Remove shared pref "advanced_folder_picker" and make it default to enabled - only relevant for Android 4.x
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I just updated syncthing to version 0.4.8 using Google Play (I suppose this is the version due to the comments... "disallow adding the same node multiple times" ...)
When running, this popup comes:
Syncthing Binary Crashed
The syncthing binary has exited with error code 2.
If this error persists, try reinstalling the app and restarting your device.
I've tried both but still happens...
any suggestions ?
(I am using android-2.3.7 - CyanogenMode-7.2.0-blade, on ZTE-Blade)
The text was updated successfully, but these errors were encountered: