Andy+
-
Posts
584 -
Joined
-
Last visited
Posts posted by Andy+
-
-
I would recommend several intermediate steps. All measures that are implemented must also be tested in detail and may have an impact on different functions. In addition, the trust of the community would increase again if there was an update every month or like that. Small and many steps with security are better than a big one, which contains not so much security.
-
Since BTsync 1.4.111 I have been a productive user of Resilio, now with 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 up to date.
Two simple examples with big consequences: The app keeps freezing on Android and the Windows service cannot be installed in some cases.
The former 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 completely in the long run, although I don't really want to, but 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 would be the selective synchronization.
So I say: Resilio takes care of your community intensively, making it the best advertisement in many companies. If you allow Syncthing to completely overtake you, it's your own fault.
-
On 2/2/2020 at 2:46 AM, luomat said:
Looking at the change log and the forum posts for the last three releases:
2.6.4.1344 - December 27, 2019 - contains literally one fix
2.6.3.1340 - January 14, 2019 - 4 lines in the changelog
2.6.2.1330 - November 22, 2018 - 10 lines, a reasonable release
So we had two releases in all of 2019, and one of them was literally just a single issue security fix.
We went through all of 2019 without a significant release. It's not unreasonable to hope for something more if you want us to believe the app has not been abandoned. As for Frank's complaints about apps that update "too often", well that hardly seems relevant.
Maybe there's a huge 3.0 waiting in the wings… but if that's the case, I hope a beta will be coming out soon.
Doe you have any information about regular updates, which consider all the bugs? Or information about next update before end of the year?
-
If you follow the last cycles of updates you can count. So, patient and waiting is needed.
-
Felt has nothing been in the software for a longer time. The update from 2.6.3 to 2.6.4 was an inevitable patch. If you read through the threads, you will read about bugs that would justify regular updates. In this way it was used in the past. I see it in the Syncthing Forum that loyal Resilio fans are migrating.
-
Thats a good issue, I think. And also to place in the new feature section:
-
You are willcome.
-
There are a few key signs to look out for. You have the values and information parameters size, local size, files, local files and status. You also have to take into account that the peers, remote or local, also store ignore patterns. Then deviations can also occur.
Otherwise, the information should be the same locally and globally.
If the percentages do not go away, it indicates difficulties in compensating for differences. Then you should correct the permissions etc.
-
What are resource forks for you? Doe you have any examples?
-
You have to go the opposite way and register the server with the clients. Then this message does not appear and all clients registered at the server.
-
The current Resilio CLI have a very small tool set and nothing for debuging and maintenance. The last features would be good by problems an others, e.g. to have logs, to maintain or reset the database, to show processes etc., etc.
-
It would be good to have a drop down possibility to choose set "Send only", "Receive only", "Send and receive" for each peer.
-
Sorry, again and again we hear the same, also in other threads. Your software is still good, but the bugs are not getting any smaller.
In the meantime, the Sync service can no longer be installed on Windows 10, as various threads show here. The Android APP has to be started every time you want to sync, because it freeze and nothing else happens, etc. etc. Partly inflexibility, I can not set "Send only", "Receive only", "Send and receive" as example for new features.
Because of the thing with the Android APP, I am sometimes forced to switch to Syncthing, which forces me to combine Resilio with Syncthing. Nobody understands what's going on here anymore. Alex doe his best, but honestly, he's just patching around.
I think there would be a lot more posts about bugs and problems if the forum were really active again. That would significantly promote and advance the development. But that doesn't happen because everyone now knows that nothing solid or sustainable is happen anyway. Always patchwork.
-
Same as here
https://forum.resilio.com/topic/71783-sync-service-wont-start/
I dont know the solution, maybe a compatible mode or admin mode is running.
-
Maybe test Syncthing to have that feature.
-
Did you set up the ignore patterns on both peers or all peers?
-
Maybe */* or /*/*
-
You can do this on the DS via the control panel as follows:
DSM > Control Panel > Security > Tab: Certificate
-
For that we have this forum. But honestly, it´s better for you to have some own tests. I would play with compatibility mode or administrator mode or something like that. A question would be also, if you have any scanner you can switch of (virus, malware, etc.) or any other software, which could be block your activities.
-
Maybe the support tell us uncommented CLI syntaxes.
-
What the meaning of DHT? Maybe is needed in the modern China, in which sometimes the thing restricted anyway.
-
Installation as service or starting as admin or in a compatible mode.
-
Resilio seems to have no CLI. The best case is, to disconnect and reconnect the affected peers.
-
I recommend testing Syncthing well because there are a few things to consider as well.
I mainly use 3 Synology servers, 5 Windows clients, 3 Smartphones with Resilio. I haven't had any data loss so far, but there are inconsistencies, some of which are mentioned here. Because of this, I have now also installed Syncthing in parallel on all devices and with appropriate ignorelists there are overlaps in the same directories possible. In comparison, Resilio is the reference for me, although Syncthing is catching up and running just as well. Because the Resilio APP does not start reliably on smartphones, syncthing is now installed everywhere. Overall, it have pros and cons and each package has its advantages and disadvantages, so I use both in parallel.
However, one thing is clear, the support at Syncthing is completely different than here, everyone can get an idea of it "https://forum.syncthing.net".
How such deletions can occur is at least a mystery to me. I have never had anything like this, but I consistently and everywhere use the latest version, now v2.6.4 (I could now make a choke and say that with these update cycles this is not a problem either ... 😎).
Maybe first something about the history and my reasons for using both:
I have been using Resilio since version 1.4.111 (then BTsync), the previous versions were not yet so stable. I pre-matched the 3 Synology servers at different locations and then set them up there. With Resilio, I manage around 2.11 TB of data in over 50 peers. Resilio has been running well since v2.x.x and currently v2.6.4 is actually reliable, without major errors and is fast. I experimented with Syncthing and developed an ignorelist so that Resilio and Syncthing can work in the same directories:
// Resilio files
.sync
.syncID
.syncIgnore
.syncArchive
* .bts
! sync
* .syncPart
* .syncTemp
* .syncOld// syncthing files
.stfolder
.stignore
.stversion
.syncthing *
.syncthing. *
.syncthing. *. *
~ Syncthing ~ *. *. Tmp
* .IdentifierSyncthing has a better relay handling with external connections than Resilio. If the 5-digit ports cannot be used, e.g. because the ports in the router are closed or cannot be opened as UPnP or because you are in a strict company network where only http and https work, channels at the http and https level are used, i.e. ports 80 and 443 connections. In such an environment, Resilio is unworkable. Then I use syncthing, that is for me the main reason. Other minor advantages are several peers can point to one directory in Syncthing, for example to establish a kind of star connection. This is not possible with Resilio. The "Send + Receive", "Send Only" and "Receive Only" modes are easy to set up. Resilio can do that too, but the peer type has to be changed and set up with each change.
Then there is the performance: One of the servers is on a 2000 (!) Line (yes, that still exists today). Because Resilio is really very performant, this performance needs quite a bit of basic bandwidth. As soon as there are already 5 larger peers, almost nothing works anymore. If the peers are small, so if there are small directories to match, a few more peers go, but the performance problem remains. With Syncthing I have over 40 peers in sync and it still works. The reaction speed to changes is then slower, but this does not bother with this server. These 40 peers go to the same directories on my productive server, which are compared with all other servers and clients with Resilio, thanks to my ignore list no problem.
My experience shows that Resilio has a very strong competitor, but is still a reference. Both packages have bugs and minor problems. I use open words and Resilio should read along well, because more and more people deal with the "other".
writing large files
in Sync Troubleshooting
Posted
Maybe a bug. Maybe ones more as reason to have updates in short cycles. It makes no sense to have a big update in one or two times per year. It is better to have in fixed cycles of a month or so.