SAP Knowledge Base Article - Preview

3765584 - Possible causes of rc 15 connection broken warnings, cluster alert report

Symptom

You observed cluster alerts report:

Node is XXXXX title is DB replication disruption on XXXXX for hana_hts_sync_state resource in pacemaker cluster

Upon checking trace files, you found:

  1. nameserver trace warnings like `w TrexNet Channel.cpp(00507) ...... reading failed with rc=15 (connection broken)`.
  2. nameserver trace errors like `e clock_monitor    ClockMonitor.cpp(00073) : info: high cpu load, this job should run each 1000 msec, but it took XXXX msec.`
  3. var/log/messages shows `HANA_CALL timed out after 5 seconds running command 'python systemReplicationStatus.py --site=XXXX'`.


Read more...

Environment

  • SAP HANA 1.0, platform edition
  • SAP HANA 2.0, platform edition

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

rc=15, connection broken, hana_call timeout, systemReplicationStatus.py, pacemaker, hana_hts_sync_state, replication disruption, nameserver clock_monitor, high cpu load, TrexNet read failed, transparent huge pages , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.