This article covers loggers related to Redundancy that were introduced in Ignition version 7.8.X.
Loggers in this article:
Redundancy.StateMonitoring
A series of loggers monitoring creation, communication, and disconnect for Redundancy on either the Master or Backup server.
StateMonitoring.Channels.MasterTCPChannel
- Provides information about initialization and closing of the connection from the master node, as well as the synchronization of the two nodes.
- INFO log that shows both the initialization and later, the closing of the connection for a redundant pair:
Redundancy master state monitoring server started on port 8750
(id=4) Connected to address '/10.10.65.60'
Starting redundancy channel id 4
Reporting master start time of Wed Dec 31 16:00:00 PST 1969
Peer node information has been updated: RedundancyNode(address=10.10.65.60, httpAddresses=[http://10.10.65.60:8088/main], sessionCount=0, activityLevel=Active, projectState=Good)
Received a full runtime state update from the other redundant node.
Peer node information has been updated: RedundancyNode(address=10.10.65.60, httpAddresses=[http://10.10.65.60:8088/main], sessionCount=0, activityLevel=Cold, projectState=Good)
...
(id=4) Shutting down channel.
Refreshing redundant state (forced=false). Current state: [RedundancyState[role=Independent, activity level=Active, project state=Good, history level=Full]
The redundant node state has changed. Current state: [RedundancyState[role=Independent, activity level=Active, project state=Good, history level=Full]
- INFO log that shows both the initialization and later, the closing of the connection for a redundant pair:
-
- DEBUG log that shows additional detail for both the initialization and later, the closing of the connection for a redundant pair. In this example, the master node was set back to Independent to close the socket connection:
Backup node's activity level is 'Active', and the master is currently active or the recovery mode is set to 'Automatic'. Sending a request for backup to become non-active.
Comparing module manifests:
[(com.inductiveautomation.alarm-notification/3.8.5 (b2016120813)), (com.inductiveautomation.eam/1.8.5 (b2016120821)), (com.inductiveautomation.phone-notification/3.8.5 (b2016120813)), (com.inductiveautomation.sfc/2.8.5 (b2016120821)), (com.inductiveautomation.sms-notification/3.8.5 (b2016120813)), (com.inductiveautomation.taghistorian/1.8.5 (b2016120813)), (dnp3-driver/1.8.5 (b2016120813)), (fpmi/8.8.5 (b2016120821)), (fsql/7.8.5 (b2016120813)), (help/3.8.5 (b2016120813)), (ia.voice.en_us_katherine/3.8.2 (b0)), (logix-v21/2.8.5 (b2016120813)), (mobile/3.8.5 (b2016120821)), (modbus-driver2/4.8.5 (b2016120821)), (omron-driver/1.8.5 (b2016120813)), (opccom/3.8.5 (b2016120821)), (rept/3.8.5 (b2016120813)), (siemens-drivers/3.8.5 (b2016120813)),
(symfact/4.8.5 (b2016120821)), (udp-driver/3.8.5 (b2016120813)), (xopc/3.8.5 (b2016120821)), (xopc-drivers/3.8.5 (b2016120813))]
[(com.inductiveautomation.alarm-notification/3.8.5 (b2016120813)), (com.inductiveautomation.eam/1.8.5 (b2016120821)), (com.inductiveautomation.phone-notification/3.8.5 (b2016120813)), (com.inductiveautomation.sfc/2.8.5 (b2016120821)), (com.inductiveautomation.sms-notification/3.8.5 (b2016120813)), (com.inductiveautomation.taghistorian/1.8.5 (b2016120813)), (dnp3-driver/1.8.5 (b2016120813)), (fpmi/8.8.5 (b2016120821)), (fsql/7.8.5 (b2016120813)), (help/3.8.5 (b2016120813)), (ia.voice.en_us_katherine/3.8.2 (b0)), (logix-v21/2.8.5 (b2016120813)), (mobile/3.8.5 (b2016120821)), (modbus-driver2/4.8.5 (b2016120821)), (omron-driver/1.8.5 (b2016120813)), (opccom/3.8.5 (b2016120821)), (rept/3.8.5 (b2016120813)), (siemens-drivers/3.8.5 (b2016120813)), (symfact/4.8.5 (b2016120821)), (udp-driver/3.8.5 (b2016120813)), (xopc/3.8.5 (b2016120821)), (xopc-drivers/3.8.5 (b2016120813))]
(id=4) Channel state set to 'CONNECTED'
Backup node's activity level is 'Active', and the master is currently active or the recovery mode is set to 'Automatic'. Sending a request for backup to become non-active.
...
(id=4) Channel state set to 'DISCONNECTED'
Exception received while shutting down the server channel. This is likely a normal error expected after closing the socket.
Socket Closed
- DEBUG log that shows additional detail for both the initialization and later, the closing of the connection for a redundant pair. In this example, the master node was set back to Independent to close the socket connection:
-
- TRACE log showing comparison between the two redundant nodes to ensure synchronization. These logs will be reported every few seconds or so:
Runtime state is up-to-date.
Performing full backup node version check. Backup node version: [94124ae2-ebb6-4837-bf3e-07966a74ef54/0] Our version: [94124ae2-ebb6-4837-bf3e-07966a74ef54/0]
Backup node version is OK.
- TRACE log showing comparison between the two redundant nodes to ensure synchronization. These logs will be reported every few seconds or so:
StateMonitoring.Channels.BackupTCPChannel
- Provides information about initialization and closing of the connection from the backup node, as well as the synchronization of the two nodes.
- INFO log that shows both the initialization and later, the closing of the connection for a redundant pair:
Starting redundancy channel id 1
(id=1) Connected to address '/10.10.60.75'
…
Master start time was reported to be 'Thu Oct 14 09:37:14 PDT 2021' (adjusted to backup clock)
Peer node information has been updated: RedundancyNode(address=null, httpAddresses=null, sessionCount=0, activityLevel=Active, projectState=null)
Peer node information has been updated: RedundancyNode(address=169.254.56.163, httpAddresses=[http://169.254.56.163:8088/main], sessionCount=0, activityLevel=Active, projectState=Good)
Project version synchronized, backup node is up-to-date.
Peer node information has been updated: RedundancyNode(address=169.254.56.163, httpAddresses=[http://169.254.56.163:8088/main], sessionCount=0, activityLevel=Active, projectState=null)
- INFO log that shows both the initialization and later, the closing of the connection for a redundant pair:
-
- DEBUG log that shows additional detail for both the initialization and later, the closing of the connection for a redundant pair. In this example, the backup node was set back to Independent to close the socket connection:
Attempting to connect to '/10.10.60.75':8750
…
(id=1) Channel state set to 'CONNECTED'
…
Channel thread was interrupted, system likely shutting down or redundancy stopped.
- DEBUG log that shows additional detail for both the initialization and later, the closing of the connection for a redundant pair. In this example, the backup node was set back to Independent to close the socket connection:
-
- TRACE log showing periodic checks to ensure synchronization. These logs will be reported every second:
Runtime state is up-to-date.
Last execution cycle took 32 ms. Will sleep for 968 ms.
Last execution cycle took 30 ms. Will sleep for 970 ms.
- TRACE log showing periodic checks to ensure synchronization. These logs will be reported every second:
StateMonitoring.MasterStateManager
- Provides information about the initialization, active connection, and closing of the connection from the master node.
- INFO logger stating a successful connection then later closed:
Successfully registered new connection to redundant master from '/10.10.65.60:63287'
Refreshing redundant state (forced=false). Current state: [RedundancyState[role=Master, activity level=Active, project state=Good, history level=Full]
Join-wait time has expired, will refresh system state.
Redundancy master state monitoring server stopped.
- INFO logger stating a successful connection then later closed:
-
- DEBUG log providing details about the connection’s channel id:
Registered channel id '5'
Monitoring channel detected.
...
Unregistering closed channel '5'
- DEBUG log providing details about the connection’s channel id:
-
- TRACE log providing the current state of the Master node. These logs will be reported every few seconds or so:
Refreshing redundant state (forced=false). Current state: [RedundancyState[role=Master, activity level=Active, project state=Good, history level=Full]
- TRACE log providing the current state of the Master node. These logs will be reported every few seconds or so:
StateMonitoring.BackupStateManager
- Provides information about the initialization and active connection of the connection from the backup node.
- INFO logger stating a successful connection:
The redundant node state has changed. Current state: [RedundancyState[role=Backup, activity level=Cold, project state=Good, history level=Full]
Join-wait time has expired, will refresh system state.
- INFO logger stating a successful connection:
-
- DEBUG log providing additional details about the connection’s state:
Calculating activity. Existing level: Cold, Channel state: CONNECTED, negotiated level: Cold, project state: Good, join-wait expired: false
- DEBUG log providing additional details about the connection’s state:
-
- TRACE log providing the current state of the Backup node. These logs will be reported every few seconds or so:
Refreshing redundant state (forced=false). Current state: [RedundancyState[role=Backup, activity level=Cold, project state=Good, history level=Full]
- TRACE log providing the current state of the Backup node. These logs will be reported every few seconds or so:
Comments
0 comments
Article is closed for comments.