VMware Cloud Community
dderic
Contributor
Contributor
Jump to solution

How to Start/Stop/Restart Tools in CentOS

Hello,

So I have VMware tools installed in Centos.  I know it starts up by itself.  How do I manually start/stop/restart it?  I've looked in /etc/rc.d/init.d and I can't seem to find the script.

Thanks!

Eric

0 Kudos
1 Solution

Accepted Solutions
nirvy
Commander
Commander
Jump to solution

Try:

/etc/vmware-tools/services.sh restart

View solution in original post

0 Kudos
9 Replies
gaspipe
Enthusiast
Enthusiast
Jump to solution

service vmware-tools {start|stop|status|restart|force-reload}

0 Kudos
dderic
Contributor
Contributor
Jump to solution

I tried that, says unrecognized service?  Thanks for replying though.

0 Kudos
nirvy
Commander
Commander
Jump to solution

Try:

/etc/vmware-tools/services.sh restart

0 Kudos
abirhasan
Enthusiast
Enthusiast
Jump to solution

Have you tried with this command.?

# service vmware start




abirhasan   
0 Kudos
dderic
Contributor
Contributor
Jump to solution

Thanks nirvy, that did it! 

Can I simply stick services.sh in /etc/rc.d/init.d and use chkconfig/ntsysv to configure its startup/shutdown?

0 Kudos
dderic
Contributor
Contributor
Jump to solution

Doh.

[root@asdf init.d]# chkconfig --add vmware
service vmware does not support chkconfig
[root@asdf init.d]#
0 Kudos
dderic
Contributor
Contributor
Jump to solution

So I grabbed the RPMs from:

http://packages.vmware.com/tools/esx/latest/rhel6/x86_64/index.html

Specifically, vmware-tools-services-8.6.5-3.x86_64.rpm and it's dependencies.  I installed it with Yum.  It installed /etc/rc.d/init.d/vmware-tools-services which chkconfig supports.

Everything seems to work, start, and stop correctly.  The only thing is vSphere Client says:

"VMware Tools: (?) Running (3rd-party/Independent)"

... instead of ...

"VMware Tools: (check) Running (Current)"

I'm not sure if this is the ideal way of getting VMware tools on CentOS.  Anyone care to comment?

While the RPMs are listed as 3rd-party/Independent, it does works properly as an initialization script.

0 Kudos
gaspipe
Enthusiast
Enthusiast
Jump to solution

The "3rd party/independent" remark is to be expected, if installing VMware tools from source other than the vSphere/ESXi itself, I believe. It is somewhat strange that the traditional way didn't work for you, as CentOS definitely can run/start/strop VMware tools which are installed traditionally. Maybe there were some problems you didn't notice during installation which caused this behaviour.

0 Kudos
gaspipe
Enthusiast
Enthusiast
Jump to solution

0 Kudos