[ClusterLabs] why some resources blocked

[Ken Gaillot]

On Fri, 2018-03-02 at 11:53 +0100, Mevo Govo wrote:
> 
> Hi, 
> 
> I am new in pacemaker, corosync and on this list. 
> I created a cluster (based on "Clusters from Scratch" doc). The DRBD
> and my filesystem on it work fine. Then I add an oracle and oralsnr
> resource. But these oracle resources remain stopped. I can start and
> stop the ora resources well by "pcs resource debug-start". (I can
> login into database, lsnrctl status ...). Could you help me, why do
> not these resources start automatically? I do not see errors in
> "/var/log/cluster/corosync.log", only this:
> 
> Mar  1 10:44:40 xetest1 crmd[12440]: warning: Input I_ELECTION_DC
> received in state S_INTEGRATION from do_election_check
> Mar  1 10:44:40 xetest1 pengine[12439]:  notice: On loss of CCM
> Quorum: Ignore
> Mar  1 10:44:40 xetest1 pengine[12439]:  notice: Start  
> fs_drbd1#011(xetest1)
> Mar  1 10:44:40 xetest1 pengine[12439]:  notice: Start  
> ora_listener#011(xetest1 - blocked)
> Mar  1 10:44:40 xetest1 pengine[12439]:  notice: Start  
> ora_db_xe#011(xetest1 - blocked)
> 
> 
> [root at xetest1 /]# pcs status
> Cluster name: cluster_xetest
> Stack: corosync
> Current DC: xetest2 (version 1.1.16-12.el7-94ff4df) - partition with
> quorum
> Last updated: Fri Mar  2 10:03:04 2018
> Last change: Fri Mar  2 10:02:48 2018 by root via cibadmin on xetest1
> 
> 2 nodes configured
> 5 resources configured
> 
> Online: [ xetest1 xetest2 ]
> 
> Full list of resources:
> 
>  Master/Slave Set: drbd1_sync [drbd1]
>      Masters: [ xetest1 ]
>      Slaves: [ xetest2 ]
>  fs_drbd1       (ocf::heartbeat:Filesystem):    Started xetest1
>  ora_listener   (ocf::heartbeat:oralsnr):       Stopped
>  ora_db_xe      (ocf::heartbeat:oracle):        Stopped
> 
> Daemon Status:
>   corosync: active/disabled
>   pacemaker: active/disabled
>   pcsd: active/disabled
> [root at xetest1 /]#
> 
> # I created oracle resources by these commands (OCFMON user also
> created successful during debug-start)
> 
> pcs -f clust_ora_cfg_tmp resource create ora_listener
> ocf:heartbeat:oralsnr \
>   sid="XE" \
>   home="/u01/app/oracle/product/11.2.0/xe" \
>   user="oracle" \
>   listener="LISTENER" \
>   op monitor interval=30s
> 
> pcs -f clust_ora_cfg_tmp constraint colocation add ora_listener with
> fs_drbd1 INFINITY
> pcs -f clust_ora_cfg_tmp constraint order promote fs_drbd1 then start
> ora_listener

^^^ fs_drbd1 is not a master/slave resource, so it can't be promoted

I'm guessing you want to colocate fs_drbd1 with the master role of
drbd1_sync (and order it after the promote of that).

If you want ora_listener and then ora_db_exe to start in order after
that, I'd group fs_drbd1, ora_listener, and ora_db_exe, then
colocate/order the group with the master role of drbd1_sync.

> 
> pcs -f clust_ora_cfg_tmp resource create ora_db_xe
> ocf:heartbeat:oracle \
>   sid="XE" \
>   home="/u01/app/oracle/product/11.2.0/xe" \
>   user="oracle" \
>   monuser="OCFMON" \
>   monpassword="******" \
>   shutdown_method="immediate" \
>   op monitor interval=30s
> 
> pcs -f clust_ora_cfg_tmp constraint colocation add ora_db_xe with
> ora_listener INFINITY
> pcs -f clust_ora_cfg_tmp constraint order promote ora_listener then
> start ora_db_xe
> 
> pcs -f clust_ora_cfg_tmp constraint
> pcs -f clust_ora_cfg_tmp resource show
> 
> pcs cluster cib-push clust_ora_cfg_tmp
> pcs status
> 
> Thanks: lados.
> 
-- 
Ken Gaillot <kgaillot at redhat.com>