Service error on Ubuntu 14.04

[bshow80]

I receive this error every time I run "puppet agent --test" and the open-vm-tools service is running already.

Error: Could not start Service[open-vm-tools]: Execution of '/etc/init.d/open-vm-tools start' returned 1: * Starting open-vm daemon vmtoolsd
Error: /Stage[main]/Openvmtools/Service[open-vm-tools]/ensure: change from stopped to running failed: Could not start Service[open-vm-tools]: Execution of '/etc/init.d/open-vm-tools start' returned 1: * Starting open-vm daemon vmtoolsd

[razorsedge]

What version of operating system, Open VM Tools, and Puppet are you using?

[bshow80]

Unbuntu 14.04 Server
Puppet 3.7.5
Open VM Tools 2:9.4.0-1280544-5ubuntu6.2

On Fri, Apr 10, 2015 at 1:39 AM, Mike Arnold notifications@github.com
wrote:

What version of operating system, Open VM Tools, and Puppet are you using?

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[razorsedge]

And I should have read the title of the issue to know one of those answers... :-(

Try passing the parameter service_hasstatus => true in the main class.

class { '::openvmtools':
  service_hasstatus => true,
}

[bshow80]

I am still receiving

Error: Could not start Service[open-vm-tools]: Execution of
'/etc/init.d/open-vm-tools start' returned 1: * Starting open-vm daemon
vmtoolsd
Error: /Stage[main]/Openvmtools/Service[open-vm-tools]/ensure: change from
stopped to running failed: Could not start Service[open-vm-tools]:
Execution of '/etc/init.d/open-vm-tools start' returned 1: * Starting
open-vm daemon vmtoolsd

although the service is in fact running.

On Fri, Apr 10, 2015 at 10:09 AM, Mike Arnold notifications@github.com
wrote:

And I should have read the title of the issue to know one of those
answers... :-(

Try passing the parameter service_hasstatus => true in the main class.

class { '::openvmtools':
service_hasstatus => true,
}

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[razorsedge]

I have pushed version 1.0.0 to the Puppet Forge. Please let me know if this fixes the problem.

[bshow80]

Mike,

This seems to have fixed it. Thank you!

On 4/12/15, Mike Arnold notifications@github.com wrote:

Closed #1 via 21cd8c1.

---

Reply to this email directly or view it on GitHub:
#1 (comment)