uSync Complete fails thinking its in a load balanced environment

Questions
,
1

Hi I am using uSync (v13.2.5) + Exporter (v13.1.8), Snapshots (v13.1.8), PeopleEdition (v13.1.8), Publisher (v13.1.8), Complete (v13.1.8).

When we try to push a change to our staging site or live site we get the error:

Error while processing Push - (export/Prepare/0/) [InternalServerError] Folder : [our-guid\uSync] does not exist when it should and the server is running in an load balanced environment.

We do not have a load balanced environment. To attempt to solve this issue we have tried to:

  • Delete uSync on both environments and start again
  • Delete all temp folders (this got us closest but failed at next stage with same error)
  • Setting up a new environment
  • Updating to use Complete v 13.1.10
  • Manually deleting all usync tables from db and starting from scratch.

We have worked with uSync for years and have not came across this before. Does anyone have anything we can try to figure out what the issue is here. Any help will be much appreciated!

3

Hi,

For the load balancing message uSync is just checking to see what role the Umbraco server thinks it is, and if its not a ā€˜Singleā€™ server then we report its in some form of load balancing.

this isnā€™t a show stopper (if you for example have a backoffice server you access with a dedicated url) but it is often the cause of the folder being missing so thatā€™s why itā€™s reported.

if you donā€™t think you are running in a load balanced environment, but umbraco thinks it is a couple of things could be true.

  1. A local dev install is connected to the same database: when you do this, Umbraco treats that other server as part of the load balanced set, (and sends it and the sever notifications when things change etc).
  2. Azure or something has scaled up (auto scale might be on?) so you are infact load balanced you just havenā€™t been told.
  3. A slot swap on deploment might have triggered it while the live and new slot where both active. (this is usually short lived and not really something that gets picked up much).

if its failing at diffrent poiints in the process that that does sort of imply that mid the export the folders undeath are changing (and might happen under a load balance).

It can sometimes fail if there is actually nothing to export (so it thinks its exported but it actually generated nothing). this is rare, and usually only happens if a load of the Sync handlers have been disabled (so there really is nothing to export).

I would have a look and see does the temp folder (usync/receive) on the server actuall contain a folder with the guid above - the failure, is when this folder gets looked for itā€™s missing