SyncTrayzor
SyncTrayzor copied to clipboard
canton7
config.xml got destroyed
A few days ago SyncTrayzor stoped working with this error message on startup
(haven't touched any config file):
Today a had a look an the config.xml:
It only contains 2455 \0 chars.
After deleting the config.xml SyncTrayzor is working again and the config.xml contains valid xml again.
-> So for me the problem is fixed - this issue is just for letting you know that SyncTrayzor may corrupts it's config file.
Other people have seen similar things after upgrading Windows. One person saw lots of Syncthing's log files filled with null bytes as well. I'll have another look to see if my code might be responsible somehow, but without a repro this sort of thing is hard to pin down.
I haven't heard any more of these reports, so I think they must have been related to the windows update that some people were linking it to. Closing, please reopen if you see it pop up again.
One question. Synctrayzor uses the config.xml file to store configuration (folders, etc.). This file gets corrupted and it is deleted. Synctrayzor is restarted, and the file is rebuilt, and everything works again. How? Where does Synctrayzor recover the config information (synced folders, etc.)?
That stuff is stored in Syncthing's config.xml, which is in a different place. SyncTrayzor's just holds the settings in File -> Settings.
This just happened to my father’s machine. No access to debug I’m afraid, but another sample for you - clearly not fixed.
Thanks for reporting. All of the cases that I've been able to dig into were either strongly correlated with a Windows update, or other files in the same directory were corrupted in the same way. If anyone has any information which contradicts either of those, please post it.
Happens regularly here about once a month. I wish it could be fixed. Deleting config.xml usually clears this, so no other files seem to be corrupted.
Same here, without reason. Happened on may, the 3rd (I copied the corrupted file just in case) and today as well. No system crash or whatsoever.
Can you both confirm whether the corruption is a block of zero bytes being written to the start of the file, or something else?
I cannot confirm this since it's not clear how to reproduce it. I will make sure to make a copy it happens next time.
Yes indeed, it's a block of zero bytes. File size may vary.
2020-05-03 config.xml.txt 2021-10-14 config.xml.txt
Hi All, My tip : Replace autostart registry entry with the name of this batch.
Create a batch file to start syncthing after a good backup 👍
del %~dp0debug.log del %~dp0data\syncthing\syncthing.log
7z.exe a "%~dp0backup.7z" . -r
syncthing.exe -upgrade syncthing -home=%~dp0data\syncthing
You need to download 7Zip binaries in same folder.
Regards. Sam !start - Syncthing.bat.txt
FWIW I'm still seeing this on occasion on otherwise well-behaved systems. SyncTrayzor logs and nully config
It occurred twice the last few days after Windows Update KB5016616 (os-builds 19042.1889, 19043.1889 en 19044.1889). Never had this problem before.
