Puppet client 3.2.X fails to install on Windows 7 x64

[Josh D]

Some of my users are having difficulty installing the Puppet client on their 64-bit Widows machines.  The installation will get get to the point where everything is installed and it attempts to start the service.  The service fails (see relevant information from install log from /l*v below) and then the installer rolls back.  I've tried various ways of launching the installer, had different users attempt to install on the problem machines, etc but always wind up with the same error.  The accounts in question have permission to start/stop services.  Any ideas?

StartServices: Service: Puppet Agent

MSI (s) (88:6C) [09:29:47:321]: Note: 1: 2205 2:  3: Error 

MSI (s) (88:6C) [09:29:47:321]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1920 

Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient privileges to start system services.

MSI (s) (88:20) [09:29:57:739]: I/O on thread 7856 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 8588 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 7504 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 9268 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 6048 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 4460 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 7356 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 8800 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 8316 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 8436 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:739]: I/O on thread 4716 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 6840 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 10224 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 8248 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 4944 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 2860 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 9484 could not be cancelled. Error: 1168

MSI (s) (88:20) [09:29:57:740]: I/O on thread 8116 could not be cancelled. Error: 1168

MSI (s) (88:6C) [09:29:57:740]: Note: 1: 2205 2:  3: Error 

MSI (s) (88:6C) [09:29:57:740]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 

MSI (s) (88:6C) [09:29:57:740]: Product: Puppet -- Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient privileges to start system services.

MSI (s) (88:6C) [09:29:57:742]: Note: 1: 2205 2:  3: Error 

MSI (s) (88:6C) [09:29:57:742]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1602 

Are you sure you want to cancel?

Action ended 9:29:59: InstallFinalize. Return value 3.

[Rob Reynolds]

This error is a lie. :) 

The true issue [1][2][3] had to an encoding bug in a gem that Puppet depends on that was fixed in 3.3.1. We didn't add the PUPPET_AGENT_STARTUP_MODE [4] until 3.4.0 so there isn't a way to tell it not to try to start the service.

The supported way of making it work is to update to at least 3.3.1.

1: http://projects.puppetlabs.com/issues/22493

2: http://projects.puppetlabs.com/issues/22613

3: https://tickets.puppetlabs.com/browse/PUP-316 with a nice video showing repro and fix.

4: http://docs.puppetlabs.com/windows/installing.html#automated-installation

 

MSI (s) (88:6C) [09:29:57:742]: Note: 1: 2205 2:  3: Error 

MSI (s) (88:6C) [09:29:57:742]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1602 

Are you sure you want to cancel?

Action ended 9:29:59: InstallFinalize. Return value 3.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/90b581a2-53f0-4c98-a463-dbe296345161%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Rob Reynolds

Developer, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco - http://bit.ly/pupconf14
Register now and save 40%! Offer expires January 31st.

[Josh D]

On Friday, January 24, 2014 1:02:59 PM UTC-7, Rob Reynolds wrote:

The supported way of making it work is to update to at least 3.3.1.

Just tried installing the 3.4.2 client and had the same problem; service fails to start and the installation is rolled back.  The log is *slightly* different.

StartServices: Service: Puppet Agent

Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient privileges to start system services.

MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37672 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37536 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 29532 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37384 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 38872 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 34136 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33292 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 1136 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33376 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 32688 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31448 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 31128 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 33536 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30684 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 27924 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 11324 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 37092 could not be cancelled. Error: 1168
MSI (s) (94:8C) [09:41:44:708]: I/O on thread 30248 could not be cancelled. Error: 1168
MSI (s) (94:D8) [09:41:44:708]: Product: Puppet -- Error 1920. Service 'Puppet Agent' (puppet) failed to start.  Verify that you have sufficient privileges to start system services.

Are you sure you want to cancel?

Action ended 9:41:50: InstallFinalize. Return value 3.

 

[Rob Reynolds]

Josh,

 Can you try something for me? With the install, can you add the following to it? 

msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual

And tell me if it installs okay?

Then we'll move onto trying to start the service and see what errors crop up.

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/17b9a371-7aa5-4894-bf23-0e1fc5be7b9c%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Josh D]

On Monday, January 27, 2014 10:34:36 AM UTC-7, Rob Reynolds wrote:

Josh,

 Can you try something for me? With the install, can you add the following to it? 

msiexec /qn /i themsilocation.msi PUPPET_AGENT_STARTUP_MODE=Manual

And tell me if it installs okay?

