pacemaker 1.1.15-21.1
libpacemaker3 1.1.15-21.1
DB: SAP HANA SPS 12

Manually HANA DB starts and work perfectly, Master/Primary replicates to Secondary/Slave perfectly.

But when start the HANA DB pacemaker resource, crm_mon shows that HANA DB resource gets started and both the nodes becomes Slave, and keep showing them Slave forever. However HANA DB didn't get start from the cluster which could be verified by running "sapcontrol -nr 00 -function GetProcessList" which shows system is not running.

HANA Topology and DB resource configuration:

primitive rsc_SAPHanaTopology_TST_HDB00 ocf:suse:SAPHanaTopology \
    operations $id=rsc_sap2_TST_HDB00-operations \
    op monitor interval=10 timeout=600 \
    op start interval=0 timeout=600 \
    op stop interval=0 timeout=300 \
    params SID=TST InstanceNumber=00

primitive rsc_SAPHana_TST_HDB00 ocf:suse:SAPHana \
    operations $id=rsc_sap_TST_HDB00-operations \
    op start interval=0 timeout=3600 \
    op stop interval=0 timeout=3600 \
    op promote interval=0 timeout=1600 \
    op monitor interval=60 role=Master timeout=700 \
    op monitor interval=61 role=Slave timeout=700 \
params SID=TST InstanceNumber=00 PREFER_SITE_TAKEOVER=true DUPLICATE_PRIMARY_TIMEOUT=600 AUTOMATED_REGISTER=true

ms msl_SAPHana_TST_HDB00 rsc_SAPHana_TST_HDB00 \
meta is-managed=true notify=true clone-max=2 clone-node-max=1 target-role=Started interleave=true

clone cln_SAPHanaTopology_TST_HDB00 rsc_SAPHanaTopology_TST_HDB00 \
meta is-managed=true clone-node-max=1 target-role=Started interleave=true

Following events are logged when cluster tries to start the HANA DB resource: 2017-05-11T15:29:35.775044+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation p_fence_saphdbtst1_monitor_0 locally on saphdbtst2 2017-05-11T15:29:35.776600+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation p_fence_saphdbtst1_monitor_0 on saphdbtst1 2017-05-11T15:29:35.777021+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation p_fence_saphdbtst2_monitor_0 locally on saphdbtst2 2017-05-11T15:29:35.779302+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation p_fence_saphdbtst2_monitor_0 on saphdbtst1 2017-05-11T15:29:35.779770+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_ip_TST_HDB00_monitor_0 locally on saphdbtst2 2017-05-11T15:29:35.843129+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_ip_TST_HDB00_monitor_0 on saphdbtst1 2017-05-11T15:29:35.843567+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_SAPHana_TST_HDB00:0_monitor_0 locally on saphdbtst2 2017-05-11T15:29:35.845257+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_SAPHana_TST_HDB00:0_monitor_0 on saphdbtst1 2017-05-11T15:29:35.845682+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_SAPHanaTopology_TST_HDB00:0_monitor_0 locally on saphdbtst2 2017-05-11T15:29:35.847105+05:00 saphdbtst2 crmd[10195]: notice: Initiating monitor operation rsc_SAPHanaTopology_TST_HDB00:0_monitor_0 on saphdbtst1 2017-05-11T15:29:35.902758+05:00 saphdbtst2 crmd[10195]: notice: Result of probe operation for p_fence_saphdbtst1 on saphdbtst2: 7 (not running) 2017-05-11T15:29:35.903336+05:00 saphdbtst2 crmd[10195]: notice: Result of probe operation for p_fence_saphdbtst2 on saphdbtst2: 7 (not running) 2017-05-11T15:29:35.938865+05:00 saphdbtst2 crmd[10195]: notice: Result of probe operation for rsc_ip_TST_HDB00 on saphdbtst2: 7 (not running)
2017-05-11T15:29:35.950344+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:35.984612+05:00 saphdbtst2 systemd[1]: Started Session c45235 of user tstadm.
2017-05-11T15:29:36.432092+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:36.456621+05:00 saphdbtst2 systemd[1]: Started Session c45236 of user tstadm.
2017-05-11T15:29:36.463414+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:36.468627+05:00 saphdbtst2 systemd[1]: Started Session c45237 of user tstadm. 2017-05-11T15:29:36.991382+05:00 saphdbtst2 SAPHana(rsc_SAPHana_TST_HDB00)[10203]: INFO: RA ==== begin action monitor_clone (0.152.17) ====
2017-05-11T15:29:37.050443+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:37.072682+05:00 saphdbtst2 systemd[1]: Started Session c45238 of user tstadm.
2017-05-11T15:29:40.077857+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:40.100617+05:00 saphdbtst2 systemd[1]: Started Session c45239 of user tstadm. 2017-05-11T15:29:40.121749+05:00 saphdbtst2 crmd[10195]: notice: Transition aborted by status-180881403-master-rsc_SAPHana_TST_HDB00 doing create master-rsc_SAPHana_TST_HDB00=5: Transient attribute change
2017-05-11T15:29:40.614835+05:00 saphdbtst2 su: (to tstadm) root on none
2017-05-11T15:29:40.636628+05:00 saphdbtst2 systemd[1]: Started Session c45240 of user tstadm. 2017-05-11T15:29:43.363140+05:00 saphdbtst2 SAPHana(rsc_SAPHana_TST_HDB00)[10203]: INFO: RA ==== end action monitor_clone with rc=7 (0.152.17) (8s)==== 2017-05-11T15:29:43.367148+05:00 saphdbtst2 lrmd[10192]: notice: rsc_SAPHana_TST_HDB00_monitor_0:10203:stderr [ Error performing operation: No such device or address ] 2017-05-11T15:29:43.367490+05:00 saphdbtst2 lrmd[10192]: notice: rsc_SAPHana_TST_HDB00_monitor_0:10203:stderr [ Error performing operation: No such device or address ] 2017-05-11T15:29:43.407874+05:00 saphdbtst2 crmd[10195]: notice: Result of probe operation for rsc_SAPHana_TST_HDB00 on saphdbtst2: 7 (not running) 2017-05-11T15:29:43.408223+05:00 saphdbtst2 crmd[10195]: notice: saphdbtst2-rsc_SAPHana_TST_HDB00_monitor_0:18 [ Error performing operation: No such device or address\nError performing operation: No such device or address\n ]


Nutshell: crm_mon shows that HANA DB started and both nodes are Slave, but DB didn't get started by cluster, sapcontrol command shows that HANA is not running on either node.



--
Regards,

Muhammad Sharfuddin

_______________________________________________
Users mailing list: Users@clusterlabs.org
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to