Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(URGENT) Problem with sync after update to uSync.Complete v13.1.9 #257

Open
afabri73 opened this issue Feb 3, 2025 · 1 comment
Open

Comments

@afabri73
Copy link

afabri73 commented Feb 3, 2025

Hi,
I have three website (Umbraco v13.5.3 with uSync.Complete v13.1.9) configured as follow:
- STAGE => single standalone VM
- PROD-ADMIN => single standalone VM (no Load Balancing)
- PROD-FRONTEND => n.3 Load Balanced VM

PROD Environment is configured with DFSR to sync some folders on Admin VM FileSytem (css, scripts, media and views) to the 3 frontends

Everything worked fine until last Friday.
On Saturday, I updated in all environments (STAGE,PROD-ADMIN,and all PROD-FRONTENDS) Umbraco from v13.5.2 to v13.5.3 and uSync.Complete from v13.1.8 to v13.1.9
From that moment the sync between the environments (STAGE/PROD-ADMIN) no longer works and every time I try to perform a PULL or a PUSH I always receive the following error:
Error while processing Pull - (pullFetch/Files/0/) [InternalServerError] Access to the path 'C:\inetpub\wwwroot_intranet\Views\DfsrPrivate' is denied.

Even in the PROD-ADMIN umbraco logs I see errors like the following:
Not authorized to get directories for '"C:\inetpub\wwwroot_intranet\wwwroot\scripts\DfsrPrivate" ad Not authorized to get directories for '"C:\inetpub\wwwroot_intranet\wwwroot\css\DfsrPrivate"

Another thing I noticed is that the error is given only if I try to PULL or PUSH DataTypes, DocumentTypes and Content.
But if I try to PULL or PUSH Templates, Partial Views or Media, the sync complete correctly.

What I don't understand is why the problem appeared only after updating Umbraco and uSync.Complete.
The DFSR has been configured two weeks ago and I have never encountered any errors before, during sync

How can I solve it?
Is it possible to configure uSync.Complete to exclude from check the folders that generate error?
(wwwroot\scripts\DfsrPrivate, wwwroot\css\DfsrPrivate and Views\DfsrPrivate)

Thank you for the support
Adriano

@KevinJump
Copy link
Member

Hi,

I've checked over the changes between v13.1.8 and v13.1.9 (and the usync changes between v13.2.5 and v13.2.6 which are wrapped up in them). there are no changes to file access to reading of folders (they are config, and one about when media files get renamed but that code only gets hit when media does get renamed and during a media sync).

my scarred past with DFS replication (it's like properly 25 years ago now, I try to forget) the DFS private files can lock and it can cause some issues especially when you try to access them, but ideally the DFSPrivate folders would be outside of the replicated folders, but really i am trying to forget this episode (lots of late night pizza 😟 )

However, In uSync you should be able to stop the scan of files in a couple of ways.

1. (the non-config way).

ensure that the "Files" config is not selected for any of the servers (or default settings on the main dashboard)

Image

you can also check in the 'advanced' section of each server to see that "include files" isn't ticked.

Image

this should stop the folder scan from happening on the push/pulls.

2. The config file - remove the folders from the list way.

the folders that are scanned are set in the 'additionalFolders' setting in the appsettings.json files (https://docs.jumoo.co.uk/usync/complete/guides/syncPublisher/publishConfig/config#appsettingsjson-config-file).

e.g

"uSync": {
  "Publisher": {
    "Settings": {
      "IncomingEnabled": true,
      "AppId": "****************",
      "AppKey": "****************",
      "AdditionalFolders": ""
    }
  }
}

the default for additional folders is "~/Views", "~/wwwroot/css", "~/wwwroot/scripts" but given you have dfs setup then guessing you don't need any of these ?

Kevin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants