VMware Cloud Community
regiscamy
Contributor
Contributor
Jump to solution

Can't power on vcenter

Hello everybody,

We cannot start the vCenter on a esx 6.0 host when I execute this command :

[root@aut-srv-esx4:~] vim-cmd vmsvc/power.on 4

Powering on VM:

Power on failed

The status of the Vcenter is:

[root@aut-srv-esx4:~] vim-cmd vmsvc/power.getstate 4

Retrieved runtime info

Powered off

The hostd.log shows the folowing error:

2016-07-01T09:36:56.409Z info hostd[3F98CB70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=65734394] Event 119 : User root@127.0.0.1 logged in as VMware-client/5.1.0

2016-07-01T09:36:56.411Z info hostd[FF982AE0] [Originator@6876 sub=Vimsvc.TaskManager opID=65734397 user=root] Task Created : haTask-4-vim.VirtualMachine.powerOn-116759414

2016-07-01T09:36:56.411Z info hostd[3FE81B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=65734397 user=root] Event 120 : aut-srv-vce6 on host aut-srv-esx4.autotrans.fr in ha-datacenter is starting

2016-07-01T09:36:56.411Z warning hostd[3FE81B70] [Originator@6876 sub=Vmsvc.vm:/vmfs/volumes/55e56065-d2d28ea9-0765-d4ae52b78b88/aut-srv-vce6/aut-srv-vce6.vmx opID=65734397 user=root] State Transition (VM_STATE_OFF -> VM_STATE_POWERING_ON) not allowed for this Vm

2016-07-01T09:36:56.411Z info hostd[3FE81B70] [Originator@6876 sub=Default opID=65734397 user=root] AdapterServer caught exception: vim.fault.InvalidState

2016-07-01T09:36:56.411Z info hostd[3FE81B70] [Originator@6876 sub=Vimsvc.TaskManager opID=65734397 user=root] Task Completed : haTask-4-vim.VirtualMachine.powerOn-116759414 Status error

2016-07-01T09:36:56.414Z info hostd[3FEC2B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=657343a1 user=root] Event 121 : User root@127.0.0.1 logged out (login time: Friday, 01 July, 2016 09:36:56, number of API invocations: 0, user agent: VMware-client/5.1.0)

Can you help us please ?

Thanks in advance

0 Kudos
1 Solution

Accepted Solutions
peetz
Leadership
Leadership
Jump to solution

Hi,

please check the VM's status with the vSphere Client (connecting directly to the ESXi host) or the ESXi builtin Host Client (available since 6.0 U2) and if there are any tasks running on the VM (e.g. a Snapshot removal) that might prevent it from powering on.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de

View solution in original post

0 Kudos
5 Replies
TheVElement
VMware Employee
VMware Employee
Jump to solution

Have a look in the virtual machine's vmware.log file.

0 Kudos
peetz
Leadership
Leadership
Jump to solution

Hi,

please check the VM's status with the vSphere Client (connecting directly to the ESXi host) or the ESXi builtin Host Client (available since 6.0 U2) and if there are any tasks running on the VM (e.g. a Snapshot removal) that might prevent it from powering on.

- Andreas

Twitter: @VFrontDe, @ESXiPatches | https://esxi-patches.v-front.de | https://vibsdepot.v-front.de
0 Kudos
regiscamy
Contributor
Contributor
Jump to solution

This log contains nothing new

0 Kudos
TheVElement
VMware Employee
VMware Employee
Jump to solution

Two things to try:

1. Try removing the virtual machine from inventory and re-adding it.

2. Check to see if there are any files that are locked (though if there were, you should've seen mention of this in the vmware.log file). See KB 10051 for details on this (https://kb.vmware.com/kb/10051).

0 Kudos
dyno
Contributor
Contributor
Jump to solution

in my case, it simply because the host is in maintenance mode.