On Tue, Jul 13, 2010 at 6:19 PM, Patrick Mohr <kc7...@gmail.com> wrote:
> You might want to take a look at
> http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows
>
> It looks like some people have gotten farther than you.
Thanks for the link! Again in the hopes of sharing my "user
experience" with the community, I'm noting my progress in getting
Puppet running on a 64-bit Windows 7 desktop machine (my target
platform is Server 2008 and Server 2008 R2, so I don't think my choice
of guinea pig platforms is *entirely* insane... ).
I started over with the instructions at the wiki (and checked the URL
referenced there), but I still ended up getting the error about not
being able to determine the "basic system flavour."
I think I may have introduced a couple of issues by installing the
gems and the (newer) tarballs side-by-side. Gem Puppet runs up to the
point where it complains about not being able to import the syslog
module (which doesn't exist on Windows). I assume this is a stale
dependency that's been evolved out of the new version. Sure enough,
after ripping out the gems I got back to the flavour issue.
After further investigation, I cleared this up by adding a couple more gems via:
gem install win32-security
gem install win32-process
gem install win32-dir
gem install sys-admin
Now I am seeing the following error:
>ruby puppet apply
The system cannot find the path specified.
C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:78:in
`initialize': uninitialized constant Fcntl::F_SETFD (NameError)
from
C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:31:in
`new'
from
C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:31:in
`default'
from
C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:35:in
`current'
from
C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb:279:in
`initialize'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:560:in
`new'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:560:in
`set_filetimeout_timer'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:311:in
`parse'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/application.rb:299:in
`run'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/application.rb:398:in
`exit_on_fail'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/application.rb:299:in
`run'
from C:/Ruby186/lib/ruby/site_ruby/1.8/puppet/util/command_line.rb:55:in
`execute'
from puppet:4
A little digging shows that I needed to install the MinGW dev kit:
http://files.rubyforge.vm.bytemark.co.uk/rubyinstaller/devkit-3.4.5r3-20091110.7z
After installing it according to the RubyInstaller docs, I was able to
build my own native extensions to the gems listed above by adding the
"--platform win32" switch. But now I'm getting a DLL error requiring
a Ruby 1.8 DLL ... it's ignorable, but things aren't working right.
Next I find I'm hung up inside Puppet (and Facter, for that matter,
which exits with the same error while importing the puppetversion
fact!), and this one is just Ruby enough to stump me:
>ruby puppet doc
C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/application/kick.rb:
C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/application/kick.rb:107:
Invalid next (SyntaxError)
As a last-ditch effort, I went back to the Puppet-team-recommended
1.8.6 installer, which is now considered "old" but there appear to be
some gem support issues on Windows with the newer distributions of
Ruby.
I'm going to leave things here for now on this project. If anyone
with experience in these matters has gotten Puppet to run on a fairly
recent Windows platform, I'd love to hear how you did it ... :)
--
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.
