Link to home
Start Free TrialLog in
Avatar of bereten
bereten

asked on

Vcenter not accessible after upgrading from 5.5 0b to 5.5 2b

Hello, I updated my vcenter last night successfully from 5.5 0b to 5.5 2b, however I couldn't connect via vsphere client to VCenter after the upgrade, I checked all services running. I tried connecting then via vsphere web client and found no inventory. I had a clone as backup plan  that I turned on to keep the environment running and services available.
I have now powered down original Vcenter and need to troubleshoot this issue, any help?
between after I successfully installed vcenter, I moved on to upgrade update manager and I was asked at some point to enter credentials, my colleague that keep login info attempted 3 times locking the account, not sure this has any impact on vcenter not being accessible.
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

I updated my vcenter last night successfully from 5.5 0b to 5.5 2b

however I couldn't connect via vsphere client to VCenter after the upgrade

Does not seem like a successful upgrade, if it was successful you would be able to connect!

I'm a little confused as to where you are now

1. Can you now connect to vCenter Server via vSphere Client and Web Client?
Avatar of bereten
bereten

ASKER

Hi Andrew, was not able to connect with vsphere client, when I did with web client no inventory found. at the moment i'm running on the clone I had in case of failure. I have powered down original Vcenter, Vcenter version on original server has been upgraded to 5.5 2b( that's why I used "successfully") but unable to connect.
Upgrades are always terrible, and sometimes break.

I would copy your clone, and try again. It would seem permissions have broken.

We have for example a number of vCenter 5.5 installations, that since updates have been applied have broken VMware vCenter Orchestrator and Ruby vSphere Console - for unknown reasons, which are still working with VMware Support with as too why!
It was UPDATE and not UPGRADE.
It looks like vpxd (vcenter server) is not started.
Updates or Upgrades, they are all the same! - "splitting hairs!"

Change of code, configuration files, as I put in my follow up.....

" We have for example a number of vCenter 5.5 installations, that since updates "...

I would repeat the Upgrade/Update and see if you can reproduce the issue, and then we will have to start looking at upgrade/update logs, and vCenter Server logs and events.

and if you have a VMware Support and Subscription, time for VMware Support to start earning their money, bang it on their Service Desk!

As Critical Service Down!
what does event log say when looking for vpxd?
Avatar of bereten

ASKER

I had a webex session with vmware this morning they suggest i do a re install of  SSO, Vcenter, inventory services etc..
we had done this in 2 steps 03/06  SSO, Inventory services and web client, 03/27 Vcenter. They think i'm having issues cause didn't perform all upgrades same day. If i remove and re-install wouldn't i lose my existing configs, that sounds to me like a clean install not an update?
SOLUTION
Avatar of gheist
gheist
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of bereten

ASKER

Thanks Gheist and Andrew.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial