On 28 Okt., 15:09, Kikanny <kika...@gmail.com> wrote:
> Hmmm...I've made some progress. There seemed to be some problems with
> Ruby 1.9.1. So I reverted back to Ruby 1.8.7 and followed the steps
> again as outlined 
> inhttp://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows.
> Installed an additional gem called win32-security. This allowed the
> puppet daemon to actually run!!
>
> I do get a bunch of messages saying "No such file or directory -uname -
> s". But the daemon actually runs and tries to create a new SSL key.
> But it fails with the following error messages.
>
> err: Could not request certificate: Could not write C:/puppet/conf/ssl/
> private_keys/testing.pem to privatekeydir: Could not find a default
> provider for user
> Exiting: failed to retrieve certificate and waitforcert is disabled.
>
> I'm guess its gotta do something with path? Anyone got any ideas?

Any updates on this issue? Just set up puppet on a test box with a
Windows 2003 R2 32 Bits and I get the same error.

Kind regards, Thomas

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

Reply via email to