ODA OAKERR:7008 Error encountered while stopping VM - Error: Domain cannot be shutdown

Asset ID:	1-72-2294434.1
Update Date:	2017-08-24
Keywords:

Solution Type Problem Resolution Sure

Solution 2294434.1 : ODA OAKERR:7008 Error encountered while stopping VM - Error: Domain cannot be shutdown

Applies to:

Oracle Database Appliance X5-2 - Version All Versions and later
Information in this document applies to any platform.

Symptoms

In ODA, stopping VM encounters error: OAKERR:7008

[root@oradb20 ~]# oakcli stop vm oradbdea12

OAKERR:7008 Error encountered while stopping VM - Error: Domain cannot be shutdown

log file shows below contents:

>oakd.log

2017-08-01 09:02:37.358: [ OAKFW][3783239424]{0:109:2} After lock release : Parsed : /opt/oracle/oak/conf/UI_STOP_-2006974650_oradbdea12.xml
2017-08-01 09:02:37.358: [ ADAPTER][3783239424]{0:109:2} OAKERR:7008 Error encountered while stopping VM - Error: Domain cannot be shutdown

2017-08-01 09:02:37.358: [ OAKFW][3783239424]{0:109:2} Command : stop for: oradbdea12 completed with status: FAIL
2017-08-01 09:02:37.359: [ OAKFW][3791632128][F-ALGO]{0:109:2} Engine received reply for command : stop for: oradbdea12

>doakcli.log

2017-08-01 09:02:36,403 doakcli_log INFO About to run command stop vm oradbdea12 <<<<
2017-08-01 09:02:36,403 doakcli_log DEBUG trying to get the master node
2017-08-01 09:02:36,403 doakcli_log DEBUG Trying to contact http://192.168.19.21:8881
2017-08-01 09:02:36,523 doakcli_log INFO 0 call to getNodeMode() returned 1
2017-08-01 09:02:36,523 doakcli_log INFO trying to contact master node 0
2017-08-01 09:02:36,523 doakcli_log DEBUG command being used stop vm oradbdea12
2017-08-01 09:02:38,125 doakcli_log DEBUG Command returned
['\nOAKERR:7008 Error encountered while stopping VM - Error: Domain cannot be shutdown\n\n', ''] <<<<<
2017-08-01 09:51:47,573 doakcli_log INFO About to run command

Changes

None

Cause

VM went to bad/unstable state for multiple reasons like: space issue on mount point, last shutdown was not clean etc. Hence on stopping vm using command: oakcli stop vm can throw error OAKERR:7008

Solution

Restart xend services from dom0 (the hypervisor for ODA) of both the nodes

#restart xend service

Note 1: Restarting xend deamon, offlines all the guest VM's running on the node. As an alternate, if the problem VM is accessible, login and shut it down manually or kill the VM using its process id (ps -ef|grep <<VM name as it appears in command xm list>>)

Note 2: VM's should come back online after xend restart, if it doesn't start the VM manually: oakcli start vm <<vm name>>

Attachments

This solution has no attachment