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

(DP) Support Tip: mmd and kms are Down

$
0
0

[Error Message]

After restarting Data Protector server processes , mmd and kms are down and backup jobs can not be started .


/opt/omni/sbin/omnisv -status

     ProcName      Status  [PID]
==============================
     crs         : Active  [22621]
     mmd         : Down
     kms         : Down
     hpdp-idb    : Active  [7347]
     hpdp-idb-cp : Active  [7367]
     hpdp-as     : Active  [7390]
     omnitrig    : Active
     Sending of traps disabled.
==============================
Status: At least one of the Data Protector processes/services is not running.


This system is configured to restart DP services automatically after a last backup job of a day by detecting a completion of omnib command .

 

[Cause]

It seems that CRS has not been stopped normally .

- /var/opt/omni/server/log/omnisv.log
2017-2-5 4:48:35 - STOP
Cannot stop "crs" service, system error:
[1053]

2017-2-5 4:50:27 - START
HPE Data Protector services successfully started.


MMD and KMS are initiated by CRS start up .
If CRS didn't stop and remained, CRS will be skipped at the next start up .
Because the start up of CRS doesn't happen , MMD and KMS will not be started up also .

Regarding the situation that CRS didn't stop , CRS seems to have been busy .
According to sm.log , MMD and KMS were stopped before BSM .
omnib command might have finished and returned , but CRS still had some activities for BSM .


- /var/opt/omni/server/log/sm.log
2017-02-05 04:47:32.851  BSM.5834.1 ["/sm/smcmn/smmain.c $Rev: 53174 $ $Date:: 2016-04-26 06:17:01 ":2088] A.09.00 b109
Session started.

2017-02-05 04:48:17.381  DBSM.6369.1 ["/sm/smcmn/smmain.c $Rev: 53174 $ $Date:: 2016-04-26 06:17:01 ":2088] A.09.00 b109
Session started.

2017-02-05 04:48:32.771  DBSM.6369.1 ["/sm/smcmn/smmain.c $Rev: 53174 $ $Date:: 2016-04-26 06:17:01 ":2272] A.09.00 b109
Session ended.

2017-02-05 04:48:35.311  MMD.22619.1 ["/sm/smcmn/unix.c $Rev: 53394 $ $Date:: 2016-05-15 10:23:25 ":154] A.09.00 b109
Session killed.

2017-02-05 04:48:35.321  KMS.22620.0 ["/sm/smcmn/unix.c $Rev: 53394 $ $Date:: 2016-05-15 10:23:25 ":154] A.09.00 b109
Session killed.

2017-02-05 04:48:35.351  BSM.5834.1 ["/sm/smcmn/smmain.c $Rev: 53174 $ $Date:: 2016-04-26 06:17:01 ":2249] A.09.00 b109
Session ended.

 

[Workaround / Fix]

It will be a kind of timing issues .
To avoid the error situation ,it is suggested to insert some sleep before executing omnisv stop even though omnib command returned without any error .


Viewing all articles
Browse latest Browse all 3189

Trending Articles