VMware Cloud Community
vkaranam
Enthusiast
Enthusiast
Jump to solution

Re: 500 error

Hello Guys,

I am getting the fillowing error on my vcops-vSphere UI

500 The call failed on the server; see server log for details (StatusCode: 500)

and when i press OK it says

vCenter Operations Manager is being configured to work with your virtual environment.
This may take a few minutes.

Its been like this for past 2 days. It not throwing any values. All i did is restarted the vcops and from then i am getting these errors.

Thanks

VK

0 Kudos
1 Solution
8 Replies
vkaranam
Enthusiast
Enthusiast
Jump to solution

No i ddin't take a look.i will go through it.

The vcops which i am facing the problem was working fine from past 8 months. It appeared suddenly after a reboot.

Thanks

VK

0 Kudos
spravtek
Expert
Expert
Jump to solution

The script mentioned in the KB fixes a potential database corruption ... So might give that a shot ...

Definitely check the logs mentioned in the KB though

vkaranam
Enthusiast
Enthusiast
Jump to solution

I re-booted the vApp again and it working fine now. But i cannot see the effciency pane in the vsphere -UI. i Can see only health and risk as of now and both health and risk are collecting metrics.

Thanks spravtek for the info. let me wait sometime and see what happens.

Thanks

VK

0 Kudos
vkaranam
Enthusiast
Enthusiast
Jump to solution

The efficiency pane has shown up once i login again.

Thanks

VK

0 Kudos
spravtek
Expert
Expert
Jump to solution

I hope this is not going to be a trend like with Windows machines 😉

Good luck!

0 Kudos
IamTHEvilONE
Immortal
Immortal
Jump to solution

the KB is only for 5.0.0 ... as that was fixed in subsequent releases.

Error 500 can sometimes mean that you ran out of space, which would also explain certain resources not displaying badges.

can you make sure to run a `df -h` on each VM to see if you have exhausted space on either?

0 Kudos
vkaranam
Enthusiast
Enthusiast
Jump to solution

Hey IamtheEvilone,

My first check was df-h. All the machines have more than 50% of space. Then i rebooted the vApp which fixed the issue.

Thanks

VK

0 Kudos