-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
Crash on Startup #381
Comments
Found the Error, two instances of SyncTrayzor Running with syncthign using the same port for GUI |
Is that the actual message, or does the third line actually say "System.Exception: Unable to find Syncthing at path C:\Users<You>\Whatever"? |
No, two instances of SyncTrayzor running together will not cause that error. It was more likely your AntiVirus removing syncthing after SyncTrayzor started, but I can't be sure from the information I've got so far. |
This is the actual messege which I copy & pasted |
So in Settings under Listen Adress for the GUI I changes the default port from 8384 to 8380 on one and to 8381 on the other instance, now it works |
Again, multiple instances won't cause that error. It's looking for syncthing.exe, but it hasn't been told where to look, for some reason. Can you post (or email me) your entire log file? Go to Settings -> Logging + STTRACE -> Show SyncTrayzor Log File. |
Here is the complete Log:
|
it only accours if you bind the GUI to 0.0.0.0:portx - so localhost:portx won't crash, Anitvirus is Avast - so maybe it has something to do with it, you never know with this damned snake oil :-) |
Looking through the log, something else is broken too: it should successfully find a free port to start Syncthing on, but that's failing. |
Aah, I follow. That first error caused the error which you reported. Nothing to do with AV in this case. |
User reported that FreePortFinder was failing to find a free port when another instance of Syncthing was running - it was rethrowing the exception after the first attempt, which means it's a SocketError I wasn't anticipating. There isn't enough information to say what SocketError it was though. Just continue on all of them. We'll give up after a few anyway. Fixes #381
Mind trying this build (when it finishes) with the gui listen addresses / ports which made it crash before? https://ci.appveyor.com/project/canton7/synctrayzor/build/1.1.16.472/artifacts . Thanks! |
Sure, I hava a look at it in the next minutes |
Crap, this built is getting blocked now by avast |
Hah, nice. |
Okay, the new Version does not crash, it just picks the next free port: |
Awesome, thanks for checking. |
See #354 |
@etraff, I had a similar issue with Kaspersky in the past. Kaspersky's heuristics blocked Syncthing, not at the fault at the developers of either program, though. Kaspersky's machine learning simply did what it was meant to do: block things it may deem a threat, because of permissions the app may or may not have, being an otherwise 'unknown' program with different code, etc.. Note I didn't even need to whitelist the programs; Kaspersky's team got in contact with me right away to update their whitelists and improve their heuristics. :-) |
#354 is a completely different issue. This issue turned out to be unrelated to AV - I thought it was due to AV at the start, but I was wrong. |
OS: Win 10
The text was updated successfully, but these errors were encountered: