VMware Cloud Community
upcvmteam
Contributor
Contributor

Can't run esxtop

I am trying to get %ready information on one of my hosts, but when I try to trun esxtop I get the following error, and my ssh session disconnects.

Connect via vmauthd failed. -5 Not connected: Couldn't connect to serverd[/i]

Any clues?

0 Kudos
14 Replies
sbeaver
Leadership
Leadership

Who are you logged in as? Try "su -" to get to root and try again

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
bretti
Expert
Expert

Can you run other commands like top or ps -ef?

0 Kudos
upcvmteam
Contributor
Contributor

I am logged in as root

0 Kudos
upcvmteam
Contributor
Contributor

I am able to run top and ps -ef

0 Kudos
sbeaver
Leadership
Leadership

Did you log in as root or do you su to root?

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**
0 Kudos
bretti
Expert
Expert

One more question. ESX 3 or ESX 2?

0 Kudos
upcvmteam
Contributor
Contributor

ESX 2.5.4

I logged in as root.

0 Kudos
bretti
Expert
Expert

Sorry my ESX 2.5 is getting rusty. Can you run these commands.

\[root@srv-genv-vms01 root]# service vmware-vpxa status

vmware-vpxa is running

\[root@srv-genv-vms01 root]# service httpd.vmware status

httpd (pid 21368 1612 1598) is running...

\[root@srv-genv-vms01 root]#

0 Kudos
upcvmteam
Contributor
Contributor

Both services are running

Sorry my ESX 2.5 is getting rusty. Can you run these

commands.

\[root@srv-genv-vms01 root]# service vmware-vpxa

status

vmware-vpxa is running

\[root@srv-genv-vms01 root]# service httpd.vmware

status

httpd (pid 21368 1612 1598) is running...

\[root@srv-genv-vms01 root]#

0 Kudos
bretti
Expert
Expert

You might try restarting the management agent from the properties of the host within virtual center. However I'm not sure that will help the situation. Can you run esxtop on any other host servers without an issue?

0 Kudos
bretti
Expert
Expert

This is a little more harsh but you can also try to kill the ccagent process.

ps -ef | grep cc

root 12691 12488 0 Mar01 ? 00:00:00 /usr/sbin/vmware-ccagent

kill -9

I believe it will restart the process on it's own. Last resort would be a reboot of the host.

0 Kudos
upcvmteam
Contributor
Contributor

This is a little more harsh but you can also try to

kill the ccagent process.

ps -ef | grep cc

root 12691 12488 0 Mar01 ? 00:00:00

/usr/sbin/vmware-ccagent

kill -9 <PID>

I believe it will restart the process on it's own.

Last resort would be a reboot of the host.

This server isn't running ccagent it's running serverd

Refference: http://kb.vmware.com/vmtnkb/search.do?cmd=displayKC&docType=kc&externalId=1840&sliceId=SAL_Public&di...

I killed serverd and allowed it to restart, but no dice. The problem is not resolved

0 Kudos
bretti
Expert
Expert

Cool, learn something new every day. I did not know about that difference between serverd and ccagent.

I think you may have to move to the last resort. Reboot the host.

Is this the only host you are having this issue on?

Other than that I'm kind of out of ideas.

0 Kudos
upcvmteam
Contributor
Contributor

Cool, learn something new every day. I did not know

about that difference between serverd and ccagent.

I think you may have to move to the last resort.

Reboot the host.

Is this the only host you are having this issue on?

Other than that I'm kind of out of ideas.

Yeah this is the only one. You're probably right. Looks like I'm just going to have to wait until the next time I can reboot it.

0 Kudos