Hi Allister, I am in no way a puppet expert, but I do have puppetmaster running on MacOS 10.5.6 server and puppet on MacOS 10.5.6 clients.
I am using Nigels packages from https://sites.google.com/a/explanatorygap.net/puppet/. I am using the facter-1.5.2 and puppet-0.24.7 packages. I have a very basic setup see http://groups.google.com/group/puppet-users/browse_thread/thread/4644f7c66f899b80/b924ab9210477029 This is all on a clean install with latest Apple updates. I believe that puppet doesn't use specific a puppet user on the mac and just runs as root. I hope that helps, Marcus. On Wed, Apr 8, 2009 at 7:54 AM, Allister Banks <[email protected]> wrote: > > Hey all, > I have recorded my steps towards getting puppet functional > through one of the four different methods that I can think of, which > are: > 1.Source(copying and insatlling to the recommended unix FSH > directory, /usr/local/src) > 2.pkg hosted at explanatorygap > 3.MacPorts > 4.RubyGems > I haven't cleanly tested the last two, but here's where I am with the > first two: > 1. I can't seem to install either facter or puppet properly, this is > with the most recent ruby, 1.9.1. Here's where I left off with > facter: > sudo ruby ./install.rb > Password: > ./install.rb:38:in `require': no such file to load -- ftools > (LoadError) > from ./install.rb:38:in `<main>' > and then for puppet, from the customizations i thought were right: > $ PATH=$PATH:/usr/local/src/facter/bin:/usr/local/src/puppet/bin > $ RUBYLIB=/usr/local/src/facter/lib:/usr/local/src/puppet/lib > $ export PATH RUBYLIB > > and then just the command and then the error s at the end: > $ rake --trace > (in /usr/local/src/puppet/test) > ** Invoke default (first_time) > ** Invoke test (first_time) > ** Execute test > ...... > .... > /usr/local/src/puppet/test/lib/puppettest.rb:20:in `require': no such > file to load -- mocha (LoadError) > from /usr/local/src/puppet/test/lib/puppettest.rb:20:in `<top > (required)>' > from /usr/local/src/puppet/test/util/utiltest.rb:3:in `require' > from /usr/local/src/puppet/test/util/utiltest.rb:3:in `<top (required) >>' > from /usr/local/lib/ruby/1.9.1/rake/rake_test_loader.rb:5:in `load' > from /usr/local/lib/ruby/1.9.1/rake/rake_test_loader.rb:5:in `block > in <main>' > from /usr/local/lib/ruby/1.9.1/rake/rake_test_loader.rb:5:in `each' > from /usr/local/lib/ruby/1.9.1/rake/rake_test_loader.rb:5:in `<main>' > rake aborted! > Command failed with status (1): [/usr/local/bin/ruby -Ilib:lib:../lib > "/usr...] > /usr/local/lib/ruby/1.9.1/rake.rb:968:in `block in sh' > /usr/local/lib/ruby/1.9.1/rake.rb:981:in `call' > /usr/local/lib/ruby/1.9.1/rake.rb:981:in `sh' > /usr/local/lib/ruby/1.9.1/rake.rb:1065:in `sh' > /usr/local/lib/ruby/1.9.1/rake.rb:1000:in `ruby' > /usr/local/lib/ruby/1.9.1/rake.rb:1065:in `ruby' > /usr/local/lib/ruby/1.9.1/rake/testtask.rb:117:in `block (2 levels) in > define' > /usr/local/lib/ruby/1.9.1/rake.rb:1083:in `verbose' > /usr/local/lib/ruby/1.9.1/rake/testtask.rb:102:in `block in define' > /usr/local/lib/ruby/1.9.1/rake.rb:613:in `call' > /usr/local/lib/ruby/1.9.1/rake.rb:613:in `block in execute' > /usr/local/lib/ruby/1.9.1/rake.rb:608:in `each' > /usr/local/lib/ruby/1.9.1/rake.rb:608:in `execute' > /usr/local/lib/ruby/1.9.1/rake.rb:574:in `block in > invoke_with_call_chain' > /usr/local/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize' > /usr/local/lib/ruby/1.9.1/rake.rb:567:in `invoke_with_call_chain' > /usr/local/lib/ruby/1.9.1/rake.rb:584:in `block in > invoke_prerequisites' > /usr/local/lib/ruby/1.9.1/rake.rb:581:in `each' > /usr/local/lib/ruby/1.9.1/rake.rb:581:in `invoke_prerequisites' > /usr/local/lib/ruby/1.9.1/rake.rb:573:in `block in > invoke_with_call_chain' > /usr/local/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize' > /usr/local/lib/ruby/1.9.1/rake.rb:567:in `invoke_with_call_chain' > /usr/local/lib/ruby/1.9.1/rake.rb:560:in `invoke' > /usr/local/lib/ruby/1.9.1/rake.rb:2012:in `invoke_task' > /usr/local/lib/ruby/1.9.1/rake.rb:1990:in `block (2 levels) in > top_level' > /usr/local/lib/ruby/1.9.1/rake.rb:1990:in `each' > /usr/local/lib/ruby/1.9.1/rake.rb:1990:in `block in top_level' > /usr/local/lib/ruby/1.9.1/rake.rb:2029:in > `standard_exception_handling' > /usr/local/lib/ruby/1.9.1/rake.rb:1984:in `top_level' > /usr/local/lib/ruby/1.9.1/rake.rb:1963:in `block in run' > /usr/local/lib/ruby/1.9.1/rake.rb:2029:in > `standard_exception_handling' > /usr/local/lib/ruby/1.9.1/rake.rb:1960:in `run' > /usr/local/bin/rake:31:in `<main>' > > And then I moved on to the pkg install, creating the necessary > directories in /etc as root, since there was no puppet user, and > moving the basic "simple install recipe" sudo.pp and sites.pp files > into their proper directories. > > expGapPkgs:manifests stringer$ sudo puppetmasterd --mkusers > Got 1 failure(s) while initializing: Failed to retrieve current state > of resource: Could not determine OS X version > > expGapPkgs:manifests stringer$ id puppetd > id: puppetd: no such user > > expGapPkgs:manifests stringer$ sudo puppetd --test > info: Creating a new certificate request for expgappkgs.local > info: Creating a new SSL key at /etc/puppet/ssl/private_keys/ > expgappkgs.local.pem > err: Could not find server : getaddrinfo: nodename nor servname > provided, or not known > err: Could not request certificate: Certificate retrieval failed: > Could not find server puppet > > I then moved on to try to run puppetmasterd with the -v and -d flags: > > expGapPkgs:manifests stringer$ sudo puppetmasterd -v -d --no-daemonize > info: Starting server for Puppet version 0.24.8 > debug: Creating interpreter > debug: Creating default schedules > debug: Failed to load library 'ldap' for feature 'ldap' > debug: Failed to load library 'shadow' for feature 'libshadow' > debug: /Settings[top]/Settings[main]/File[/var/puppet/lib]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[metrics]/File[/var/puppet/rrd]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[main]/File[/var/puppet/state]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[main]/File[/var/puppet/log]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[main]/File[/var/puppet/run]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[reporting]/File[/var/puppet/reports]: > Autorequiring File[/var/puppet] > debug: /Settings[top]/Settings[main]/File[/etc/puppet/ssl]: > Autorequiring File[/etc/puppet] > err: /Settings[top]/Settings[main]/File[/var/puppet/log]: Failed to > retrieve current state of resource: Could not find user puppet > debug: /Settings[top]/Settings[reporting]/File[/var/puppet/reports]: > File does not exist > debug: /Settings[top]/Settings[reporting]/File[/var/puppet/reports]: > Changing ensure > debug: /Settings[top]/Settings[reporting]/File[/var/puppet/reports]: 1 > change(s) > err: /Settings[top]/Settings[reporting]/File[/var/puppet/reports]/ > ensure: change from absent to directory failed: Could not set > directory on ensure: Could not find user puppet > debug: /Settings[top]/Settings[metrics]/File[/var/puppet/rrd]: File > does not exist > debug: /Settings[top]/Settings[metrics]/File[/var/puppet/rrd]: > Changing ensure > debug: /Settings[top]/Settings[metrics]/File[/var/puppet/rrd]: 1 change > (s) > err: /Settings[top]/Settings[metrics]/File[/var/puppet/rrd]/ensure: > change from absent to directory failed: Could not set directory on > ensure: Could not find user puppet > debug: Finishing transaction 13213040 with 2 changes > Got 3 failure(s) while initializing: Failed to retrieve current state > of resource: Could not find user puppet; change from absent to > directory failed: Could not set directory on ensure: Could not find > user puppet; change from absent to directory failed: Could not set > directory on ensure: Could not find user puppet > > > Any input for simple basic next steps would be greatly appreciated, I > am making these assumptions about each failure: > from source, I may not be setting the PATH correctly. > from pkg, I need to create the puppet user, chown the /etc/puppet > directory, > and for both, at some point, add the puppet.conf file to the /etc/ > puppet/ directory, and do some kind of launchdaemon to start at boot. > > Thanks in advance for any and all suggestions, > > Allister Banks > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
