This Knowledgebase article provides a list of Knowledgebase articles that individually address specific unexpected Neverfail Heartbeat behaviors.
Unexpected behaviors are exceptional failure cases when Neverfail does not act as expected. These conditions generally arise because a particular pattern of failures puts Heartbeat into state from which it cannot recover easily, either because the failure mode is unexpected OR because human intervention is required to decide on the correct recovery route.
Unexpected behavior scenarios are generally well documented in the Neverfail Knowledgebase; however, if you encounter an undocumented problem, you should gather the logs and send them to your Support representative, together with a detailed description of the environment and of the problem encountered.
For more information on how to gather Neverfail logs, see Knowledgebase article #146 - 'How to retrieve the Neverfail Heartbeat logs and other useful information for Support purposes'
Neverfail has identified below a list of commonly encountered unexpected Neverfail Heartbeat behaviors. Click on a link below to find out more about a specific unexpected Neverfail Heartbeat behavior including how to troubleshoot it.
Two Active or Two Passive Servers
Knowledgebase article #516 - 'Resolve Two Active Servers'
Knowledgebase article #984 - 'Resolve Two Passive Servers'
Neverfail License Becomes Invalid
Knowledgebase article #985 - 'Resolve an Invalid Neverfail License'
Neverfail Can't Sync
Knowledgebase article #991 - 'Neverfail Synchronization Failures'
Knowledgebase article #992 - 'Neverfail Channel Drops'
Knowledgebase article #993 - 'MaxDiskUsage Errors'
Knowledgebase article #994 - 'Application Slowdown'