All folders showing unknown after upgrade


(Lee) #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


(Audrius Butkevicius) #2

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


(Lee) #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.


(Audrius Butkevicius) #4

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


(Lee) #5

Here is a screen shot from my web browser:

Here is the Synctrazor settings folder tab: image

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


(Audrius Butkevicius) #6

Can you provide the logs?


(uok) #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?

(Antony Male) #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.


(to_be_deleted) #9

I had the same problem after upgrading from 0.14.47 to 0.14.48 on two linux amd64 nodes.node1_after_upgrade_log.txt (11.7 KB)


(to_be_deleted) #10

I also noticed another problem but I don’t know if its related to this issue. In the log posted above I have “mismatching index” entries

2018-06-07 11:25:14 Established secure connection to 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH at 10.10.10.160:57838-10.20.10.160:20081/tcp-client (TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305) 2018-06-07 11:25:14 Device 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH client is “syncthing v0.14.48” named “HSTNAS01” at 10.10.10.160:57838-10.20.10.160:20081/tcp-client 2018-06-07 11:25:14 Device 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH folder “Archiv” (ngnzq-fyq6p) has mismatching index ID for us (0x1E88916BF6AA21A9 != 0x4350D9037E29136E) 2018-06-07 11:25:14 Device 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH folder “Archiv” (ngnzq-fyq6p) has a new index ID (0xBEF85B7006858238) 2018-06-07 11:25:27 Device 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH folder “Images” (nux7m-yfmea) has mismatching index ID for us (0x29D0D01A583B7A13 != 0xC585779B52DACFB3) 2018-06-07 11:25:27 Device 7E4EKDA-DEXQAEY-DIKXM2L-6XO7YWS-ARPGAW6-CRUSAI7-U2U5UMP-CCZKRAH folder “Images” (nux7m-yfmea) has a new index ID (0xC86C473AFF721E04)

Should this go to the issue tracker on github Cc?


(Audrius Butkevicius) #11

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


(Lee) #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.


(to_be_deleted) #13

@Lee: Yes, the unknown got away by waiting a little bit more time after upgrade. Everything up and working now.


(system) #14

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