OK, I''m a total noob to puppet, so please forgive any stupid
mistakes. I''m trying to get a test setup working to evaluate it as a
replacement for radmind. I played with it a bit earlier in the
summer, but got busy with other project, and I''m just now getting back
to it. I had a working setup then, but since I''ve upgraded to 0.24.5
and Facter 1.4.1 I''m not able to get anything working. When I try to
launch puppetmsterd I get "Got 3 failure(s) while initializing: Failed
to retrieve current state of resource: Did not get id; Failed to
retrieve current state of resource: Did not get id; Failed to retrieve
current state of resource: Did not get id". This is running on a G4
Xserv with OS X Server 10.5. Ruby is up to date. I installed Puppet
from the packages here: http://explanatorygap.net/puppetfacter/.
I''ve also tried it from a Power Mac running OS X 10.4, and I get this
error:
/usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:166:in `handle'':
Certificate names must be lower case; see #1168 (ArgumentError)
from /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:166:in
`handle''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
357:in `parse''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
350:in `each_source''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
918:in `each''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
918:in `each_source''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
350:in `parse''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
349:in `each''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:
349:in `parse''
from /usr/lib/ruby/site_ruby/1.8/puppet.rb:177:in
`parse_config''
from /usr/bin/puppetmasterd:165
Something is not working. Is it me or this version of Puppet? I''ve
tried googling these errors ad-nauseum with no results.
ANY suggestions would be helpful.
Best!
Daniel Shown
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Completely remove all traces of puppet and reinstall. Probably some cruft from older versions is sticking around and messing things up. Also, use the canonical source http://reductivelabs.com not some third-party. --Paul On Thu, Aug 28, 2008 at 9:23 AM, Daniel Shown <daniel.shown@gmail.com> wrote:> > OK, I''m a total noob to puppet, so please forgive any stupid > mistakes. I''m trying to get a test setup working to evaluate it as a > replacement for radmind. I played with it a bit earlier in the > summer, but got busy with other project, and I''m just now getting back > to it. I had a working setup then, but since I''ve upgraded to 0.24.5 > and Facter 1.4.1 I''m not able to get anything working. When I try to > launch puppetmsterd I get "Got 3 failure(s) while initializing: Failed > to retrieve current state of resource: Did not get id; Failed to > retrieve current state of resource: Did not get id; Failed to retrieve > current state of resource: Did not get id". This is running on a G4 > Xserv with OS X Server 10.5. Ruby is up to date. I installed Puppet > from the packages here: http://explanatorygap.net/puppetfacter/. > > I''ve also tried it from a Power Mac running OS X 10.4, and I get this > error: > > /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:166:in `handle'': > Certificate names must be lower case; see #1168 (ArgumentError) > from /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb:166:in > `handle'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 357:in `parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 350:in `each_source'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 918:in `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 918:in `each_source'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 350:in `parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 349:in `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb: > 349:in `parse'' > from /usr/lib/ruby/site_ruby/1.8/puppet.rb:177:in > `parse_config'' > from /usr/bin/puppetmasterd:165 > > Something is not working. Is it me or this version of Puppet? I''ve > tried googling these errors ad-nauseum with no results. > > ANY suggestions would be helpful. > > Best! > Daniel Shown > > > >--~--~---------~--~----~------------~-------~--~----~ 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 Aug 29, 6:07 am, "Paul Lathrop" <p...@tertiusfamily.net> wrote:> Completely remove all traces of puppet and reinstall. Probably some > cruft from older versions is sticking around and messing things up. > Also, use the canonical sourcehttp://reductivelabs.comnot some > third-party. >That''s not some third-party, that is who reductivelabs says to download OSX puppet packages from. I found this thread cause I am getting the same bug. OSX client, linux puppetmaster. Successfully serving dozens of CentOS and Ubuntu boxes, but OSX chokes on file{} definitions. =( --~--~---------~--~----~------------~-------~--~----~ 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 Tue, Oct 14, 2008 at 10:49 PM, Deimos <barry.robison@gmail.com> wrote:> > On Aug 29, 6:07 am, "Paul Lathrop" <p...@tertiusfamily.net> wrote: >> Completely remove all traces of puppet and reinstall. Probably some >> cruft from older versions is sticking around and messing things up. >> Also, use the canonical sourcehttp://reductivelabs.comnot some >> third-party. >> > > That''s not some third-party, that is who reductivelabs says to > download OSX puppet packages from. I found this thread cause I am > getting the same bug. OSX client, linux puppetmaster. Successfully > serving dozens of CentOS and Ubuntu boxes, but OSX chokes on file{} > definitions. =(That would be me. :) I''m about to rebuild those packages as I''ve changed the preflight script as I''d just come across this problem and I made the preflight more selective about which cruft it removes. You should be able to resolve this by doing: rm -Rf "/usr/lib/ruby/site_ruby/1.8/puppet*" rm -Rf "/usr/lib/ruby/site_ruby/1.8/facter*" and reinstalling the packages. I''m updating them now. -- Nigel Kersten Systems Administrator Tech Lead - MacOps --~--~---------~--~----~------------~-------~--~----~ 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 should also add this has been committed upstream. http://projects.reductivelabs.com/issues/show/1649 If you''re connected to a large directory service with OS X, you''re going to want to grab something newer than puppet 0.24.5, as a pathological performance problem was fixed upstream after this that caused user/group lookups to take way too long. Note you can create your own packages from puppet git repos now using the createpackage script in conf/osx/createpackage.sh Packages have been updated and tested. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Yes. Thanks a lot for the update, working nicely now. I''ve created my own pkg''s with createpackage.sh from the 0.24.6rc1 tarball and am testing that. On Oct 16, 1:11 am, "Nigel Kersten" <nig...@google.com> wrote:> I should also add this has been committed upstream. > > http://projects.reductivelabs.com/issues/show/1649 > > If you''re connected to a large directory service with OS X, you''re > going to want to grab something newer than puppet 0.24.5, as a > pathological performance problem was fixed upstream after this that > caused user/group lookups to take way too long. > > Note you can create your own packages from puppet git repos now using > the createpackage script in conf/osx/createpackage.sh > > Packages have been updated and tested.--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---