syncthing-android: "Syncthing has crashed"
Hi,
after running fine for a few weeks, syncthing now crashes on my Android device.
Device: Blackberry DTEK50 STH100-2, Android 6.0.1 Syncthing Android: 0.9.7 installed via Google Play
Log has these entries:
[ABCDE] 20:15:41 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[ABCDE] 20:15:41 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (1.998999 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[ABCDE] 20:15:41 INFO: Entering the backoff state.
[ABCDE] 20:15:41 INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint' (2.992680 failures of 2.000000), restarting: false, error: "{dynamic+https://relays.syncthing.net/endpoint dynamic+https://relays.syncthing.net/endpoint} returned unexpectedly", stacktrace: [unknown stack trace]
[ABCDE] 20:15:43 INFO: Exiting
Other incident, different bug report in log:
[ABCDE] 05:40:46 INFO: syncthing v0.14.24 "Dysprosium Dragonfly" (go1.8 linux-arm64) felix@P50 2017-02-23 06:47:07 UTC
[ABCDE] 05:40:46 INFO: My ID: ABCDE-------------------------------------
[ABCDE] 05:40:47 INFO: Single thread SHA256 performance is 421 MB/s using minio/sha256-simd (10 MB/s using crypto/sha256).
[ABCDE] 05:40:49 INFO: Hashing performance with weak hash is 99.27 MB/s
[ABCDE] 05:40:50 INFO: Hashing performance without weak hash is 308.89 MB/s
[ABCDE] 05:40:50 INFO: Weak hash disabled, as it has an unacceptable performance impact.
[ABCDE] 05:40:50 FATAL: Cannot open database: resource temporarily unavailable - Is another copy of Syncthing already running?
[ABCDE] 05:55:29 INFO: Disconnected from relay relay://195.154.107.80:22067
[ABCDE] 05:55:29 INFO: Exiting
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 34 (18 by maintainers)
Commits related to this issue
- On exit code 1, kill Syncthing and retry start (ref #865) — committed to syncthing/syncthing-android by Nutomic 7 years ago
@jebeld17 That was me you were talking to. You first sent a question about whether to report bugs to security@ given that the logs have Syncthing IDs in them. I responded like this:
You then sent me a log saying essentially “are you sure I can’t report this crash here instead”, to which I responded:
Certainly this is more curt than the first message, but you also didn’t heed the first message. I’m not telling you to go fuck yourself. I’m telling you to use the channels for reporting things like they are intended.
@Nutomic Thanks for the crash notification option!
@calmh Is there any way to tell from exit codes that Syncthing was stopped because another instance is already running?
And I will make an option for the crash notifications (off by default).
You both made a little sheep feel happy. There are no more crash warnings. 🥇
Sorry people, I drank a little and got a tad off-hand! xD I apologize for my interruption.
https://www.youtube.com/watch?v=30kS2Kr7YjQ
I noticed that I implemented the log file trimming wrong, so it would keep the first 10k lines of the log, instead of the last 10k. So if you check the log after Syncthing was started again, it might not actually contain the crash info.
@AudriusButkevicius @calmh Can these kind of errors cause a full restart of Syncthing? If so, how can I detect (and ignore) such errors?
Absolutely not sure. Those might be actual crashes that should be investigated.
What I was implying is that many “set it and forget it” setups are now producing a lots of “noise”, while some users can’t really act on this “noise” (hence my proposal to make it "opt-in). For example - I’ve set ST for some of my relatives’ phones more than a year ago. “Mostly” it is working, occasional disconnects here and there, but mainly working just fine. Files fly from PC to phone, from phone to PC. But since 0.9.7, while it seemingly work as before (files fly around), now some of them have “crush” notifications about once every couple of hours.
BTW: I got logs of one such device, and it’s mostly clean. lots of “restarting after sleep” (I guess that’s the way it handles wifi-only run condition). The only legitimate errors I’ve found are few of those:
and
The “Syncthing has crashed” notification was added here recently: https://github.com/syncthing/syncthing-android/commit/245470a9d40996f40119918f94c51f9c776e873a
I guess it’s good for debugging, but “in general” it’s a bit too much IMO. Especially on older, low memory devices it “crashes” quite frequently (seemingly auto-relaunches after a while). Since 0.9.7, my friends/family with somewhat old phones, all complain that it “crashes” for them many times a day. Most of them are “not techy enough” to be able to submit reports, and mainly are just confused and annoyed by it.
Maybe it should be an “opt-in” thing, idk…