All folders showing unknown after upgrade

Support
1

I am currently running Syncthing on 5 machines. 3 of the machines are Windows 7 Pro and 2 of the machines are Server 2012 R2. I am running SyncTrayzor 1.1.21 on all of the machines. I just re-enabled the auto upgrade feature to allow the machines to upgrade from 0.14.44 to the latest 0.14.47. Everything appeared to work great on all of my windows 7 machines and one of the Server 2012 R2 machines, however, the other Server 2012 R2 machine shows a “unknown” status on all of the shared folders. Is there any way I can force another upgrade to maybe correct whatever went wrong during the initial upgrade?

Thanks Lee

2

You probably need to force refresh the page. If that doesn’t help, check the logs.

3

Refreshed and got the same results. Nothing looks out of the ordinary in the logs, however, I went into the SyncTrazor settings screen and clicked on the folders tab and received the message “Folders unavailable. Please start Syncthing.”. When I list the processes in task manager, Syncthing is indeed running.

4

I suggest you try to access the web UI from a browser and see what happens.

5

Here is a screen shot from my web browser:

image
image.png1163×658 12.9 KB

Here is the Synctrazor settings folder tab: image

I have also tried to reinstall Synctrazor, but had the same result.

6

Can you provide the logs?

7

@lee3521

  • are the folders syncing or not?
  • SyncTrazor has lost connection to Syncthing - missing API key?
  • can you connect to Syncthing via browser? same error?
  • are there errors in the browser javascript console?
  • are there differences if you compare old vs. current config.xml?
  • are there differences if you compare config.xml from broken vs. working machine?
8

The API key won’t be an issue.

Grab the syncthing logs (there are log options on the menus of both syncthing and SyncTrayzor). It’s probably just taking a very long time to start up, but let’s see.

11

I think it’s just sorting and sending indexes, or computing the new key space (not sure if that got merged yet).

12

catfriend1, Your issue is most likely related to this post reason for: ... has mismatching index ID for us (somehex != someotherhex) ...

My unknown status fixed itself. As it turns out, my server was just under a very heavy load and was taking a while to start up.

14

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.