Guest

Preview Tool

Cisco Bug: CSCus75059 - HA heartbeat timeout due to NodeHeartbeatThread on both admin VMs

Last Modified

Sep 18, 2015

Products (1)

  • Cisco WebEx Meetings Server

Known Affected Releases

2.5.1.29

Description (partial)

Symptom:
Per logs n primary admin:
[ NodeHeartbeatThread] 2015-01-09 16:24:29,573 [NodeHeartbeatThread-setStatus 284] <DEBUG>   NodeHeartbeatThread setStatus() - Sent a heartbeat request to host HAIRPhostname

[ NodeHeartbeatThread] 2015-01-09 16:24:44,589 [NodeHeartbeatThread-setStatus 348] <DEBUG> NodeHeartbeatThread Got SocketTimeoutException while reading Node status for hostname HAIRPhostname Read timed out

[ SystemMonitorThread] 2015-01-09 16:24:48,301 [SystemMonitorThread-setStatus 340] <DEBUG> setStatus() Did not receive heartbeat from node HAIRPhostname node status = false 
[ SystemMonitorThread] 2015-01-09 16:24:48,301 [SystemMonitorThread-setStatus 362] <ERROR> SystemMonitorThread setStatus() Publishing Node DOWN for host=HAIRPhostname
 
On secondary admin:
[ NodeHeartbeatThread] 2015-01-09 16:24:36,275 [NodeHeartbeatThread-setStatus 284] <DEBUG>   NodeHeartbeatThread setStatus() - Sent a heartbeat request to host HAIRPhostname
[ NodeHeartbeatThread] 2015-01-09 16:24:36,277 [NodeHeartbeatThread-setStatus 342] <DEBUG>   NodeHeartbeatThread getResourceStatus for HAIRPhostname NodeStatus:: true ResourceStatus::true

IRP does not respond to primary admin in timely fashion and is marked down, but at that time was able to respond to the secondary admin and is reachable on the network.

NodeHeartbeatThread should only be active on the primary admin, and invalid state of HA on the secondary admin can lead to VMs responding improperly and being marked down.

Conditions:
Deployment with HA servers
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.