SAP HANA scale-out - pacemaker.service: "Cannot find sapstartsrv and sapcontrol executable, please set DIR_EXECUTABLE parameter!"

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


SUSE Linux Enterprise Server for SAP 15


An SUSE HA cluster for SAP HANA scale-out and the HANA database have been set up. SAP hostagent and HANA database are configured for native systemd integration. Cluster and HANA are seeming to be functional. Nevertheless, on the majority maker node the pacemaker service shows an error on missing sapstartsrv and sapcontrol executables.
hana00:~ # systemctl status pacemaker

* pacemaker.service - pacemaker needs SAP instance service
     Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; disabled; vendor preset: disabled)
    Drop-In: /etc/systemd/system/pacemaker.service.d/00-pacemaker.conf
     Active: active (running) since Tue 2023-05-02 13:14:23 CEST; 12s ago
       Docs: man:pacemakerd
   Main PID: 5332 (pacemakerd)
      Tasks: 9
     CGroup: /system.slice/pacemaker.service 
May 02 13:14:28 hana00 SAPHanaController(rsc_SAPHanaCon_HA1_HDB10)[5498]: ERROR: ACT: Cannot find sapstartsrv and sapcontrol executable, please set DIR_EXECUTABLE parameter!
May 02 13:14:28 hana00 pacemaker-controld[5339]:  notice: Result of probe operation for rsc_SAPHanaCon_HA1_HDB10 on hana00: not running 


In the specific case of majority maker nodes for SAP HANA scale-out clusters, the
message can safely be ignored. In this case there is neither SAP HANA nor SAP
hostagent installed by intention.

If a corosync quorum device is used instead of the majority maker node, the
situation will not occur. There is no pacemaker on the quorum device.

The message must not to be confused with similar error messages from resource
agents SAPHanaController or SAPHana on regular cluster nodes. On regular cluster
nodes this error has to be taken serious. There it needs investigation.


The pacemaker cluster probes on all nodes for active resources. Even on nodes that
are excluded by location constraints, probes are done to make sure no unexpected
resources are running. Probes are triggered when the pacemaker service is started. 
In case of HANA the probe checks the needed binaries for SAP which are not installed on the
majority maker node.

Additional Information

Manual pages SAPHanaSR-ScaleOut(7), SAPHanaSR_basic_cluster(7)
SUSE TIDs 7024037 7022702 7022984 000019899 000020964


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:000021062
  • Creation Date: 05-May-2023
  • Modified Date:05-May-2023
    • SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

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