SAP Knowledge Base Article - Preview

3791805 - Unexpected system-wide stop of cluster protected ASCS/ERS after running sapcontrol on dialog instance to stop only one application instance

Symptom

  • While performing a change activity and trying to stop only one application server, the whole system went down unexpectedly.
  • ASCS and ERS stopped although no maintenance was planned for these instances.
  • history.glf shows: Stop instance by user "trusted unix domain socket user" from "localhost".
  • sapstartsrv.log (or sapstartsrv.old) shows: "CN=..., O=SAP System PKI, C=DE is stopping SAP System at ".
  • Cluster logs show sap_suse_cluster_connector executing stop (for example: fire_resource_action stop ...).
  • The cluster set the resource meta attribute target-role=Stopped, preventing automatic restart until manually cleared.


Read more...

Environment

  • SAP ABAP/JAVA instance on Linux with HA cluster implemented

Product

SAP ERP all versions ; SAP NetWeaver all versions ; SAP S/4HANA all versions

Keywords

sapcontrol, StopSystem, sapstartsrv, history.glf, trusted unix domain socket user, SAP System PKI, pacemaker, sap_suse_cluster_connector, target-role Stopped, unexpected , KBA , BC-CST-STS , Startup Service , BC-OP-LNX , Linux , 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.