Spurious starts of the syncthing binary
See original GitHub issueDescription of the issue
The syncthing binary seems to start every now and then as i get notifications via Synctrayzor on my Windows desktop.
The problem is that the app is configured to start only with wifi+charger.
Version Information
App Version: 1.1.1.2
Syncthing Version: v1.1.1
Android Version: Android 8.0
Device model: OnePlus 3T
Android Log
I have hundreds of lines like these in the log:
04-24 21:06:31.249 W/SyncthingService( 6666): Deferring shutdown until State.STARTING was left
04-24 21:06:32.249 W/SyncthingService( 6666): Deferring shutdown until State.STARTING was left
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
weird errors and crash, new folders dont sync on new simple ...
With my local syncthing process not running, I connected to both servers and removed all the spurious files under folder1. folder1 is now ......
Read more >panic: device present in global list but missing as ... - GitHub
I am running syncthing on Ubuntu 20.04 and parallel to a system update (before actually performing the update) I got an error from...
Read more >Prevent background service from being killed due to "detect ...
The Android application wraps a native binary of the Syncthing project and provides some additional functionality like starting/stopping ...
Read more >Syncthing Jail | TrueNAS Community
But what I am struggling with, is getting syncthing to start, ... edit /usr/local/etc/rc.d/syncthing to execute the syncthing binary at the ...
Read more >Syncthing - Open Source BitTorrent sync alternative
Syncthing is a continuous file synchronization program. ... Syncthing 1.0.1 is the latest binary to "support" (it seemed to work, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m giving it a try if it happens again 😉
This isn’t easy. You would need more log history than the app outputs , I guess you won’t like to stay connected for a permanent adb logcat -v and wait for the problem to reoccur.