Latest builds can be found here: https://build.syncthing.net/viewType.html?buildTypeId=Syncthing_Tools&branch_Syncthing=<default>&tab=buildTypeStatusDiv
Click on the build number and go into artifacts tab.
1 Like
Hiya
OK, so worked out it is linux_amd64.
And copied the file to the NAS and moved to the bin folder.
I’ve then chmod +x to make it executable.
I can see the file and I’m in the folder, but I’m getting stindex: command not found
Maybe you need to start with ./ so it means ./stindex
Thank you. This is all so basic, thank you. Assume I need to specify the DB folder
stat /var/services/homes/mark/.config/syncthing/index-v0.14.0.db: no such file or directory (is another instance of Syncthing running?)
It is always forgotten to say that syncthing has to be stopped. In the case of Synology via the package center. You can check this with ps -e | grep syncthing and if there are problems, initiate the stop with killall syncthing.
Hey - it’s not running, and the ps command showed that. It’s the folder to the DB I think. I had it before
stindex is quite RAM-heavy - so if your DB is of any size, you might have problems running it on the NAS itself.
In which case, you can grab a copy of the DB and transfer it to your Windows machine for analysis:
- Stop Syncthing on the NAS;
- Log into the NAS under SSH as admin;
- Elevate yourself to root user with
sudo -i - Copy the DB folder to an accessible shared folder on the NAS with
cp -R /usr/local/syncthing/var/index-v0.14.0.db /volume1/(shared folder name here)
- Copy the DB folder onto your Windows machine;
- Run
stindexwithstindex -mode idxck (path to DB folder here)
Can you specify the command you used.
One noticeable thing is “homes/mark”: Usually it is not plural, i.e. “home/mark”
Hey - the command I used was the one above without a path to the DB folder.
How can I find the path to the DB folder on my system?
Under Windows in User AppData
You can run syncthing -paths I believe which will show where the db is.
1 Like
So I get:
Configuration file:
/var/services/homes/mark/.config/syncthing/config.xml
Database directory:
/var/services/homes/mark/.config/syncthing/index-v0.14.0.db
Device private key & certificate files:
/var/services/homes/mark/.config/syncthing/key.pem
/var/services/homes/mark/.config/syncthing/cert.pem
HTTPS private key & certificate files:
/var/services/homes/mark/.config/syncthing/https-key.pem
/var/services/homes/mark/.config/syncthing/https-cert.pem
Log file:
-
GUI override directory:
/var/services/homes/mark/.config/syncthing/gui
Default sync folder directory:
/var/services/homes/mark/Sync
Except when I cd / to the var/services/homes/mark folder there’s no .config folder.
So if I stindex -idxchk passing in the full folder to the DB folder - I’m getting the same error message.
I’m happy to temporarily allow someone remote desktop access if it would help. I appreciate this is trying to help me, help you … but I’m wondering if you’ve all had enough and it might be easier and quicker to take over 
I’m happy to continue either way
Dot directories (starting with .) are not visible using ls unless you pass in the -a option.
Also those paths are only correct if you run Syncthing as the same user and with the same environment and parameters as when it runs “for real”.
You’re on a Synology which is a really odd environment; the database will be somewhere under /var/packages if you run the synocommunity package, and it’s not guaranteed to be accessible by the user you log in as.
We generally say that you should run Syncthing on a normal computer, and the more I’ve worked with these NASes the more I’m convinced that’s the right stance.
1 Like
It is a question of philosophy. Basically, a NAS is always a server and not a regular computer that is considered as client. The perspective must be corresponding. A Synology differs little from a normal Linux server. However, there are differences that you have to know.
There is a clear separation of access rights between users and APPs at the Synologys. Users must have permissions to APPs and folders and APPs must have permissions to folders. If one or the other doesn’t fit, nothing can work. However, everything is clearly configurable via Synology DSM.
I’m not sure if any of this has been any use so far to you.
I’m close to just calling it quits to be honest. Absolutely no offence to you guys but I honestly need to be running a business and put my efforts there and need a sync software that just works. There isn’t one out there. Not one. Even the Synology ones provided don’t work.
Is Synology a common platform for Syncthing? Is it worth trying to nail this or not?
Sorry if I sound a grump - again it’s not aimed at you
Did you ever encounter anything that didn’t work that wasn’t the remote devices completion? I am not saying it’s ok that this doesn’t work, but as long as folders show the correct status and are in sync that’s just cosmetic. And we are working on fixing that too, so before if it really comes to abandoning, please retry after
@anyoneknowingSynology: Is the system too borked to just run the Syncthing binary directly instead of a synology package? And have all the config and data in self-created folders free of black-magic-ACL.
marky_uk, In short, Syncthing is very suitable for Synology, also on Windows and Android. You have one alternative, but not the tools from Synology itself, because they are have always been unreliable with these mass of datas to be synchronized.
I will briefly tell you my story so that you know what I mean:
Since BTsync 1.0.128, mainly 1.4.111 I have been a productive user of this software, now with Resilio version 2.6.4. Resilio runs on 4 Synology servers, 5 Windows clients, 3 smartphones, 2 Tablets. The software is very reliable, constant observation was not necessary in the past. But the advances in Linux, Windows and Android mean new problems and bugs are coming up again and again. Unfortunately, the update cycle at Resilio is no longer practicable and very much to long.
Two simple examples with big consequences: The app keeps freezing on Android and in the meantime the Windows service cannot be installed in some cases on Windows builds >190x.
The first meant that I was forced to weave in Syncthing, which is possible with the right ignore patterns, so that the Android systems work smoothly - just embarrassing. One of the servers has now been completely switched to Syncthing and the coexistence of Resilio and Syncthing is working smoothly.
If the update cycles continue like now, I will have to change to Syncthing completely in the long run, since the administration is correspondingly more complex. In addition, Resilio wasted a lot of time and allowed Syncthing to become just as good and reliable, which was not always the case. It has also become more flexible in terms of features. The only real advantage of Resilio would be the selective synchronization, timely I use on Android, but currently I doesnt use. If Resilio allow Syncthing to completely overtake, it’s there own fault.
Finally the problems with permissions and so one are sometimes similar and I have to maintain in the same way. I am also a self-employed person and can understand that you need a quick solution, because all tests also require time and capacity. This laboratory work doesn’t help, I also found out. So in the end I just stopped syncthing on all devices, deleted all databases and started syncthing on all devices again. Since then everything has been going well. And dont forget regarding your Synology DS713+, Ignore permissions on “Yes” for each peer (folder) … 
@imsodin hey hey. Yes I have had the most wonderful of instances when all have been synced perfectly. Life is good when that happens. There have just been many instances where the sync goes out but then requires a lot of manual intervention to get it back on track - like this particular instance.
When the Scan happens, it looks like my scenario is not being checked for. Is that all that needs to happen here?
I’m more than happy to test anything anyone wants if it helps.
As I said, it has me going radical here - am I the only one with such issues? Do all Syncthing devices report back so you have details of who is suffering in silence? (I assume not re data privacy). Do you know how many people use the app on Synology devices?
You are not the only one, as already written. I also had problems and I said how I dealt with it because nothing helped me either. And if you follow a few rules, I’ve already described them all, it goes very well. Also, in which way I´m maintain regarding permissions and so one.
How many users have Syncthing installed on the Synologys is difficult to understand. If I look at the download numbers that you can see only for Synologys alone in the package center:
Syncthing (SynoComm.): Not specified
Syncthing (Kastelo): 0
Resilio: 29.973
The 29.973 only show the downloads from the DSM package center. Resilio has its own Synology page, in which any architecture can be installed manually. I always use that. This download platform is well known and many downloads also take place there, so in summary personally I guess there are roughly 50.000 downloads.
I assume that those who use Resilio also use Syncthing to a large extent to change from resilio to Syncthing or set up mixed activities or to make tests because of interest. I´m also started in 2015 with v0.12 and with first tests because of my interest. First I tested extensively, then I set up the first tasks with v1.x.x and today I have been productive since v1.3.3, see above.