Hi,
I have a running puppetmaster with nginx and passenger and ruby 1.9.2.
When i do puppet cert --trace --list . i get the following error.
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/
cert.rb:43:in `block (2 levels) in <class:Cert>''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
357:in `block (2 levels) in parse_options''
/usr/lib64/ruby/1.9.1/optparse.rb:1277:in `call''
/usr/lib64/ruby/1.9.1/optparse.rb:1277:in `block in parse_in_order''
/usr/lib64/ruby/1.9.1/optparse.rb:1264:in `catch''
/usr/lib64/ruby/1.9.1/optparse.rb:1264:in `parse_in_order''
/usr/lib64/ruby/1.9.1/optparse.rb:1258:in `order!''
/usr/lib64/ruby/1.9.1/optparse.rb:1349:in `permute!''
/usr/lib64/ruby/1.9.1/optparse.rb:1370:in `parse!''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
364:in `parse_options''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/
cert.rb:230:in `parse_options''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
302:in `block (2 levels) in run''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
410:in `hook''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
302:in `block in run''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
401:in `exit_on_fail''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application.rb:
302:in `run''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/util/
command_line.rb:69:in `execute''
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/bin/puppet:4:in `<top
(required)>''
/usr/bin/puppet:19:in `load''
/usr/bin/puppet:19:in `<main>''
Could not parse options: wrong number of arguments (1 for 0)
I have seen this bug on http://projects.puppetlabs.com/issues/7428
However i am unable to solve the problem given in the link.
I changed /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/
application/cert.rb
Eg:
option("--all", "-a") do
@all = true
end
to
option("--all", "-a") do |*_|
@all = true
end
Am i doing anything wrong.
Regards,
Kevin
--
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, Dec 15, 2011 at 02:33, linuxbsdfreak <linuxbsdfreak@gmail.com> wrote: Hey there.> I have a running puppetmaster with nginx and passenger and ruby 1.9.2.I see something odd here - 1.9.2 in the line above, and ...> When i do puppet cert --trace --list . i get the following error. > > /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ > cert.rb:43:in `block (2 levels) in <class:Cert>''... 1.9.1 here. Which we don''t actually support. My guess is you are running with 1.9.1 accidentally, and that is breaking. Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
Dan - Some distro''s pinned these kind of directories at 1.9.1. For example in Debian the package is called ruby-1.9.1 even though its version 1.9.2/1.9.3 (depending on release). # ruby1.9.1 --version ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] # ls /usr/lib/ruby/ 1.8 1.9.1 vendor_ruby Anyhow ... what is interesting, is that I can replicate this on wheezy. # gem1.9.1 install puppet # ruby1.9.1 /usr/local/bin/puppet cert --list /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use RbConfig instead of obsolete and deprecated Config. /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': iconv will be deprecated in the future, use String#encode instead. Could not parse options: wrong number of arguments (1 for 0) And switching back to the packaged version: # /usr/bin/puppet cert --list --all + dashboard (B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5) + db1.vms.cloud.bob.sh (C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06) + foremanweb1.vms.cloud.bob.sh (F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86) + ken@bob.sh (CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8) + lb1.vms.cloud.bob.sh (73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1) + mc-server-global (52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1) + node1.cloud.bob.sh (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names: DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh) + web1.vms.cloud.bob.sh (68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D) root@node1:~# Odd. I''ll dig a bit further. ken. On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman <daniel@puppetlabs.com> wrote:> On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak <linuxbsdfreak@gmail.com> wrote: > > Hey there. > >> I have a running puppetmaster with nginx and passenger and ruby 1.9.2. > > I see something odd here - 1.9.2 in the line above, and ... > >> When i do puppet cert --trace --list . i get the following error. >> >> /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ >> cert.rb:43:in `block (2 levels) in <class:Cert>'' > > ... 1.9.1 here. Which we don''t actually support. > > My guess is you are running with 1.9.1 accidentally, and that is breaking. > > Daniel > -- > ⎋ Puppet Labs Developer – http://puppetlabs.com > ♲ Made with 100 percent post-consumer electrons > > -- > 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.
Okay - so its a known issue: http://projects.puppetlabs.com/issues/7428 Looks like there is a workaround there Kevin. Let us know how you go. ken. On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber <ken@puppetlabs.com> wrote:> Dan - Some distro''s pinned these kind of directories at 1.9.1. For > example in Debian the package is called ruby-1.9.1 even though its > version 1.9.2/1.9.3 (depending on release). > > # ruby1.9.1 --version > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] > # ls /usr/lib/ruby/ > 1.8 1.9.1 vendor_ruby > > Anyhow ... what is interesting, is that I can replicate this on wheezy. > > # gem1.9.1 install puppet > # ruby1.9.1 /usr/local/bin/puppet cert --list > /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use > RbConfig instead of obsolete and deprecated Config. > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': iconv > will be deprecated in the future, use String#encode instead. > Could not parse options: wrong number of arguments (1 for 0) > > And switching back to the packaged version: > > # /usr/bin/puppet cert --list --all > + dashboard (B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5) > + db1.vms.cloud.bob.sh (C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06) > + foremanweb1.vms.cloud.bob.sh (F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86) > + ken@bob.sh (CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8) > + lb1.vms.cloud.bob.sh (73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1) > + mc-server-global (52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1) > + node1.cloud.bob.sh > (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names: > DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh) > + web1.vms.cloud.bob.sh (68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D) > root@node1:~# > > Odd. I''ll dig a bit further. > > ken. > > On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman <daniel@puppetlabs.com> wrote: >> On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak <linuxbsdfreak@gmail.com> wrote: >> >> Hey there. >> >>> I have a running puppetmaster with nginx and passenger and ruby 1.9.2. >> >> I see something odd here - 1.9.2 in the line above, and ... >> >>> When i do puppet cert --trace --list . i get the following error. >>> >>> /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ >>> cert.rb:43:in `block (2 levels) in <class:Cert>'' >> >> ... 1.9.1 here. Which we don''t actually support. >> >> My guess is you are running with 1.9.1 accidentally, and that is breaking. >> >> Daniel >> -- >> ⎋ Puppet Labs Developer – http://puppetlabs.com >> ♲ Made with 100 percent post-consumer electrons >> >> -- >> 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.
Hi,
As i already mentioned on the 1st post. I have edited the file and
changed the entries mentioned in the post.
I changed /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/
application/cert.rb
Eg:
option("--all", "-a") do
@all = true
end
to
option("--all", "-a") do |*_|
@all = true
end
Is the syntax correct or wrong.
Regards,
Kevin
On Dec 15, 8:57 pm, Ken Barber <k...@puppetlabs.com>
wrote:> Okay - so its a known issue:
>
> http://projects.puppetlabs.com/issues/7428
>
> Looks like there is a workaround there Kevin. Let us know how you go.
>
> ken.
>
>
>
>
>
>
>
> On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber <k...@puppetlabs.com>
wrote:
> > Dan - Some distro''s pinned these kind of directories at
1.9.1. For
> > example in Debian the package is called ruby-1.9.1 even though its
> > version 1.9.2/1.9.3 (depending on release).
>
> > # ruby1.9.1 --version
> > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]
> > # ls /usr/lib/ruby/
> > 1.8 1.9.1 vendor_ruby
>
> > Anyhow ... what is interesting, is that I can replicate this on
wheezy.
>
> > # gem1.9.1 install puppet
> > # ruby1.9.1 /usr/local/bin/puppet cert --list
> > /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use
> > RbConfig instead of obsolete and deprecated Config.
> > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in
`require'': iconv
> > will be deprecated in the future, use String#encode instead.
> > Could not parse options: wrong number of arguments (1 for 0)
>
> > And switching back to the packaged version:
>
> > # /usr/bin/puppet cert --list --all
> > + dashboard
(B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5)
> > + db1.vms.cloud.bob.sh
(C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06)
> > + foremanweb1.vms.cloud.bob.sh
(F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86)
> > + k...@bob.sh
(CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8)
> > + lb1.vms.cloud.bob.sh
(73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1)
> > + mc-server-global
(52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1)
> > + node1.cloud.bob.sh
> > (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names:
> > DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh)
> > + web1.vms.cloud.bob.sh
(68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D)
> > root@node1:~#
>
> > Odd. I''ll dig a bit further.
>
> > ken.
>
> > On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman
<dan...@puppetlabs.com> wrote:
> >> On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak
<linuxbsdfr...@gmail.com> wrote:
>
> >> Hey there.
>
> >>> I have a running puppetmaster with nginx and passenger and
ruby 1.9.2.
>
> >> I see something odd here - 1.9.2 in the line above, and ...
>
> >>> When i do puppet cert --trace --list . i get the following
error.
>
> >>>
/usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/
> >>> cert.rb:43:in `block (2 levels) in
<class:Cert>''
>
> >> ... 1.9.1 here. Which we don''t actually support.
>
> >> My guess is you are running with 1.9.1 accidentally, and that is
breaking.
>
> >> Daniel
> >> --
> >> ⎋ Puppet Labs Developer –http://puppetlabs.com
> >> ♲ Made with 100 percent post-consumer electrons
>
> >> --
> >> 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.
That should be fine as long as you''re only running on Ruby 1.9. A fix for this issue went into our 2.7.x branch yesterday [ https://github.com/puppetlabs/puppet/commit/933844567fbe4078cb76f2c089ced1cb6c4170b7]. I''d love to hear if that solves your problems, although I think on 1.9.2 it''s functionally equivalent to what you''re already doing. On Fri, Dec 16, 2011 at 4:50 AM, linuxbsdfreak <linuxbsdfreak@gmail.com>wrote:> Hi, > > As i already mentioned on the 1st post. I have edited the file and > changed the entries mentioned in the post. > > > I changed /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/ > application/cert.rb > > Eg: > > option("--all", "-a") do > @all = true > end > > to > > option("--all", "-a") do |*_| > @all = true > end > > Is the syntax correct or wrong. > > Regards, > Kevin > > On Dec 15, 8:57 pm, Ken Barber <k...@puppetlabs.com> wrote: > > Okay - so its a known issue: > > > > http://projects.puppetlabs.com/issues/7428 > > > > Looks like there is a workaround there Kevin. Let us know how you go. > > > > ken. > > > > > > > > > > > > > > > > On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber <k...@puppetlabs.com> wrote: > > > Dan - Some distro''s pinned these kind of directories at 1.9.1. For > > > example in Debian the package is called ruby-1.9.1 even though its > > > version 1.9.2/1.9.3 (depending on release). > > > > > # ruby1.9.1 --version > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] > > > # ls /usr/lib/ruby/ > > > 1.8 1.9.1 vendor_ruby > > > > > Anyhow ... what is interesting, is that I can replicate this on wheezy. > > > > > # gem1.9.1 install puppet > > > # ruby1.9.1 /usr/local/bin/puppet cert --list > > > /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use > > > RbConfig instead of obsolete and deprecated Config. > > > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': iconv > > > will be deprecated in the future, use String#encode instead. > > > Could not parse options: wrong number of arguments (1 for 0) > > > > > And switching back to the packaged version: > > > > > # /usr/bin/puppet cert --list --all > > > + dashboard > (B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5) > > > + db1.vms.cloud.bob.sh > (C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06) > > > + foremanweb1.vms.cloud.bob.sh(F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86) > > > + k...@bob.sh > (CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8) > > > + lb1.vms.cloud.bob.sh > (73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1) > > > + mc-server-global > (52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1) > > > + node1.cloud.bob.sh > > > (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names: > > > DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh) > > > + web1.vms.cloud.bob.sh > (68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D) > > > root@node1:~# > > > > > Odd. I''ll dig a bit further. > > > > > ken. > > > > > On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman <dan...@puppetlabs.com> > wrote: > > >> On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak <linuxbsdfr...@gmail.com> > wrote: > > > > >> Hey there. > > > > >>> I have a running puppetmaster with nginx and passenger and ruby > 1.9.2. > > > > >> I see something odd here - 1.9.2 in the line above, and ... > > > > >>> When i do puppet cert --trace --list . i get the following error. > > > > >>> /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ > > >>> cert.rb:43:in `block (2 levels) in <class:Cert>'' > > > > >> ... 1.9.1 here. Which we don''t actually support. > > > > >> My guess is you are running with 1.9.1 accidentally, and that is > breaking. > > > > >> Daniel > > >> -- > > >> ⎋ Puppet Labs Developer –http://puppetlabs.com > > >> ♲ Made with 100 percent post-consumer electrons > > > > >> -- > > >> 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.
Hi Patrick, The checked the diff and applied it. It works now. Hope its fixed in the new version. Regards, Kevin On Dec 16, 7:17 pm, Patrick Carlisle <patr...@puppetlabs.com> wrote:> That should be fine as long as you''re only running on Ruby 1.9. A fix for > this issue went into our 2.7.x branch yesterday [https://github.com/puppetlabs/puppet/commit/933844567fbe4078cb76f2c08...]. > I''d love to hear if that solves your problems, although I think on 1.9.2 > it''s functionally equivalent to what you''re already doing. > > On Fri, Dec 16, 2011 at 4:50 AM, linuxbsdfreak <linuxbsdfr...@gmail.com>wrote: > > > > > > > > > Hi, > > > As i already mentioned on the 1st post. I have edited the file and > > changed the entries mentioned in the post. > > > I changed /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/ > > application/cert.rb > > > Eg: > > > option("--all", "-a") do > > @all = true > > end > > > to > > > option("--all", "-a") do |*_| > > @all = true > > end > > > Is the syntax correct or wrong. > > > Regards, > > Kevin > > > On Dec 15, 8:57 pm, Ken Barber <k...@puppetlabs.com> wrote: > > > Okay - so its a known issue: > > > >http://projects.puppetlabs.com/issues/7428 > > > > Looks like there is a workaround there Kevin. Let us know how you go. > > > > ken. > > > > On Thu, Dec 15, 2011 at 7:40 PM, Ken Barber <k...@puppetlabs.com> wrote: > > > > Dan - Some distro''s pinned these kind of directories at 1.9.1. For > > > > example in Debian the package is called ruby-1.9.1 even though its > > > > version 1.9.2/1.9.3 (depending on release). > > > > > # ruby1.9.1 --version > > > > ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux] > > > > # ls /usr/lib/ruby/ > > > > 1.8 1.9.1 vendor_ruby > > > > > Anyhow ... what is interesting, is that I can replicate this on wheezy. > > > > > # gem1.9.1 install puppet > > > > # ruby1.9.1 /usr/local/bin/puppet cert --list > > > > /var/lib/gems/1.9.1/gems/facter-1.6.4/lib/facter/util/config.rb:7: Use > > > > RbConfig instead of obsolete and deprecated Config. > > > > /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'': iconv > > > > will be deprecated in the future, use String#encode instead. > > > > Could not parse options: wrong number of arguments (1 for 0) > > > > > And switching back to the packaged version: > > > > > # /usr/bin/puppet cert --list --all > > > > + dashboard > > (B6:1F:91:F3:70:E4:AD:C5:4C:B8:40:BF:0D:2A:7D:C5) > > > > + db1.vms.cloud.bob.sh > > (C6:B2:F7:3E:9A:DB:F7:75:22:CD:6F:30:55:3E:C5:06) > > > > + foremanweb1.vms.cloud.bob.sh(F8:0D:12:BB:F8:D1:3A:AD:A2:73:46:E2:78:85:69:86) > > > > + k...@bob.sh > > (CB:9C:4E:67:41:59:4B:43:39:0C:4B:DD:25:A2:19:D8) > > > > + lb1.vms.cloud.bob.sh > > (73:C7:B3:4D:C9:5A:1D:D6:80:C2:57:96:B5:0A:A9:C1) > > > > + mc-server-global > > (52:63:C0:02:14:83:CD:9D:36:0D:82:3F:E3:19:03:E1) > > > > + node1.cloud.bob.sh > > > > (4B:12:11:DE:8F:21:71:EA:50:3A:70:97:81:0C:A9:E4) (alt names: > > > > DNS:puppet, DNS:node1.cloud.bob.sh, DNS:puppet.cloud.bob.sh) > > > > + web1.vms.cloud.bob.sh > > (68:CC:0A:6F:80:CC:84:DE:3D:37:0A:02:E5:2A:BA:6D) > > > > root@node1:~# > > > > > Odd. I''ll dig a bit further. > > > > > ken. > > > > > On Thu, Dec 15, 2011 at 7:20 PM, Daniel Pittman <dan...@puppetlabs.com> > > wrote: > > > >> On Thu, Dec 15, 2011 at 02:33, linuxbsdfreak <linuxbsdfr...@gmail.com> > > wrote: > > > > >> Hey there. > > > > >>> I have a running puppetmaster with nginx and passenger and ruby > > 1.9.2. > > > > >> I see something odd here - 1.9.2 in the line above, and ... > > > > >>> When i do puppet cert --trace --list . i get the following error. > > > > >>> /usr/lib64/ruby/gems/1.9.1/gems/puppet-2.7.9/lib/puppet/application/ > > > >>> cert.rb:43:in `block (2 levels) in <class:Cert>'' > > > > >> ... 1.9.1 here. Which we don''t actually support. > > > > >> My guess is you are running with 1.9.1 accidentally, and that is > > breaking. > > > > >> Daniel > > > >> -- > > > >> ⎋ Puppet Labs Developer –http://puppetlabs.com > > > >> ♲ Made with 100 percent post-consumer electrons > > > > >> -- > > > >> 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.