# Gateway Redundancy Providers System Events (Remote needs to do full pull)

**URL:** <https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959>\
**Category:** Ignition\
**Tags:** redundancy\
**Created:** [December 11, 2023, 7:26am UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959 "2023-12-11T07:26:38Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![vincent.devillers](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vincent.devillers](https://forum.inductiveautomation.com/u/vincent.devillers)\
**Post date:** [December 11, 2023, 7:26am UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/1 "2023-12-11T07:26:39Z")

</div>

We have noticed on the Redundancy page, repeatedly the events :

- [_alarm\_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.

In the logger info we have also repeatedly warnings :

- Partial sync operation failed: result was 'Bad\_OutOfRange("Remote version has different UUID, or remote revision is too far behind")'. Full sync will be needed.
- Partial sync operation failed: result was 'Bad\_OutOfRange("Full pull already in progress")'. Full sync will be needed.  
The redundancy properties are stating 'Activity Level' : Active and 'Synchronisation Status : ' : Good

Are these logging something to be worried about?  
Do we have to perform a 'Force Re-Sync'?

**Information about the redundancy :**

![afbeelding](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/af9a2844b3db1431927039626c5f2de1538c8f4c.png)

 ![afbeelding](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/4/a4310835eca639d985ad3a9054ce3e9871fe02aa.png)

The Dispatched Updates/sec seems to be high, somtimes a warning is shown  
 ![afbeelding](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/5/a59cd8fdf1cc6a940bb606f1f1c6361e960ad840.png)

**Information about the system :**

- Ignition : 8.1.29
- Tags : 744332  
 ![afbeelding](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/5/75ca6c1c13c94cb1b041a4039ac8981b0cdf8f2c.png)

![afbeelding](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/4/b44a6fdeca98b1246f636f7e7bdf8998bc63d1c6.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 11, 2023, 1:06pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/2 "2023-12-11T13:06:44Z")

</div>

Was there any point in time where you might have upgraded a module on the master while the backup wasn't synchronized? Having mismatched modules prevents synchronization. (Been there. Symptoms like yours.) Module installs while synchronized are propagated from master to backup.

---

<div class="post-metadata">

**Author:** ![vincent.devillers](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vincent.devillers](https://forum.inductiveautomation.com/u/vincent.devillers)\
**Post date:** [December 12, 2023, 6:20am UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/3 "2023-12-12T06:20:25Z")

</div>

No, the last time we dit a full update to 8.1.29 on both master and backup.  
I've also performed a "Force Re-Sync" but it quickly again shows " [_alarm\_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data."

I'm wondering if we have to much Dispached Updates / sec (at this moment 3,250.4)  
Qued Updates is at 4,166.5  
and Pending Updates sometimes low, sometimes \> 8,000

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 12, 2023, 1:17pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/4 "2023-12-12T13:17:12Z")

</div>

That update queue sounds suspicious. Are your gateways not on the same LAN? (Putting a WAN between a master and backup is not supported, because the bandwidth and low latency requirements become a problem for anything but trivial setups.)

---

<div class="post-metadata">

**Author:** ![djgilson](https://avatars.discourse-cdn.com/v4/letter/d/f14d63/32.png) [@djgilson](https://forum.inductiveautomation.com/u/djgilson)\
**Post date:** [December 12, 2023, 7:27pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/5 "2023-12-12T19:27:38Z")

</div>

We are having the same issue with 3 systems with redundancy. I have been working with IA, but no answers yet. We are running version 8.1.32. We are not sure when this started. 2 of the systems have been running without the message for over a year. We noticed it on the system we added redundancy to a few weeks ago. Then we noticed the other 2 systems had the same message.  
Hope to have an answer soon.

---

<div class="post-metadata">

**Author:** ![vincent.devillers](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vincent.devillers](https://forum.inductiveautomation.com/u/vincent.devillers)\
**Post date:** [December 15, 2023, 8:09am UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/6 "2023-12-15T08:09:03Z")

</div>

Those are two virtual machines from one of out customer. I will have to askt them if they are on the same lan

---

<div class="post-metadata">

**Author:** ![David\_Lopez](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@David\_Lopez](https://forum.inductiveautomation.com/u/David_Lopez)\
**Post date:** [February 28, 2024, 9:42pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/7 "2024-02-28T21:42:08Z")

</div>

Hello everyone, do you have any updates?.

I'm having the same issue on Ignition 1.8.35 (the master is hosted on the cloud and the redundancy is on premisse). Also, I believe that this is related with other alarm times issues.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 28, 2024, 9:53pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/8 "2024-02-28T21:53:50Z")

</div>

> [@David\_Lopez](#):
>
> the master is hosted on the cloud and the redundancy is on premisse

That is simply unsupportable. Don't do that.

---

<div class="post-metadata">

**Author:** ![David\_Lopez](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@David\_Lopez](https://forum.inductiveautomation.com/u/David_Lopez)\
**Post date:** [February 28, 2024, 10:17pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/9 "2024-02-28T22:17:07Z")

</div>

Thank you for your fast response, I will work on that.  
Do you know if there is any document that details why this is not recommended?, I would like to understand more about that, would you mind to explain to me a little bit more please. Since, it's an important change I need to support it before perform this change.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 28, 2024, 10:57pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/10 "2024-02-28T22:57:29Z")

</div>

See this recent topic:

> [@Architecture for Distributed Control Center](https://forum.inductiveautomation.com/t/architecture-for-distributed-control-center/85104/9):
>
> Ignition redundancy is both latency sensitive and subject to split brain syndrome. If the comms goes down between sites, both servers will end up active and therefore numerous properties start to diverge. So let me amend my answer to: Ignition redundant servers must be installed on a common LAN with a robust network layout (preferably multi-path, like RTSP), such that any loss of comms also results in loss of comms to all clients and all devices and all databases. (Trunk port for multiple VL…

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 28, 2024, 10:58pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/11 "2024-02-28T22:58:29Z")

</div>

More topics:

[https://forum.inductiveautomation.com/search?q=split%20brain%20%40pturmel%20order%3Alatest](https://forum.inductiveautomation.com/search?q=split%20brain%20%40pturmel%20order%3Alatest)

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [February 4, 2026, 10:01pm UTC](https://forum.inductiveautomation.com/t/gateway-redundancy-providers-system-events-remote-needs-to-do-full-pull/82959/13 "2026-02-04T22:01:07Z")

</div>

did you find the cause of those messages ?
