laurin1
-
Posts
97 -
Joined
-
Last visited
Posts posted by laurin1
-
-
I've never had an issue with this, but I did "Reset this PC" on one of my machines today and now it fails with this:
Devices not linked
Please checked that both devices are online
BTW, this machine runs Sync as service. Also, the machine now shows up on other machines but is Disconnected. The machine in question always goes through the process of trying to download certificate and folder data, then fails.
-
2 hours ago, Andy+ said:
(all files in the SynUserxxxxxxxxxx directory that end with *.db and *.db-wal)
I don't have any of these files in .SyncUser1503178328 directory. All of those are in the parent directory of .SyncUser1503178328.
However, I removed the folder with the error and added it back and the error has not returned (knock on wood), which never fixed the issue in 2.7.1.
2 hours ago, Andy+ said:If the Pro version is in use and identities are used, it might also be helpful to recreate the master identity, since orphaned or duplicate identities sometimes accumulate there, which can cause disruptions. Unfortunately, these identities can only be hidden via the GUI, but not deleted, which is very bad.
I'm tempted to do this at some point, as I've had this identity in place now for a very long time. However, I'm a little wary since my license (I have a Business License) is tied to the identity, is it not?
-
I just installed 2.7.2, due to having a problem with the application crashing constantly (2.7.0), both the desktop and service version, on 5 different machines:
QuoteWithin the last few weeks (not sure exactly went this started, Sync started crashing on 4 of them, the 2 installed as a service and 2 others. The machine that I use most frequently is not installed as a service and has not crashed. One of the ones that is not a service, but is crashing only crashes on first login for the day (and I login to it every day). The other non-service machine will crash repeatedly - I'll RDP into the machine and see about 50 instances of the icon in the taskbar and the window about the app has crashed with options to relaunch, submit dump, or exit. The service ones concern me the most as these could offline for some time and I would not know it. I'm attaching one of the DMP files and associated logs from a crash that occured on 10/13/20 at 7:54PM.
Support replied:
QuotePlease upgrade all your peers to the current 2.7.2 Sync version -- some important fixes have been made since v.2.7. If the problem persists after upgrade, collect fresh dumps and logs from the affected peers.
However, as I told them:
QuoteI will try 2.7.2, but we updated to 2.7.1 and incurred such problems, we had to downgrade back to 2.7.0:
• On 6/28/20 I experienced this:
• https://help.resilio.com/hc/en-us/articles/204753659
•2.7.1 is unusable for us. If 2.7.2 has the same issues, we won’t be able to use it either.
So I tried 2.7.2 and already getting "Database Error":
-
Oh, that and downgraded to 2.7.0 - I believe there is a bug in 2.7.1 that caused this in the first place, because prior to that change, this all worked fine for years.
-
Well, what I did was removed the folder from Sync and removed the .sync from all machines, then added them all back and now it's working fine (no permission changes needed).
-
Yea, I know, I saw that. There is nothing wrong with the file system, that is a problem with Sync. None of the machines are out of space. This has happened before (on many occasions). Right now, everything is synced, but what you pointed out is a bug in the Sync software.
I have tried doing smaller folders, but the problem is there are so many of them, that it takes me FOREVER to configure a new machine (or a rebuild), which I do all too frequently).
-
I've had numerous issues with 2.7.1, including this one:
The only solution I found was downgrading to 2.7.0.
My problems started with a database error. I removed and added back the folder in question, but never would finish on all machines.
-
FYI, I've tried restarting both machines, and this is a new machine I just added (well, I removed as a peer, deleted all the files, and resynced).
-
Why, at times, does it just stop transferring files? KDAVISTEST has been stuck here for 45 minutes:
From KDAVIS:
-
Installing using the UI works fine for me. FYI, I install using credentials (because I have to), then change it to Local System, so I don't have to worry about password changes. Works just fine!
-
On 2 machines, the network service install (upgrade from 2.6.3) just exits, no error, no nothing.
-
Nice write up.
-
Wonderful.
-
On 8/17/2019 at 6:37 AM, jacw said:
I've sent in two support requests over the past two months related to Sync not functioning on my Synology NAS's anymore. On one I treid a new install. It still won't open the web interface and allow me to reconnect the device to my devices. But anyway, there has been no reply whatsoever.
-
I'm not sure of the cause, but I've had this happen now twice in the last few weeks. Both times, it was one of my devices that runs Sync as a service. Restarting the service on that machine cause this to just "magically go away".
-
Oh, yea, forgot that was even a link. Well, now the issue is gone.
-
A folder has been stuck on at 90% for some time. I restarted the client but still stuck. Any way to "unstick" it?
-
I agree, but that is what support told me I had to do .
-
I’ve already starting deploying to machines!
Seriously, if you are going to pull a version, you should post a notice of why!
Do I need to go back and downgrade my machines or what???
-
Can someone please kick this user!?!
https://forum.resilio.com/profile/63826-ysossuff/
For those of us that follow the whole forum, we are getting hammered.
-
FYI, the Change Log has not been updated: https://help.resilio.com/hc/en-us/articles/206216855-Sync-2-x-change-log
-
Actually, the first attempt, on my first machine, when I clicked Install Now, did something and then the disappeared, but did not update. I clicked "Check now" and that time it worked.
-
I've worked in I.T. a long time and I flat out disagree with that publication. If the authentication process doesn't enforce rules like that, users will definitely create passwords like "123456789" or "aaaaaaaa" (on systems that allow such, I've seen it happen) which are much easier to brute-force hack (or even guess). For that matter, that document conflicts with itself:
QuoteVerifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets.
But above that the document states:
QuoteWhen processing requests to establish and change memorized secrets, verifiers SHALL compare the prospective secrets against a list that contains values known to be commonly-used, expected, or compromised. For example, the list MAY include, but is not limited to:
- Passwords obtained from previous breach corpuses.
- Dictionary words.
- Repetitive or sequential characters (e.g. ‘aaaaaa’, ‘1234abcd’).
- Context-specific words, such as the name of the service, the username, and derivatives thereof.
The rationale is given here:
QuoteQ13: Are password composition rules no longer recommended?
A13: SP 800-63B Section 5.1.1.2 paragraph 9 recommends against the use of composition rules (e.g., requiring lower-case, upper-case, digits, and/or special characters) for memorized secrets. These rules provide less benefit than might be expected because users tend to use predictable methods for satisfying these requirements when imposed (e.g., appending a ! to a memorized secret when required to use a special character). The frustration they often face may also cause them to focus on minimally satisfying the requirements rather than devising a memorable but complex secret. Instead, a blacklist of common passwords prevents subscribers from choosing very common values that would be particularly vulnerable, especially to an online attack.
Composition rules also inadvertently encourage people to use the same password across multiple systems since they often result in passwords that are difficult for people to memorize.
I agree with their reasoning, but don't believe removing those rules accomplishes the goal indicated. Especially that last line - even for myself, the only thing that finally broke me of that (because I have to 100's of passwords) is using a password manager. Seems that pushing PM's and / or 2FA is much better advice than removing those rules as recommendation.
-
What limit are you referring to? The enforcement of numbers and punctuation marks?
Latest desktop build 2.7.2
in Sync General Discussion
Posted
Yea, I'm done with this product. I've spent the last week switching everything over to Syncthing and will not be renewing my license for Sync this year.