Yep, one step ahead of you.  We were able to install by changing the startup mode to manual.  Attempting to start the service post install, resulted in: Error 1053: The service did not respond to the start or control request in a timely fashion.

There wasn't anything helpful in event viewer so we moved on to starting the agent manually.  The pertinent portion of the output from puppet agent --test --debug --verbose is below:

Error: Could not set 'directory' on ensure: Permission denied - C:/ProgramData/P
uppetLabs/puppet/var/state/graphs
Error: Could not set 'directory' on ensure: Permission denied - C:/ProgramData/P
uppetLabs/puppet/var/state/graphs
Wrapped exception:
Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs
Error: /File[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]/ensure: change f
rom absent to directory failed: Could not set 'directory' on ensure: Permission
denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs

[0;36mDebug: /File
[C:/ProgramData/PuppetLabs/puppet/var/state/graphs]: Nothing to manage: no ensure and the resource doesn't exist [0m
[0;36mDebug: Finishing transaction 38297820 [0m

Error: Could not prepare for execution: Got 3 failure(s) while initializing: Cou
ld not set 'directory' on ensure: Permission denied - C:/ProgramData/PuppetLabs/
puppet/var/state/graphs; Could not set 'directory' on ensure: Permission denied
- C:/ProgramData/PuppetLabs/puppet/var/state/graphs
Wrapped exception:
Permission denied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs; change fr
om absent to directory failed: Could not set 'directory' on ensure: Permission d
enied - C:/ProgramData/PuppetLabs/puppet/var/state/graphs

So I hopped into the PuppetLabs directory and started looking at permissions.  Everything is good up to C:/ProgramData/PuppetLabs/puppet/var.  Meaning the Administrators group has full control and can make modifications.  That is required for running puppet agent manually outside of the service.  Every directory under C:/ProgramData/PuppetLabs/puppet/var is good *except* for C:/ProgramData/PuppetLabs/puppet/var/state.  That directory appears to have been created by the service (system account) and does not have any permissions for "Administrators" set.   I attempted to alter the permissions, but I just get access denied even with an admin account.

So in summary, the service times out for reasons unknown.  Running puppet agent manually fails because Administrators cannot modify anything under C:/ProgramData/PuppetLabs/puppet/var/state

[Rob Reynolds]

Can you blow away the C:/ProgramData/PuppetLabs directory and try the install again?

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/73b52441-e66d-4661-bf1b-fc3737ec4912%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Rob Reynolds]

You should be able to take ownership of the directory you cannot delete as an administrator. Once you have done that you should be able to move forward with deleting those. I think the prior install attempts might have botched something and that directory is not removed.

[Josh D]

On Monday, January 27, 2014 4:15:12 PM UTC-7, Rob Reynolds wrote:

You should be able to take ownership of the directory you cannot delete as an administrator. Once you have done that you should be able to move forward with deleting those. I think the prior install attempts might have botched something and that directory is not removed.

Ok, have some good news to report.  First, uninstalling and blowing away C:\ProgramData\PuppetLabs resulted in the original error when performing a clean uninstall.  However, we did find one combination that worked.

#1. Uninstall and ensure C:\ProgramData is absent
#2. Install with PUPPET_AGENT_STARTUP_MODE=Manual
#3. Following installation and *BEFORE* attempting to run puppet agent service, run puppet agent as admin.

By running "puppet agent" not only did it run to completion unlike past attempts following a failed start of the service, it also mysteriously changed the puppet agent startup mode to automatic and now the puppet service works.

In the past when we followed steps #1 and #2 and attempted to start the service following installation, the service failed to start and broke the client due to permissions.  By running the client before the service, everything is fine and dandy.

[Rob Reynolds]

Josh,

 I'm glad we were able to get you going. However it is slightly troubling to see that the service flips to automatic after running puppet agent. 

Also are you overriding the user the agent installed as to a non-administrative user?

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/bafcdc5d-68b3-4bd1-9236-3d51398fda94%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Josh D]

On Wednesday, January 29, 2014 12:41:06 AM UTC-7, Rob Reynolds wrote:

Josh,

 I'm glad we were able to get you going. However it is slightly troubling to see that the service flips to automatic after running puppet agent. 

Also are you overriding the user the agent installed as to a non-administrative user?

No, we left the default settings when installing (local system account).  We were going to attempt setting the username as a last resort, but couldn't find any documentation on how to change the password post installation.

[Rob Reynolds]

Post installation you would change it like with other services on windows (services.msc, find the service, open properties and change user/password).

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/69339996-a428-41cb-bbfd-ebb1360fd680%40googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.