Crash enqueue server process
Description – crash enqueue server process using
kill
.
Run node – primary node where ASCS is running.
Run steps
[root@hahost01 ~]# ps -ef | grep enq ha1adm 182228 182215 0 16:19 ? 00:00:02 enq.sap1_ASCS00 pf=/usr/sap/HA1/SYS/profile/HA1_ASCS00_ascshost root 190183 178689 0 16:55 pts/0 00:00:00 grep --color=auto enq [root@hahost01 ~]# kill -9 182228
Expected result – because the Start_Program_01 = local
$(_ENQ) pf=$(_PF)
parameter is in the ASCS instance profile, the cluster will
fail over ASCS (message server process and enqueue process) to the secondary
node.
[root@hahost01 ~]# pcs status Cluster name: rhelha Stack: corosync Current DC: hahost02 (version 1.1.19-8.el7_6.5-c3c624ea3d) - partition with quorum Last updated: Wed May 12 16:57:52 2021 Last change: Wed May 12 16:19:17 2021 by ha1adm via crm_resource on hahost02 2 nodes configured 7 resources configured Online: [ hahost01 hahost02 ] Full list of resources: clusterfence (stonith:fence_aws): Started hahost02 Resource Group: HA1_ASCS00_group rsc_fs_ascs00 (ocf::heartbeat:Filesystem): Started hahost02 rsc_vip_ascs00 (ocf::heartbeat:aws-vpc-move-ip): Started hahost02 rsc_ascs00 (ocf::heartbeat:SAPInstance): Started hahost02 Resource Group: HA1_ERS10_group rsc_fs_ers10 (ocf::heartbeat:Filesystem): Started hahost01 rsc_vip_ers10 (ocf::heartbeat:aws-vpc-move-ip): Started hahost01 rsc_ers10 (ocf::heartbeat:SAPInstance): Started hahost01k
Recovery procedure – N/A.