Redundant gateway,
we have periodically this message "[alarm_system] Will perform full pull. Reason: redundant provider on local side has no data." and lots of device are disconnected.
Whats does it means ?
|04Feb2026 21:45:29|[_alarm_system_] Will perform full pull. Reason: redundant provider on local side has no data.|
|---|---|
|04Feb2026 20:00:13|[_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.|
|04Feb2026 19:38:58|Redundancy state changed: Role=Master, Activity level=Active, Project state=Good, History level=Full|
|04Feb2026 19:38:58|[internaldb] Remote needs to do full pull. Reason: major change detected between nodes (sync provider UUIDs did not match), this node is the redundant master, and this redundant provider does not use bidirectional sync.|
|04Feb2026 19:38:57|System restore initiated for backup node. A data-only restore file will be provided. The backup node will then restart.|
|04Feb2026 19:38:57|Redundancy state changed: Role=Master, Activity level=Active, Project state=OutOfDate, History level=Full|
|04Feb2026 19:38:35|Redundancy state changed: Role=Master, Activity level=Active, Project state=Good, History level=Full|
Based on what is in those log entries, the redundant master gateway may have restarted. The 21:45:29 message means that the alarm redundant provider on the master gateway is in a “just started” state. That’s what “redundant provider on local side has no data” means in the message. The backup gateway has recent alarm data that the master needs to pull over so that it can be brought up to date. That is all I can tell you about that log snippet though.
That s strange, both nodes was up and running
I will check if something cause this unexpected restart of the master active node...
on the backup side:
System Events
Severity Time Event
04Feb2026 21:45:26 [_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.
04Feb2026 21:45:25 [_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.
04Feb2026 21:45:23 [_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.
04Feb2026 21:45:22 [_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.
04Feb2026 21:45:21 [_alarm_system_] Remote needs to do full pull. Reason: redundant provider on remote side has no data.
04Feb2026 21:45:21 [tagprovider-ligneA] Changes detected on both sides! Will need to perform full pull from master. This will clear all pending changes for this sync provider on this node.
04Feb2026 21:45:19 [_alarm_system_] Will perform full pull. Reason: redundant provider on local side has no data.
04Feb2026 21:08:19 [tagprovider-ligneA] Changes detected on both sides! Will need to perform full pull from master. This will clear all pending changes for this sync provider on this node.
04Feb2026 20:00:14 [_alarm_system_] Will perform full pull. Reason: redundant provider on local side has no data.
04Feb2026 19:42:11 Redundancy state changed: Role=Backup, Activity level=Cold, Project state=Good, History level=Full
04Feb2026 19:41:49 Redundancy state changed: Role=Backup, Activity level=Cold, Project state=OutOfDate, History level=Full
04Feb2026 19:41:49 [client_auth_token_runtime_provider] Will perform full pull. Reason: major change detected between nodes (sync provider UUIDs did not match).
04Feb2026 19:41:49 [_alarm_system_] Will perform full pull. Reason: major change detected between nodes (sync provider UUIDs did not match).
04Feb2026 19:41:49 [_alarmshelf_] Will perform full pull. Reason: major change detected between nodes (sync provider UUIDs did not match).
04Feb2026 19:41:49 [tagprovider-ligneD] Will perform full pull. Reason: major change detected between nodes (sync provider UUIDs did not match).