Skip to content
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

Synctrayzor is stuck at "Syncthing Starting..." #420

Closed
jebeld17 opened this issue Nov 8, 2017 · 9 comments
Closed

Synctrayzor is stuck at "Syncthing Starting..." #420

jebeld17 opened this issue Nov 8, 2017 · 9 comments

Comments

@jebeld17
Copy link

jebeld17 commented Nov 8, 2017

Please note that I searched the Issues list for this exact problem before reporting.

Synctrayzor and Syncthing are getting stuck at the "Syncthing Starting..." splash screen upon opening the program on Windows 10 Pro x64, v1709.

I have tried running Synctrayzor through the Compatibility Troubleshooter running both Windows 8 and Windows Vista modes, with at least the program seeming to be more responsive and active (by outputting more logs) in the Windows Vista compat mode, but I will leave that to be said by examining the logs themselves.

I have uploaded here a whole copy of my "logs" directory found under C:\Users<username>\AppData\Roaming\SyncTrayzor.

Attachments:

@canton7
Copy link
Owner

canton7 commented Nov 8, 2017

Mind cranking the log level up to Debug then giving me an updated SyncTrayzor.log?

@antonio-gil
Copy link

Uh, well, I've the same issue, but it's a different scenario as in my case it happens in a Windows 7 x64 machine.

As far as I have seen it's "somewhat" random, and the only probable cause (not quite sure how important is) that I've seen is that it seems to happen when I shutdown the machine and didn't close SyncTrayzor using the "Exit" command on the contextual menu of the systray icon, so I've the hypothesis that it could be related.

Curiously enough, that didn't happen on the other machine that I've on home, that is a Windows 10 x64 despite that I program an automatic shutdown for that one (I mention this because my hypothesis).

If there's no problem, and if I can use this thread for the issue, I'll upload the Debug log tonight, or (more) probably tomorrow (My TZ is UTC−6:00 / or CT/CST). Otherwise, I'll open a new issue and upload the log there.

Best regards!

@canton7
Copy link
Owner

canton7 commented Feb 20, 2018

Apologies for the late delay. Some debug logs would be very helpful, thanks!

@antonio-gil
Copy link

antonio-gil commented Feb 21, 2018

I'll upload them in a moment or two (kinda busy days, and I completely forgot about this)...

But, I think that I've found certain pattern (more accurate), at least in my case: it seems that this is present when the network connection isn't established yet.


Edit: I couldn't upload the file to GitHub (I don't know why), but I upload it to Google Drive.

As you can see on the events of today you'll see that the application was launched 2 (or 3) times, where the issue were present. Following that, all the instances of Syncthing were killed via SyncTrayzor, and started again, this time working as intended (twice).

The main thing is that, by reasons that I don't fully understand (yet - although I've a suspect) my laptop doesn't "get connected" as fast as I wish, and it have a huge delay until it get recognized by the network domain, so this causes that several apps hang out until the connection is established.

Also, in the log, you'll probably see that a couple of days ago (Monday?) the application started correctly, and it was because the network is established fast enough.

Curiously enough, it doesn't matter if there is internet connection or not, as in my personal laptop (W10 x64) this issue isn't present, despite the fact that I get only connected to the local network. Not sure if that makes a difference.

canton7 added a commit that referenced this issue Feb 26, 2018
I've heard of this being thrown in some cases of obscure timeout.

Relates to: #420
canton7 added a commit that referenced this issue Feb 26, 2018
I've heard of this being thrown in some cases of obscure timeout.

Relates to: #420
@canton7
Copy link
Owner

canton7 commented Feb 26, 2018

Sorry for the delay - I don't think I get notified about edits, so didn't spot you'd added the log.

There are two things going on. The first is that my attempt to connection to Syncthing's API times out after 5 minutes, rather than 70 seconds, which is what it should be. Not sure that could be causing this, probably something deep in the windows networking stack. The second is that my attempt fails in an unexpected way, which I interpret incorrectly...

Would you mind testing this build? https://ci.appveyor.com/project/canton7/synctrayzor/build/1.1.18.498/artifacts

@antonio-gil
Copy link

Hi. No problem with the delay.

Yeah, I'll check that build, and let you know what happens. Oh, and by the way, I'll be using the x64 version.

Best regards!

@antonio-gil
Copy link

Hi again.

I've been testing the build, and the reported issue seems to be gone, at least in my particular scenario.

Regards.

@canton7
Copy link
Owner

canton7 commented Feb 28, 2018

Cool! I'll get that released at some point.

@antonio-gil
Copy link

Cool, that's great!

Thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants