Hi. I know that puppet for windows is in its basic stages but I''ve been screwing around with it. I can get facter working. However one error that it spits out is that: "Could not retrieve puppetversion: Cannot determine basic system flavour." When I try to run puppet, I get an error saying "ruby: No such file or directory -- bin/puppetd (LoadError)" Was wondering if anyone here has succeeded in getting puppet installed on Windows? I''ve been following this document: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows. Thanks! -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Oct 26, 2010, at 8:51 PM, Kikanny wrote:> Hi. I know that puppet for windows is in its basic stages but I''ve > been screwing around with it. I can get facter working. However one > error that it spits out is that: "Could not retrieve puppetversion: > Cannot determine basic system flavour." > > When I try to run puppet, I get an error saying "ruby: No such file or > directory -- bin/puppetd (LoadError)"This sounds to me like a ruby GEMPATH issue. Try to run puppet using the ruby interpreter directly. ruby -I/path/to/dir-with-puppet.rb/ puppet <puppet options> If this works you should set the GEMPATH env variable.> Was wondering if anyone here has succeeded in getting puppet installed > on Windows? I''ve been following this document: > http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows. Thanks!I don''t know but would like to read about this, too. All the best, Sandor Szücs -- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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 in http://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? On Oct 28, 6:41 am, Sandor Szuecs <sandor.szu...@fu-berlin.de> wrote:> On Oct 26, 2010, at 8:51 PM, Kikanny wrote: > > > Hi. I know that puppet for windows is in its basic stages but I''ve > > been screwing around with it. I can get facter working. However one > > error that it spits out is that: "Could not retrieve puppetversion: > > Cannot determine basic system flavour." > > > When I try to run puppet, I get an error saying "ruby: No such file or > > directory -- bin/puppetd (LoadError)" > > This sounds to me like a ruby GEMPATH issue. > Try to run puppet using the ruby interpreter directly. > ruby -I/path/to/dir-with-puppet.rb/ puppet <puppet options> > > If this works you should set the GEMPATH env variable. > > > Was wondering if anyone here has succeeded in getting puppet installed > > on Windows? I''ve been following this document: > >http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows. Thanks! > > I don''t know but would like to read about this, too. > > All the best, Sandor Szücs > ---- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
lists@truthisfreedom.org.uk
2010-Oct-28 14:58 UTC
Re: [Puppet Users] Re: Puppet on Windows
Quoting Kikanny <kikanny@gmail.com>:> 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 could be wrong, but shouldn''t those slashes be back and not forward for Windows? i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem M. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hmm...that is what puppet reports when it is run. I think its because ruby accepts only forward slashes and since puppet is based on ruby....could make sense. Could be wrong though. On Oct 28, 10:58 am, li...@truthisfreedom.org.uk wrote:> Quoting Kikanny <kika...@gmail.com>: > > > 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 could be wrong, but shouldn''t those slashes be back and not forward > for Windows? > > i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem > > M.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Windows actually doesn''t care about the direction of slashes in the path from programming languages. -Trevor On Thu, Oct 28, 2010 at 9:21 AM, Kikanny <kikanny@gmail.com> wrote:> Hmm...that is what puppet reports when it is run. I think its because > ruby accepts only forward slashes and since puppet is based on > ruby....could make sense. Could be wrong though. > > On Oct 28, 10:58 am, li...@truthisfreedom.org.uk wrote: >> Quoting Kikanny <kika...@gmail.com>: >> >> > 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 could be wrong, but shouldn''t those slashes be back and not forward >> for Windows? >> >> i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem >> >> M. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''m thinking of giving up....it looks like puppet for windows still tries to use the linux directory structure? Because there is a statement that says: debug: Puppet::Type::User::ProviderDirectoryService: file /usr/bin/ dsc1 does not exist I don''t know..I''m clueless. If anyone does get it working, please do share! :) On Oct 28, 11:21 am, Kikanny <kika...@gmail.com> wrote:> Hmm...that is what puppet reports when it is run. I think its because > ruby accepts only forward slashes and since puppet is based on > ruby....could make sense. Could be wrong though. > > On Oct 28, 10:58 am, li...@truthisfreedom.org.uk wrote: > > > Quoting Kikanny <kika...@gmail.com>: > > > > 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 could be wrong, but shouldn''t those slashes be back and not forward > > for Windows? > > > i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem > > > M. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 10/28/2010 05:47 PM, Kikanny wrote:> I''m thinking of giving up....it looks like puppet for windows still > tries to use the linux directory structure? Because there is a > statement that says: > > debug: Puppet::Type::User::ProviderDirectoryService: file /usr/bin/ > dsc1 does not exist > > I don''t know..I''m clueless. If anyone does get it working, please do > share! :)No worries - puppet is informing you that it cannot use a specific provider for the "user" resource type. This won''t keep you from running. Regards, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
x64? On Oct 28, 8:37 am, Trevor Whitlock <twhitl...@gmail.com> wrote:> Windows actually doesn''t care about the direction of slashes in the > path from programming languages. > > -Trevor > > > > > > > > On Thu, Oct 28, 2010 at 9:21 AM, Kikanny <kika...@gmail.com> wrote: > > Hmm...that is what puppet reports when it is run. I think its because > > ruby accepts only forward slashes and since puppet is based on > > ruby....could make sense. Could be wrong though. > > > On Oct 28, 10:58 am, li...@truthisfreedom.org.uk wrote: > >> Quoting Kikanny <kika...@gmail.com>: > > >> > 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 could be wrong, but shouldn''t those slashes be back and not forward > >> for Windows? > > >> i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem > > >> M. > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I actually haven''t tested that on x64. I just double checked in java and that is correct. All file accesses work with forward slashes. -Trevor On Fri, Oct 29, 2010 at 10:27 AM, barry.allard <barry.allard@gmail.com> wrote:> x64? > > On Oct 28, 8:37 am, Trevor Whitlock <twhitl...@gmail.com> wrote: >> Windows actually doesn''t care about the direction of slashes in the >> path from programming languages. >> >> -Trevor >> >> >> >> >> >> >> >> On Thu, Oct 28, 2010 at 9:21 AM, Kikanny <kika...@gmail.com> wrote: >> > Hmm...that is what puppet reports when it is run. I think its because >> > ruby accepts only forward slashes and since puppet is based on >> > ruby....could make sense. Could be wrong though. >> >> > On Oct 28, 10:58 am, li...@truthisfreedom.org.uk wrote: >> >> Quoting Kikanny <kika...@gmail.com>: >> >> >> > 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 could be wrong, but shouldn''t those slashes be back and not forward >> >> for Windows? >> >> >> i.e. the path should be c:\puppet\conf\ssl\private_keys\testing.pem >> >> >> M. >> >> > -- >> > You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en. > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, Nov 25, 2010 at 5:48 AM, thbe <thomas.bendler@gmail.com> wrote:> 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.We''ll update the page for the alpha Windows support, but testing indicates we only support local manifests application on Windows right now, and we only have a provider for managing files so far.> > 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-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- Nigel Kersten - Puppet Labs - http://www.puppetlabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hi Nigel, 2010/11/25 Nigel Kersten <nigel@puppetlabs.com>> On Thu, Nov 25, 2010 at 5:48 AM, thbe <thomas.bendler@gmail.com> wrote: > [...] > > 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. > We''ll update the page for the alpha Windows support, but testing > indicates we only support local manifests application on Windows right > now, and we only have a provider for managing files so far. >thanks for the update, managing some files and getting machine facts via facter would be completely sufficient for me in the first shot (facter already does what I expect). Do you know if MCollective will be running on Windows as well? With this combination I could manage my own script directory to start and stop applications as well as start and stop Windows itself. Kind regards, Thomas -- thomas bendler (systemadministration/network/SAP) cimt consulting ag fon: +49 (163) 6081 302 burchardstrasse 17 fax: +49 (40) 5 33 02-22 20095 hamburg http://www.cimt.de/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 26 November 2010 09:21, Thomas Bendler <thomas.bendler@cimt.de> wrote:> Hi Nigel, > > 2010/11/25 Nigel Kersten <nigel@puppetlabs.com> >> >> On Thu, Nov 25, 2010 at 5:48 AM, thbe <thomas.bendler@gmail.com> wrote: >> [...] >> > 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. >> We''ll update the page for the alpha Windows support, but testing >> indicates we only support local manifests application on Windows right >> now, and we only have a provider for managing files so far. > > thanks for the update, managing some files and getting machine facts via > facter would be completely sufficient for me in the first shot (facter > already does what I expect). Do you know if MCollective will be running on > Windows as well? With this combination I could manage my own script > directory to start and stop applications as well as start and stop Windows > itself.Joel did do a users/group provider which may be quite dated and need some porting - if you are happy to test/develop: https://github.com/finalprefix/puppet/tree/win Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
2010/11/26 Paul Nasrat <pnasrat@gmail.com>> [...] > Joel did do a users/group provider which may be quite dated and need > some porting - if you are happy to test/develop: > https://github.com/finalprefix/puppet/tree/winWhat is the procedure to use this version? Download the ZIP and run install.rb or must be something taken into account before using it? 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 26 November 2010 11:12, Thomas Bendler <thomas.bendler@gmail.com> wrote:> 2010/11/26 Paul Nasrat <pnasrat@gmail.com> >> >> [...] >> Joel did do a users/group provider which may be quite dated and need >> some porting - if you are happy to test/develop: >> https://github.com/finalprefix/puppet/tree/win > > What is the procedure to use this version? Download the ZIP and run > install.rb or must be something taken into account before using it?If you are not comfortable with git, the puppet code base and patching I would advise against trying to use this. Which based on your question you probably are. Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Nov 26, 2010 at 3:23 AM, Paul Nasrat <pnasrat@gmail.com> wrote:> On 26 November 2010 11:12, Thomas Bendler <thomas.bendler@gmail.com> wrote: >> 2010/11/26 Paul Nasrat <pnasrat@gmail.com> >>> >>> [...] >>> Joel did do a users/group provider which may be quite dated and need >>> some porting - if you are happy to test/develop: >>> https://github.com/finalprefix/puppet/tree/win >> >> What is the procedure to use this version? Download the ZIP and run >> install.rb or must be something taken into account before using it? > > If you are not comfortable with git, the puppet code base and patching > I would advise against trying to use this. Which based on your > question you probably are. >I wasn''t aware of this provider at all. Are there more repositories around like this Paul? I''ll investigate the provider today. -- Nigel Kersten - Puppet Labs - http://www.puppetlabs.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, Jun 23, 2011 at 10:07 AM, Arm Adam <arm.adam.groups@gmail.com> wrote:> Hi all, > > I realize this thread is a little old but hoping someone can tell me > if much progress has been made on getting Puppet running on Windows. > I just tried to set up an agent according to the directions at > http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows on > Windows Server 2008 x86, and got the bug (http:// > projects.puppetlabs.com/issues/6693) exactly as described with version > 2.7.1. Can someone tell me what the timeframe is for a release that > supports Windows puppet agents connecting to an existing Puppetmaster?+ puppet-users as I think this was accidentally a private reply. We''re aiming to deliver this in Q3 of this year, with work starting next month. We''ve had a few meetings in person talking about the required support, and that''s going to be captured in a public ticket people can watch very soon, I apologize for the lack of transparency here. -- Nigel Kersten Product, Puppet Labs @nigelkersten -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.