Quantcast
Channel: Data Protector Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3189

(DP) Support Tip: modular package for DP CM can not move to "up/running" status

$
0
0

[Customer symptom]
A modular package for DP CM is "starting" status forever .


# cmviewcl

CLUSTER        STATUS
cluster1       up

  NODE           STATUS       STATE
  node1          up           running

    PACKAGE        STATUS           STATE            AUTO_RUN    NODE
    ob2cl          starting         starting         disabled    node1

  NODE           STATUS       STATE
  node2          up           running

 

[Cause]
In a configuration file (ex. ob2cl.conf) , external_script is set as follows .

 

ex.)
external_script                       /etc/cmcluster/ob2cl/test_sleep.sh

 

When a cluster package is started up , external_script is executed prior to service_cmd .
If external_script never finishes , the package status can not move to "up" .

In case of executing service_cmd , even if service_cmd doesn't exit , the package status can move to "up" .
For instance , "csfailover.ksh start" doesn't exit to monitor server processes (omnisv.sh start_mon -timeout 3) .


[Workaround / Fix]
Please pay attention not to set any scripts that never finishes as external_script in a configuration file .


Viewing all articles
Browse latest Browse all 3189

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>