TS ping failure sample
The following example shows a TS ping failure taken from the Switchover
log on the backup server:
|
Time |
Topic |
Message |
|
14:17:55.667
|
ModuleMonitor
|
ModuleByName::Ping() : Ping rejected to the TsServer
module: error count [1] is within maximum [2], ping will be reissued
with regular timeout
|
|
14:18:05.667
|
ModuleMonitor
|
ModuleByName::Ping() : Reached maximum error count
[2] pinging the TsServer module on the main connection, resetting
error count and trying the alternate connection
|
|
14:18:15.667
|
ModuleMonitor
|
Ping rejected to the TsServer module: error count
[1] is within maximum [2], ping will be reissued with regular
timeout
|
|
14:18:25.667
|
ModuleMonitor
|
Ping was rejected to the TsServer module: reached
maximum error count [2], signaling that the module is down
|
|
14:18:25.667
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::process_module_monitor_event
: module monitor indicated the [TsServer] module is not responding,
both connections are up
|
|
14:18:25.667
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::ping_monitored_module
: Sending up to 2 ping(s) to the TsServer module using the main
connection
|
|
14:18:25.671
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::ping_monitored_module
: Did not receive a reply from the TsServer module after 2 ping(s)
on the main connection
|
|
14:18:25.671
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::process_module_monitor_event
: Failed to ping the [TsServer] module, checking connections PrimaryMonitor
|
|
14:18:25.679
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::check_local_gateway_connections
: Successfully pinged local gateway address [172.17.112.1], setting
network connection status to 'GatewayReached'
|
|
14:18:25.679
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::check_net_test_connections
: No NetTest addresses to ping, setting network connection status
to 'NetTestUnavailable'
|
|
14:18:25.679
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::check_primary_address
: Successfully pinged primary address [172.17.112.171], setting
network connection status to 'PrimaryReached'
|
|
14:18:25.679
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::detect_and_signal_connection_status
: module monitor indicated that the [TsServer] module is not responding
(all connections are up), primary connection status is 'monitored
module down', signaling the module is down
|
|
14:18:25.679
|
PrimaryMonitor
|
primarymonitor::CPrimaryMonitor::signal_primary_down
: Primary connection status=[monitored module down], network connection
status=[primary reached]: [TsServer] module is down, posting [event=eTSDown]
|
|
14:18:25.682
|
SwitchoverStates
|
SwitchoverState::StateBackup : Module is down, switching
now and going to StatePrimary
|
Note:
The TS pings are failures. When the pings fail, each failure is followed
by a 1-second sleep. Then a reattempt occurs after each sleep twice on
the Main connection, twice on the Auxiliary connection, and twice again
on the Main connection. After all pings fail, a switchover is attempted
(approximately 30 seconds from the first ping transmission). The 30 seconds
is the timeframe shown in the logging example above.
