vmwaretools

[slune]

hi, i am trying to run /usr/bin/vmware-config-tools.pl -d, but i was
end with exec timeout. I cannot find any think on google. Have anyone
experience with this?
It works, when I run it normally from shell.

this is my exec resource.

{ "vmwaretools_config":
subscribe => [ Package["VMwareTools"] ],
refreshonly => true,
path => "/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/
local/bin",
command => "/usr/bin/vmware-config-tools.pl -d"; }

Thx

[Marc Fournier]

Hello,

> hi, i am trying to run /usr/bin/vmware-config-tools.pl -d, but i was
> end with exec timeout. I cannot find any think on google. Have anyone
> experience with this?

I don't know what the -d switch is for, but AFAIK vmware-config-tools.pl is
an interactive script which waits for user input. This could be the reason
for the timeout you're having.

This doesn't answer your question, but I use openvmtools¹ instead because I
found vmware-tools to be much of a pain to maintain (with or without
puppet). I just pushed onto github[²] the module I use for debian and
redhat. Maybe you'll find it useful.

Marc

[¹] http://open-vm-tools.sourceforge.net/
[²] http://github.com/camptocamp/puppet-openvmtools

[Filip Slunecko]

/usr/bin/vmware-config-tools.pl -d should be without asking. When I run it
in the bash It ends in a minute, without asking any thing.
I found only this bug
(http://photographersofficeonline.com/issues/910), but it's old one
and is closed (solved?).

Filip

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>

[Marc Fournier]

> should be without asking. When I
> run it in the bash It ends in a minute, without asking any thing.

Ok, I suppose this is the part where it compiles a kernel module, which
can indeed take a while. You have a "timeout" parameter which can be
used in this case:

exec { "/usr/bin/vmware-config-tools.pl -d":
timeout => "-1" }

> I found only this bug
> (http://photographersofficeonline.com/issues/910), but it's old one
> and is closed (solved?).

I wonder why redmine is suddenly reachable through
photographersofficeonline.com ? Is this new ? It seems like an error.

Marc

[Joe McDonagh]

Wow I never knew about this option to vmware tools, thanks.

--
Joe McDonagh
AIM: YoosingYoonickz
IRC: joe-mac on freenode
L'ennui est contre-r�volutionnaire

[Filip Slunecko]

I stopped process after 30 minutes (99% CPU whole time). It looks like
it's stuck somewhere. But I don't know how to realize what is wrong.

Filip

[Joe McDonagh]

I've seen behavior like this in scripts that expect a TTY, yet there is
not one... I'm not sure exactly how to handle that...

[Ohad Levy]

the way we solved it is by setting up an additional service which compiles and set the driver (main reason for that was that network gets restarted which might disturb the puppet run)

an example can be found here:
http://theforeman.org/repositories/entry/foreman/app/views/unattended/snippets/_vmware.erb

[Filip Slunecko]

thx, that helps a lot.

Filip

[Trevor Vaughan]

You need to add the following to your exec:

environment => ['PAGER=/bin/cat','DISPLAY=:9']

vmware-config-tools.pl is kind of awful.

Trevor

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>

--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvau...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

[Filip Slunecko]

Thank you very much. I spend 14 days to try to solve this. It was real
nightmare :).

Filip

[Rob McBroom]

On Feb 11, 2010, at 7:10 AM, Marc Fournier wrote:

> [²] http://github.com/camptocamp/puppet-openvmtools

Pardon my ignorance, but why run the `install-open-vm-tools.sh` or `vmware-config-tools.pl` at all?

My manifests for VMWare guests (running RHEL5) just do this:

1. set up a yumrepo for http://packages.vmware.com/tools/esx/4.0/rhel5/$architecture/
2. make sure the “vmware-tools” package is installed
3. make sure the "vmware-tools” service runs

The only problems I’ve had are that the GPG key for that repo doesn’t seem to work (last I checked) and it doesn’t support RHEL4. What am I missing?

--
Rob McBroom
<http://www.skurfer.com/>

The magnitude of a problem does not affect its ownership.

[Dick Davies]

On Tue, Feb 16, 2010 at 3:00 PM, Rob McBroom <mailin...@skurfer.com> wrote:
> On Feb 11, 2010, at 7:10 AM, Marc Fournier wrote:
>
>> [²] http://github.com/camptocamp/puppet-openvmtools
>
> Pardon my ignorance, but why run the `install-open-vm-tools.sh` or `vmware-config-tools.pl` at all?
>
> My manifests for VMWare guests (running RHEL5) just do this:
>
> 1. set up a yumrepo for http://packages.vmware.com/tools/esx/4.0/rhel5/$architecture/
> 2. make sure the “vmware-tools” package is installed
> 3. make sure the "vmware-tools” service runs
>
> The only problems I’ve had are that the GPG key for that repo doesn’t seem to work (last I checked) and it doesn’t support RHEL4. What am I missing?

We had issues with certain modules (vmmemctl) not loading until we'd
run vmware-config-tools.pl. Running the service might have helped, but
at the time there were some widespread performance issues on our ESX
hosts and I wanted to be as blameless as possible - so I chickened out
and went for the 'official' RPMs :)

We install the (official) RPM with Puppet, and do the tools install on
the vmware console when we patch the kernel. I'm not adventurous
enough to have Puppet patch kernels and bounce systems (yet).

[Marcello de Sousa]

I've recently deployed on (via puppet) the following script to deal
automatically with kernel updates:
-----------------------------------
#Automatically updates VMWare tools (to be called from /etc/rc.local)
if [ ! -e /lib/modules/`uname -r`/.vmware_installed ]; then
/usr/bin/vmware-config-tools.pl --default
touch /lib/modules/`uname -r`/.vmware_installed
if [ "$?" -ne 0 ]; then
exit 1
fi
echo "*** Rebooting (VMWare tools update)***"
reboot
fi
-----------------------------------

Kind of a calculated risk, but really handy when you patch lots of machines
:)

Cheers,
Marcello

> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-

> users+un...@googlegroups.com.

[Rafael Brito]

Hey,
Many thanks! I was spending way too much time troubleshooting this
when found your solution!

Rafael

On Feb 13, 7:46 am, Trevor Vaughan <tvaug...@onyxpoint.com> wrote:
> You need to add the following to your exec:
>
> environment => ['PAGER=/bin/cat','DISPLAY=:9']
>
> vmware-config-tools.pl is kind of awful.
>
> Trevor
>
>
>
>
>
> On Thu, Feb 11, 2010 at 4:55 AM, slune <filip.slune...@gmail.com> wrote:
> > hi, i am trying to run /usr/bin/vmware-config-tools.pl -d, but i was
> > end with exec timeout. I cannot find any think on google. Have anyone
> > experience with this?
> > It works, when I run it normally from shell.
>
> > this is my exec resource.
>
> > { "vmwaretools_config":
> >  subscribe   => [ Package["VMwareTools"] ],
> >   refreshonly => true,
> >   path        => "/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/sbin:/usr/
> > local/bin",
> >   command     => "/usr/bin/vmware-config-tools.pl -d";  }
>
> > Thx
>
> > --
> > You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> > To post to this group, send email to puppet...@googlegroups.com.
> > To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.

>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699

> tvaug...@onyxpoint.com