• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 402
  • Last Modified:

Cannot restart vCenter VM after planned ESXi shutdown

Hello Experts,
I had to power off my network today for a UPS upgrade. I put the hosts in maintenance mode, shutdown all VM's, and shutdown the hosts using esxcli system shutdown poweroff -r "shutdown reason string". Now when I SSH into the host, after turning maintenance mode off and verifying , I enter vim-cmd vmsvc/power.on <vmid> and get "Powering on VM:  Power on failed". When I try to access the logs with /var/log/hostd.log I get "Permission denied" even though I am logged in as root user. When I run vim-cmd vmsvc/getallvms (I have 3 VM's on this host) it shows this line three times: "Skipping invalid VM <vmid>". vCenter is on one of these VM's.

Any help would be extremely appreciated.
0
Filo
Asked:
Filo
  • 6
  • 2
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
why not connect via vSphere Client direct to host, and Power On.
0
 
FiloAuthor Commented:
Thanks for the suggestion. If I download and install vSphere Client on my PC, wouldn't I have to rebuild the vSphere configuration so it can communicate to the host and vCenter VM? I haven't config'd vSphere from a fresh install before.

I should have mentioned I am on version 5.5
0
 
FiloAuthor Commented:
Alright, I connected directly to the host and was able to get into the logs using the same login that I was using over SSH. I am seeing errors regarding "the iscsi initiator could not establish a network connection to the target" and am digging into that now.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
FiloAuthor Commented:
I resolved the iscsi problem (part of the SAN array was still down due to a loose power cord), but I am still having the same problems.
0
 
pjamCommented:
Possibly need to reboot since SAN was down when you booted and it cold not be found.  Just a suggestion.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Thanks for the suggestion. If I download and install vSphere Client on my PC, wouldn't I have to rebuild the vSphere configuration so it can communicate to the host and vCenter VM? I haven't config'd vSphere from a fresh install before.

I should have mentioned I am on version 5.5

I think you are thinking about this too much! the answer is No!!!!


What on earth are you talking about here..... get it downloaded 5.5 vSphere client, install, and connect directly to ESXi host, using root username and password.


Part 2: HOW TO: Connect to the VMware vSphere Hypervisor 5.1 (ESXi 5.1) using the vSphere Client
0
 
FiloAuthor Commented:
I apologize for the inexperience/ignorance, but your suggestion Andrew did work very simply. I downloaded vCenter on my PC, connected to the host, and powered on the VM. I'm perplexed/frustrated that the CLI commands didn't work, but I'm just glad to be back up.
0
 
FiloAuthor Commented:
Also may have made a difference that I rebooted the host again after the SAN came back up, not sure if that helped.
0
 
FiloAuthor Commented:
I did have to restart each host in order for their VM's to show up in vCenter Inventory. I suspect this is because of the SAN issue when the hosts were initially powered on.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now