Redundant server always stopping and starting

[emovspunk1996]

I have a problem on my redundant server as it is always stopping and starting and after some time passes it is fully stopped. I cant seem to find what causes the problem.

MasterTCPChannel	18Sep2019 17:57:31	(id=60) Shutting down channel.
MasterTCPChannel	18Sep2019 17:57:31	Error occurred while communicating with backup client. Client has likely become unavailable.
MasterTCPChannel	18Sep2019 17:57:29	(id=61) Shutting down channel.
MasterStateManager	18Sep2019 17:57:24	System UID has been updated to '617d83d7-4de6-4314-9383-d4861efb1ae7'
MasterStateManager	18Sep2019 17:57:18	Backup node has requested a 'data-only' restore.
MasterTCPChannel	18Sep2019 17:57:18	System restore initiated by backup node. System will provide a data-only restore file.
MasterStateManager	18Sep2019 17:57:18	Connection registered from '/192.101.180.4:52810'
MasterTCPChannel	18Sep2019 17:57:18	Backup node is out of date - revision is not available on master node, so data-only restore will be performed.
DiskSyncManager		18Sep2019 17:57:15	Size of synchronization tasks on disk has exceeded the allowed maximum. Further tasks will not be stored, and the backup will need to perform a full restore.
MasterTCPChannel	18Sep2019 17:54:59	Channel did not see any activity within the specified failure timeout.
MasterTCPChannel	18Sep2019 17:54:57	Peer node information has been updated: RedundancyNode(address=192.101.180.4, httpAddresses=[http://192.101.180.4:8088/main], sessionCount=0, activityLevel=Warm, projectState=Unknown)
MasterTCPChannel	18Sep2019 17:54:56	Reporting master start time of Wed Sep 18 14:32:54 PST 2019
MasterStateManager	18Sep2019 17:54:55	Connection registered from '/192.101.180.4:52606'
MasterTCPChannel	18Sep2019 17:53:01	(id=58) Shutting down channel.
MasterTCPChannel	18Sep2019 17:53:01	(id=58) Shutting down channel.
MasterTCPChannel	18Sep2019 17:53:01	Error occurred while communicating with backup client. Client has likely become unavailable.
MasterTCPChannel	18Sep2019 17:52:59	(id=59) Shutting down channel.
MasterStateManager	18Sep2019 17:52:54	System UID has been updated to 'bf859600-2173-4c96-a0b8-fb41565b4005'
MasterStateManager	18Sep2019 17:52:48	Backup node has requested a 'data-only' restore.
MasterTCPChannel	18Sep2019 17:52:48	System restore initiated by backup node. System will provide a data-only restore file.
MasterStateManager	18Sep2019 17:52:48	Connection registered from '/192.101.180.4:52426'
MasterTCPChannel	18Sep2019 17:52:48	Backup node is out of date - revision is not available on master node, so data-only restore will be performed.
DiskSyncManager		18Sep2019 17:52:45	Size of synchronization tasks on disk has exceeded the allowed maximum. Further tasks will not be stored, and the backup will need to perform a full restore.

Any help would be greatly appreciated. Thank you

[paul-griffith]

What version of Ignition are you using? Do both systems have the same set of modules installed?

[pturmel]

If you renamed your gateway, this is probably the just-fixed bug 14791:

Nightly Changelogs - 2019

Nightly Changelog: 8.0.5-b20190923 Ignition Platform 14968: Fix a race condition in OPC read-after-write Fixed an OPC read-after-write race condition where it was possible for a read value to be older than a value supplied by subscription. 14955: Prevent the expression property from becoming a binding when overriding in a UDT Fixed an issue where tag expressions could accidentally be turned into a binding by overriding the value in a UDT instance, which caused the original expression to no l…

[emovspunk1996]

I am using 7.9.10 version. Both have same set of modules installed.

[r.lebohec]

Hi @emovspunk1996,
@paul-griffith
I have exactly the same symptoms on my 7.9.13 architecture. Have you solved your problem since? And How?

Regards,

[Julio_Guagnelli]

Hi @emovspunk1996,

Have you solved this problem? I am experiencing the same issue.

Thanks,

Julio