I noticed something strange today with the vpxd services. I upgraded one of my labs over the weekend just for the purpose of break/fix hard core testing.
What happened is I noticed after the upgrade that vSphere client would give error "you are unable to contact remote server to logon" I knew that had to be my vpxd service not being started. So I politely moved over and started the service and changed it from "automatic [delayed start]" to |automatic| and also changed the "log on as" from local system account to a specified account and made that logon account my"domain\domain admin account" filled in the password and applied the changes.
Now heres the weirdness:
After a restart of my vCenter I noticed that vCenter management server would not properly boot. After checking logs I found that the awesome vpxd client was hung in stopping mode (from the earlier restart) It seems the service never stopped when the restart was initiated.
Now, I happily managed to get logged in to a server with 95% CPU utilization initiates services.msc and stopped the service and changed back to automatic delayed and also changed the logon as back to local system account.
Now I've noticed that at any random time I find myslef having to manually restart the vpxd service....
Whats up with that.....
Feel free to weigh in.....
