To set an env var you put it before the command, i.e. STRECHECKDBEVERY=0 syncthing ....
You get the same thing when starting with -reset-database? Then please do so again and run with STTRACE=db syncthing -reset-database 2>&1 >path/to/place/the/huge/logfile.log. Be warned, the logfile will be huge, that’s expected and necessary. Then please make that file available through whatever service you like (we could actually even setup a syncthing folder for that ).
It has to be STTRACE=db /var/packages/syncthing/target/bin/syncthing ... And I doubt you really want to log to /path/Syncthing_log_Synology_DS1815.log. If you don’t have any data/home directory, at least use a dir that already exists (/media, /var, /opt, …).
I deleted the peers with double values and reconnect them. So such peers are reworked for now, but I´m not sure, if the values I see in the GUI for each peer are right. It seems so, if I compare with the folders in the Synology DSM, so is more or less the same, I have to consider, I use Ignore Patterns.
All seems right now, but I wonder me during the last days, because if I upgrade from v1.3.4 to v1.4.x, the whole no. of files increases from about 1,38 Mio to now 1,79 Mio. I doent know why.
I don’t know. That’s why I asked if you can indeed reproduce and then get logs:
Please consider the advice you are given and if you decide to not follow it, please say so, ideally giving a reason. Even if just “too cumbersome, no time” - that’s clearly perfectly valid. It then prevents the person giving advice (me) spending more time for nothing. Thanks.
I know, but it doesn´t run. I try different possibilities, but there was no reaction and the log was created in the setted folder, but was still empty.
I executed the command with the corrections directly in the storage path of Syncthing, I tried that with PuTTY, with WinSCP, both with root rights, to do nothing. I have already commented on this above.
It probably was just fine, the command just logs to the file only, i.e. you see nothing happening on the command line. To see what’s happening use tee, i.e. adjust your command line to something like this: STTRACE=db /var/packages/syncthing/target/bin/syncthing ... 2>&1 | tee ..., i.e. replace > with | tee.
How long did you wait? There’s nothing wrong with that command as far as I can see. tee does buffer the output, so that might just be the reason it takes a while.
If running a file in the current directory, you need to prepend ./, i.e. /var/packages/syncthing/target/bin$ STTRACE=db ./syncthing -reset-database 2>&1 | tee /volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log
Also you can try the following instead: STTRACE=db /var/packages/syncthing/target/bin/syncthing -reset-database -log-max-size=0 -logfile=/volume1/PublicSharings/SyncthingExchange/Syncthing_log_Synology_DS1815.log