Hi, I was wondering if anyone has puppet running on OSX 10.3. I installed ruby 1.8.2 into /usr/local and was able to install puppet 0.24.4 and factor-1.3.8 via ruby gems. My problem is that when I try to run puppet I get: bash-2.05b# /usr/local/bin/puppetd --verbose --onetime --no-daemonize err: /Settings[top]/Settings[main]/File[/var/puppet/run]/group: change from puppet to failed: too few arguments. /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ settings.rb:677:in `use'': Could not configure for running; got 1 failure(s) (RuntimeError) from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ settings.rb:675:in `apply'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ settings.rb:675:in `use'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ settings.rb:655:in `synchronize'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ settings.rb:655:in `use'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/ network/client/master.rb:206:in `initialize'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd: 322:in `new'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd:322 from /usr/local/bin/puppetd:16:in `load'' from /usr/local/bin/puppetd:16 Thanks for your help. cheers, ski BTW: I have it working fine on 10.4 and 10.5. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Have you specified a user and group in the puppet config? If so, have you tried specifying them with uid rather than name? On Wed, May 28, 2008 at 2:13 PM, Ski <kacoroski@gmail.com> wrote:> > Hi, > > I was wondering if anyone has puppet running on OSX 10.3. I installed > ruby 1.8.2 into /usr/local and was able to install puppet 0.24.4 and > factor-1.3.8 via ruby gems. My problem is that when I try to run > puppet I get: > > bash-2.05b# /usr/local/bin/puppetd --verbose --onetime --no-daemonize > err: /Settings[top]/Settings[main]/File[/var/puppet/run]/group: change > from puppet to failed: too few arguments. > /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ > settings.rb:677:in `use'': Could not configure for running; got 1 > failure(s) (RuntimeError) > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ > settings.rb:675:in `apply'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ > settings.rb:675:in `use'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ > settings.rb:655:in `synchronize'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ > settings.rb:655:in `use'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/ > network/client/master.rb:206:in `initialize'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd: > 322:in `new'' > from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd:322 > from /usr/local/bin/puppetd:16:in `load'' > from /usr/local/bin/puppetd:16 > > Thanks for your help. > > cheers, > > ski > > BTW: I have it working fine on 10.4 and 10.5. > > >-- Nigel Kersten Systems Administrator 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 -~----------~----~----~----~------~----~------~--~---
Hi, I tried setting the user and group in puppetd.conf to be the names and then tried the uid and gid numbers. No luck. I have verified the puppet user and group exists via dscl. It looks like to me that there is a bug where it is missing an argument. Appreciate any help as I need to get this going soon on the 10.3 Macs. cheers, ski Nigel Kersten wrote:> Have you specified a user and group in the puppet config? If so, have > you tried specifying them with uid rather than name? > > > On Wed, May 28, 2008 at 2:13 PM, Ski <kacoroski@gmail.com> wrote: >> Hi, >> >> I was wondering if anyone has puppet running on OSX 10.3. I installed >> ruby 1.8.2 into /usr/local and was able to install puppet 0.24.4 and >> factor-1.3.8 via ruby gems. My problem is that when I try to run >> puppet I get: >> >> bash-2.05b# /usr/local/bin/puppetd --verbose --onetime --no-daemonize >> err: /Settings[top]/Settings[main]/File[/var/puppet/run]/group: change >> from puppet to failed: too few arguments. >> /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ >> settings.rb:677:in `use'': Could not configure for running; got 1 >> failure(s) (RuntimeError) >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ >> settings.rb:675:in `apply'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ >> settings.rb:675:in `use'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ >> settings.rb:655:in `synchronize'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/ >> settings.rb:655:in `use'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/ >> network/client/master.rb:206:in `initialize'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd: >> 322:in `new'' >> from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/bin/puppetd:322 >> from /usr/local/bin/puppetd:16:in `load'' >> from /usr/local/bin/puppetd:16 >> >> Thanks for your help. >> >> cheers, >> >> ski >> >> BTW: I have it working fine on 10.4 and 10.5. > > >--~--~---------~--~----~------------~-------~--~----~ 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 May 30, 2008, at 11:34 AM, Ski Kacoroski wrote:> Hi, > > I tried setting the user and group in puppetd.conf to be the names and > then tried the uid and gid numbers. No luck. I have verified the > puppet user and group exists via dscl. It looks like to me that there > is a bug where it is missing an argument. Appreciate any help as I > need > to get this going soon on the 10.3 Macs.It looks kind of like Puppet is somehow not able to look up the user''s UID or something. I''d do some experimentation running stand-alone Puppet, trying to chown files and create users with either the netinfo or dscl providers and see where that gets you. Jeff McCune has done most of the development for those two providers and he''s not around much any more, but I''ll do what I can to try to help. -- Dawkins''s Law of Adversarial Debate: When two incompatible beliefs are advocated with equal intensity, the truth does not lie half way between them. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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 -~----------~----~----~----~------~----~------~--~---
Luke,
Using the debugger, I can see that for some reason on this one resource,
the group attribute @should is blank where in the owner it is set. This
is the problem, just not yet sure how to fix it. It is able to look up
the uid and gid numbers with no problem.
(rdb:1) p self.display
File[/var/puppet/run]nil
(rdb:1) v l
changes => nil
currentvalues => {Property(''group'', @should =
'''')=>108,
Property(''mode'', @should = ''1023'')=>1023,
Property(''owner'', @should =
''106'')=>106, Property(''ensure'', @should =
''directory'')=>:directory}
noop => nil
p => nil
This is in:
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/metatype/evaluation.rb
cheers,
ski
Luke Kanies wrote:> On May 30, 2008, at 11:34 AM, Ski Kacoroski wrote:
>
>> Hi,
>>
>> I tried setting the user and group in puppetd.conf to be the names and
>> then tried the uid and gid numbers. No luck. I have verified the
>> puppet user and group exists via dscl. It looks like to me that there
>> is a bug where it is missing an argument. Appreciate any help as I
>> need
>> to get this going soon on the 10.3 Macs.
>
>
> It looks kind of like Puppet is somehow not able to look up the
user''s
> UID or something.
>
> I''d do some experimentation running stand-alone Puppet, trying to
> chown files and create users with either the netinfo or dscl providers
> and see where that gets you.
>
> Jeff McCune has done most of the development for those two providers
> and he''s not around much any more, but I''ll do what I can
to try to
> help.
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
Luke,
I did some more digging and found that everything is good until it tries
to set @should (not sure how this is set yet). Using IRB I get:
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/parameter.rb:116:
if self.shadow
(rdb:1) l
[111, 120] in
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/parameter.rb
111 rescue => detail
112 raise Puppet::DevError, "Munging failed for
value %s in class %s: %s" %
113 [args.inspect, self.name, detail],
detail.backtrace
114 end
115
=> 116 if self.shadow
117 self.shadow.munge(*args)
118 end
119 ret
120 end
(rdb:1) self.shadow
nil
(rdb:1) self.retrieve
108
got the right value here
(rdb:1) n
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/parameter.rb:116:
if self.shadow
(rdb:1) n
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/parameter.rb:119:
ret
(rdb:1) n
/usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/metatype/attributes.rb:516:
nil
(rdb:1) self.retrieve
{Property(''ensure'', @should =
''directory'')=>:directory,
Property(''group'', @should = '''')=>108,
Property(''owner'', @should =
''106'')=>106}
but @should is not set right here. Note that the ''owner'' is
set
correctly. I still do not understand exactly how self.newattr(name,
:value => value) creates the property, but I could see nothing that
would cause a problem. I am using ruby 1.8.2 on the 10.3 macs where it
doesn''t work and ruby 1.8.6 on the 10.4 and 10.5 macs where it does
work.
cheers,
ski
Luke Kanies wrote:> On May 30, 2008, at 11:34 AM, Ski Kacoroski wrote:
>
>> Hi,
>>
>> I tried setting the user and group in puppetd.conf to be the names and
>> then tried the uid and gid numbers. No luck. I have verified the
>> puppet user and group exists via dscl. It looks like to me that there
>> is a bug where it is missing an argument. Appreciate any help as I
>> need
>> to get this going soon on the 10.3 Macs.
>
>
> It looks kind of like Puppet is somehow not able to look up the
user''s
> UID or something.
>
> I''d do some experimentation running stand-alone Puppet, trying to
> chown files and create users with either the netinfo or dscl providers
> and see where that gets you.
>
> Jeff McCune has done most of the development for those two providers
> and he''s not around much any more, but I''ll do what I can
to try to
> help.
>
--~--~---------~--~----~------------~-------~--~----~
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 May 30, 2008, at 5:10 PM, Ski Kacoroski wrote:> I still do not understand exactly how self.newattr(name, > :value => value) creates the property, but I could see nothing that > would cause a problem.I doubt that''s the problem; at the least, that''s unlikely to be os- specific, so it''s unlikely to be the source of the problem.> I am using ruby 1.8.2 on the 10.3 macs where it > doesn''t work and ruby 1.8.6 on the 10.4 and 10.5 macs where it does > work.Does 10.3 use NetInfo or dscl? What is Puppet using? Try the Util.uid/gid methods to see if they''re able to actually retrieve a given user''s uid or gid. I bet that''s the actual problem -- I think the resource types convert early-on, and they might be getting nil back instead of a real value. -- Sabbagh''s Second Law: The biggest problem with communication is the illusion that it has occurred. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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 Fri, May 30, 2008 at 3:15 PM, Luke Kanies <luke@madstop.com> wrote:> Does 10.3 use NetInfo or dscl? What is Puppet using?So 10.3 uses NetInfo as the backing store for local DirectoryService data, whereas 10.5 uses "DSLocal" which is effectively just standard plists. the "dscl" command the directoryservice provider uses talks to DirectoryServices, and thus doesn''t care about the underlying backing store implementation. It could work under 10.3, but I doubt Jeff tested it much, and I know I''ve never thought about getting it to run in 10.3 I just poked around a bit, and I don''t even have a Mac here capable of running 10.3.... so I can''t help out with that sorry.> > Try the Util.uid/gid methods to see if they''re able to actually > retrieve a given user''s uid or gid. I bet that''s the actual problem > -- I think the resource types convert early-on, and they might be > getting nil back instead of a real value. > > -- > Sabbagh''s Second Law: > The biggest problem with communication is the illusion that it > has occurred. > --------------------------------------------------------------------- > Luke Kanies | http://reductivelabs.com | http://madstop.com > > > > >-- Nigel Kersten Systems Administrator 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 will test this, but am pretty sure it is something else because puppet
does get the uid and uidnumber and was able to get the gid and gid
number as shown by:
(rdb:1) self.retrieve #self is the catalog
{Property(''ensure'', @should =
''directory'')=>:directory,
Property(''group'', @should = '''')=>108,
Property(''owner'', @should =
''106'')=>106}
The only problem is that @should variable for the group is set to
''''
instead of 108 which is the correct gidnumber. 10.3 uses netinfo and I
do see that the netinfo group provider is basically empty compared to
the netinfo user provider (perhaps that is some of the issue).
cheers,
ski
Luke Kanies wrote:> On May 30, 2008, at 5:10 PM, Ski Kacoroski wrote:
>
>> I still do not understand exactly how self.newattr(name,
>> :value => value) creates the property, but I could see nothing that
>> would cause a problem.
>
> I doubt that''s the problem; at the least, that''s unlikely
to be os-
> specific, so it''s unlikely to be the source of the problem.
>
>> I am using ruby 1.8.2 on the 10.3 macs where it
>> doesn''t work and ruby 1.8.6 on the 10.4 and 10.5 macs where it
does
>> work.
>
>
> Does 10.3 use NetInfo or dscl? What is Puppet using?
>
> Try the Util.uid/gid methods to see if they''re able to actually
> retrieve a given user''s uid or gid. I bet that''s the
actual problem
> -- I think the resource types convert early-on, and they might be
> getting nil back instead of a real value.
>
--~--~---------~--~----~------------~-------~--~----~
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 May 30, 2008, at 5:15 PM, Ski Kacoroski wrote:> I will test this, but am pretty sure it is something else because > puppet > does get the uid and uidnumber and was able to get the gid and gid > number as shown by: > > (rdb:1) self.retrieve #self is the catalog > {Property(''ensure'', @should = ''directory'')=>:directory, > Property(''group'', @should = '''')=>108, Property(''owner'', @should > ''106'')=>106} > > The only problem is that @should variable for the group is set to '''' > instead of 108 which is the correct gidnumber. 10.3 uses netinfo > and I > do see that the netinfo group provider is basically empty compared to > the netinfo user provider (perhaps that is some of the issue).The reason the group provider is empty is because it''s 100x easier than the user provider. Groups really only have a name and a gid, while users have a good bit more. I don''t see how the ''should'' value could be empty, there''s definitely something screwy going on. If you just create the resource in Ruby, do you get the same behaviour? E.g.: $ irb > require ''puppet'' > file = Puppet::Type.type(:file).create :path => "/my/file", :group => "mygroup" > file.should(:group) > file.retrieve > file.should(:group) I assume that ''retrieve'' is causing the value to go away, right? -- There is nothing worse than aggressive stupidity. -- Johann Wolfgang von Goethe --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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 -~----------~----~----~----~------~----~------~--~---
Luke, There is something screwy here with the way the puppet gem installed I think. I get: bash-2.05b# irb irb(main):001:0> require ''puppet'' LoadError: No such file to load -- puppet from (irb):1:in `require'' from (irb):1 irb(main):002:0> but I can run puppetd ok: bash-2.05b# puppet --version 0.24.4 puppet is installed in: /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/ I also tried to force it by entering the full path to puppet: bash-2.05b# irb -r /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet.rb /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet.rb:28: warning: already initialized constant PUPPETVERSION irb(main):001:0> file = Puppet::Type.type(:file).create :path => "/tmp/skitest", :group => "puppet" NoMethodError: private method `split'' called for nil:NilClass from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/autoload.rb:139:in `searchpath'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/autoload.rb:130:in `eachdir'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/util/autoload.rb:73:in `load'' from /usr/local/lib/ruby/gems/1.8/gems/puppet-0.24.4/lib/puppet/metatype/manager.rb:119:in `type'' from (irb):1 cheers, ski Luke Kanies wrote:> On May 30, 2008, at 5:15 PM, Ski Kacoroski wrote: > >> I will test this, but am pretty sure it is something else because >> puppet >> does get the uid and uidnumber and was able to get the gid and gid >> number as shown by: >> >> (rdb:1) self.retrieve #self is the catalog >> {Property(''ensure'', @should = ''directory'')=>:directory, >> Property(''group'', @should = '''')=>108, Property(''owner'', @should >> ''106'')=>106} >> >> The only problem is that @should variable for the group is set to '''' >> instead of 108 which is the correct gidnumber. 10.3 uses netinfo >> and I >> do see that the netinfo group provider is basically empty compared to >> the netinfo user provider (perhaps that is some of the issue). > > > The reason the group provider is empty is because it''s 100x easier > than the user provider. Groups really only have a name and a gid, > while users have a good bit more. > > I don''t see how the ''should'' value could be empty, there''s definitely > something screwy going on. If you just create the resource in Ruby, > do you get the same behaviour? E.g.: > > $ irb > > require ''puppet'' > > file = Puppet::Type.type(:file).create :path => "/my/file", :group > => "mygroup" > > file.should(:group) > > file.retrieve > > file.should(:group) > > I assume that ''retrieve'' is causing the value to go away, right? >--~--~---------~--~----~------------~-------~--~----~ 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 Jun 1, 2008, at 7:12 PM, Ski Kacoroski wrote:> Luke, > > There is something screwy here with the way the puppet gem installed I > think. I get: > > bash-2.05b# irb > irb(main):001:0> require ''puppet'' > LoadError: No such file to load -- puppet > from (irb):1:in `require'' > from (irb):1 > irb(main):002:0> > > but I can run puppetd ok: > > bash-2.05b# puppet --version > 0.24.4This is stupid gems. Do "require ''rubygems''" and then require puppet. Stupid gems. :/ -- Love is a snowmobile racing across the tundra and then suddenly it flips over, pinning you underneath. At night, the ice weasels come. --Matt Groening --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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 -~----------~----~----~----~------~----~------~--~---
Luke,
This works fine, but there is no mapping the gidnumber.
ski
bash-2.05b# irb
irb(main):001:0> require ''rubygems''
=> true
irb(main):002:0> require ''puppet''
=> true
irb(main):003:0> file = Puppet::Type.type(:file).create :path =>
"/tmp/ski1", :group => "puppet"
=> #<Puppet::Type::File:0x156160c @syncedchanges=0,
@title="/tmp/ski1",
@evalcount=0, @stat=nil, @parameters={:force=>Parameter(force = false,
@resource = File[/tmp/ski1]), :sourceselect=>Parameter(sourceselect =
first, @resource = File[/tmp/ski1]), :replace=>Parameter(replace = true,
@resource = File[/tmp/ski1]), :ignore=>Parameter(ignore = nil, @resource
= File[/tmp/ski1]), :path=>Parameter(path = /tmp/ski1, @resource =
File[/tmp/ski1]), :loglevel=>Parameter(loglevel = notice, @resource =
File[/tmp/ski1]), :links=>Parameter(links = manage, @resource =
File[/tmp/ski1]), :group=>Property(''group'', @should =
''puppet''),
:backup=>Parameter(backup = puppet, @resource = File[/tmp/ski1]),
:purge=>Parameter(purge = false, @resource = File[/tmp/ski1])},
@totalchanges=0, @tags=[:file], @bucket="puppet", @inited=true,
@clients={}, @arghash={:group=>"puppet"}, @failedchanges=0,
@callbacks={}>
irb(main):004:0> file.should(:group)
=> "puppet"
irb(main):005:0> file.retrieve
=> {Property(''group'', @should =
''puppet'')=>:absent}
irb(main):006:0> file.should(:group)
=> "puppet"
irb(main):007:0>
Luke Kanies wrote:> On Jun 1, 2008, at 7:12 PM, Ski Kacoroski wrote:
>
>> Luke,
>>
>> There is something screwy here with the way the puppet gem installed I
>> think. I get:
>>
>> bash-2.05b# irb
>> irb(main):001:0> require ''puppet''
>> LoadError: No such file to load -- puppet
>> from (irb):1:in `require''
>> from (irb):1
>> irb(main):002:0>
>>
>> but I can run puppetd ok:
>>
>> bash-2.05b# puppet --version
>> 0.24.4
>
>
> This is stupid gems. Do "require ''rubygems''"
and then require
> puppet. Stupid gems. :/
>
--~--~---------~--~----~------------~-------~--~----~
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 fixed this by installed version 1.8.6 of ruby. Not sure why 1.8.2 would not work on the mac. ski Luke Kanies wrote:> On Jun 1, 2008, at 7:12 PM, Ski Kacoroski wrote: > >> Luke, >> >> There is something screwy here with the way the puppet gem installed I >> think. I get: >> >> bash-2.05b# irb >> irb(main):001:0> require ''puppet'' >> LoadError: No such file to load -- puppet >> from (irb):1:in `require'' >> from (irb):1 >> irb(main):002:0> >> >> but I can run puppetd ok: >> >> bash-2.05b# puppet --version >> 0.24.4 > > > This is stupid gems. Do "require ''rubygems''" and then require > puppet. Stupid gems. :/ >--~--~---------~--~----~------------~-------~--~----~ 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 Jun 3, 2008, at 4:11 PM, Ski Kacoroski wrote:> I fixed this by installed version 1.8.6 of ruby. Not sure why 1.8.2 > would not work on the mac.Well, it''s good news that it''s fixed, but I''m a bit surprised to learn there''s an incompatibility with 1.8.2. -- The optimist proclaims that we live in the best of all possible worlds, and the pessimist fears that this is true. -- James Branch Cabell 1879-1958 --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.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 -~----------~----~----~----~------~----~------~--~---
Correction: 10.3 comes with 1.6.8 which does not work. I tried the 1.8.2 DMG installer and that version does not work. I then tried the 1.8.6 DMG installer (includes rails stuff) and it worked. 10.4 comes with 1.8.2 and it works 10.5 comes with 1.8.6 and it works. cheers, ski Luke Kanies wrote:> On Jun 3, 2008, at 4:11 PM, Ski Kacoroski wrote: > >> I fixed this by installed version 1.8.6 of ruby. Not sure why 1.8.2 >> would not work on the mac. > > > Well, it''s good news that it''s fixed, but I''m a bit surprised to learn > there''s an incompatibility with 1.8.2. >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---