sapstartsrv does not respawn after a forceful kill of the master nameserver

This document (7024291) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server for SAP Applications Service Pack 4
SUSE Linux Enterprise Server for SAP Applications Service Pack 3
SUSE Linux Enterprise Server for SAP Applications Service Pack 2
SUSE Linux Enterprise Server for SAP Applications Service Pack 1
SAPHanaSR-ScaleOut
SAPHanaSR-ScaleUp

Situation

While testing the cluster thoroughly, one of the tests to be conducted is to kill the sapstartsrv process to ensure it is being restarted when the next monitor event occurs. While performing the kill on the slave nameservers, the processes are respawned but when killing the master nameserver nothing happens or is written to the logs. The issue is seen in Scale-Out as well as in Scale-Up environments.

Resolution

Program Temporary Fixes (PTFs) are available for Scale-Out and Scale-Up deployments. Please open a service request and let us know which fix is required.

Cause

A problem with the function saphana_check_local_instance() that calls check_sapstartsrv()(responsible for monitoring the running service and restart operations it if not available).

Additional Information

After applying the fix, the following messages can be seen in /var/log/pacemaker.log when killing the master nameservice:

SAPHanaTopology(rsc_SAPHanaTopology_SAW_HDB00)[2922]:   2019/11/22_08:59:13 INFO: RA ==== end action monitor_clone with rc=0 (0.154.0) (5s)====

-> killing sapstartsrv

SAPHanaTopology(rsc_SAPHanaTopology_SAW_HDB00)[3627]:   2019/11/22_08:59:28 INFO: DEC: site=DEL, mode=primary, MAPPING=hana102, hanaRemoteHost=hana102
SAPHanaTopology(rsc_SAPHanaTopology_SAW_HDB00)[3627]:   2019/11/22_08:59:28 INFO: RA ==== begin action monitor_clone (0.154.0) ====
SAPHanaTopology(rsc_SAPHanaTopology_SAW_HDB00)[3627]:   2019/11/22_08:59:29 INFO: RA ==== end action monitor_clone with rc=0 (0.154.0) (6s)====
SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:33 INFO: RA ==== begin action monitor_clone (0.154.0) ====
SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:33 INFO: RA: SRHOOK1=
SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:33 INFO: RA: SRHOOK2=PRIM
SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:33 INFO: RA: SRHOOK3=PRIM

-> SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:35 WARNING: ACT: sapstartsrv is not running for instance SAW-HDB00, it will be started now
SAPHana(rsc_SAPHana_SAW_HDB00)[4238]:   2019/11/22_08:59:37 INFO: ACT: sapstartsrv for instance SAW-HDB00 was restarted!

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7024291
  • Creation Date: 26-Nov-2019
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center