Select to view content in your preferred language

Servers Randomly Synchronize with the Server Site, Causing Partial Outage

4142
10
01-30-2024 01:17 PM
RyanUthoff
MVP Regular Contributor

I'm having an issue with one my ArcGIS Enterprise 11.1 deployments where the two machine, active-active server site randomly re-synchronizes with the site which causes a partial outage.

Specifically, I get these error messages in the logs:

The server machine 'machine name' is synchronizing with the site. This will take a few minutes and during this operation all administrative operations will be blocked.

Resetting the synchronization flag on the machine 'machine name'. Resetting the synchronize flag as synchronization is now running.

Failed to update the security configuration. Exception Could not connect to the ArcGIS component at URL 'https://machinename:6443/arcgis/admin/local/manageHandler'. The ArcGIS component on that machine may not be running or the machine may not be reachable at this time.Error: Connection refused: connect

There were a couple other variations of that same error message from above. But after a few minutes, it finishes and everything goes back to normal. And while it doesn't happen at the same time, this has happened on both machines. So, it's not isolated to one machine.

Is there any reason why this is randomly happening? There are no other errors in the server logs. No errors in Windows event viewer, and the ArcGIS Server service doesn't get restarted or anything. Technically, we don't experience an outage because the other ArcGIS Server site handles the load until the other server site comes back online. But, it's also not ideal for one of our servers to essentially be inoperable for 20+ minutes while this is happening. 

10 Replies
JGillespie_Maps
New Contributor

Did you ever figure out what your issue was @Yogesh_Chavan 

We are experiencing the same mysterious random synchronizations, but in our case this was occurring and causing the arcsoc processes to fail even before the site had multiple machines. We added a second machine to the site in order to help stabilize the environment and are seeing the exact same log messages that you describe (they also existed when only one machine was in the site so I've no idea what it was "syncing" with). We are own our third open ticket with ESRI for this issue and so far we haven't be able to identify a root cause. Similarly, we can't force this issue to occur.

0 Kudos