Rob McBroom
2010-Apr-08 20:50 UTC
[Puppet Users] Puppet commands giving nothing but a stack trace
I suspect this has more to do with Ruby than Puppet, but I know little about
Ruby and Google has failed me, so I''m asking here.
I''m finally getting some of our older systems brought into Puppet. I
installed it on several this morning without incident, but there are two (more
or less identical RHEL 5.3 systems) that throw horrible errors. These systems
did not have Puppet or Ruby installed prior to today.
# puppet --version
/usr/lib/ruby/1.8/sync.rb:214:in `sync_unlock'': stack level too
deep (SystemStackError)
from /usr/lib/ruby/1.8/sync.rb:231:in `synchronize''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:290:in
`name''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:288:in
`each''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:288:in
`name''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:825:in
`each_source''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:823:in
`each''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:823:in
`each_source''
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:667:in
`uninterpolated_value''
... 10 levels...
from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppet.rb:1:in
`require''
from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppet.rb:1
from /usr/bin/puppet:70:in `require''
from /usr/bin/puppet:70
It seems that `facter` also poops its pants:
# facter
Could not retrieve kernel: stack level too deep
/usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:31:in
`exec'': stack level too deep (SystemStackError)
from /usr/lib/ruby/site_ruby/1.8/facter/kernel.rb:6
from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:118:in
`call''
from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:118:in
`value''
from /usr/lib/ruby/1.8/timeout.rb:48:in `timeout''
from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:116:in
`value''
from /usr/lib/ruby/site_ruby/1.8/facter/util/fact.rb:75:in
`value''
from /usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:73:in
`inject''
from /usr/lib/ruby/site_ruby/1.8/facter/util/fact.rb:71:in
`each''
... 16 levels...
from /usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:30:in
`load_all''
from /usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all''
from /usr/lib/ruby/site_ruby/1.8/facter.rb:91:in `to_hash''
from /usr/bin/facter:138
Ruby itself seems to run:
# ruby --version
ruby 1.8.5 (2006-08-25) [x86_64-linux]
But that''s not much of a challenge and I don''t know how to do
anything more complicated. Perhaps there''s some boring Ruby one-liner I
could try to see if it''s working?
--
Rob McBroom
<http://www.skurfer.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.
Ken
2010-Apr-08 21:48 UTC
[Puppet Users] Re: Puppet commands giving nothing but a stack trace
I don''t suppose its your stack size? Whats the output of ''ulimit -a'' on your box (as the user you were trying to run those command as of course). Mine is 8192 kb. Can you try it with a later version of Ruby from RHEL 5.4? On Apr 8, 9:50 pm, Rob McBroom <mailingli...@skurfer.com> wrote:> I suspect this has more to do with Ruby than Puppet, but I know little about Ruby and Google has failed me, so I''m asking here. > > I''m finally getting some of our older systems brought into Puppet. I installed it on several this morning without incident, but there are two (more or less identical RHEL 5.3 systems) that throw horrible errors. These systems did not have Puppet or Ruby installed prior to today. > > # puppet --version > /usr/lib/ruby/1.8/sync.rb:214:in `sync_unlock'': stack level too deep (SystemStackError) > from /usr/lib/ruby/1.8/sync.rb:231:in `synchronize'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:290:in `name'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:288:in `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:288:in `name'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:825:in `each_source'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:823:in `each'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:823:in `each_source'' > from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:667:in `uninterpolated_value'' > ... 10 levels... > from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppet.rb:1:in `require'' > from /usr/lib/ruby/site_ruby/1.8/puppet/application/puppet.rb:1 > from /usr/bin/puppet:70:in `require'' > from /usr/bin/puppet:70 > > It seems that `facter` also poops its pants: > > # facter > Could not retrieve kernel: stack level too deep > /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:31:in `exec'': stack level too deep (SystemStackError) > from /usr/lib/ruby/site_ruby/1.8/facter/kernel.rb:6 > from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:118:in `call'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:118:in `value'' > from /usr/lib/ruby/1.8/timeout.rb:48:in `timeout'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/resolution.rb:116:in `value'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/fact.rb:75:in `value'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:73:in `inject'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/fact.rb:71:in `each'' > ... 16 levels... > from /usr/lib/ruby/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'' > from /usr/lib/ruby/site_ruby/1.8/facter/util/collection.rb:90:in `load_all'' > from /usr/lib/ruby/site_ruby/1.8/facter.rb:91:in `to_hash'' > from /usr/bin/facter:138 > > Ruby itself seems to run: > > # ruby --version > ruby 1.8.5 (2006-08-25) [x86_64-linux] > > But that''s not much of a challenge and I don''t know how to do anything more complicated. Perhaps there''s some boring Ruby one-liner I could try to see if it''s working? > > -- > Rob McBroom > <http://www.skurfer.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 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.
Rob McBroom
2010-Apr-09 12:56 UTC
Re: [Puppet Users] Re: Puppet commands giving nothing but a stack trace
On Apr 8, 2010, at 5:48 PM, Ken wrote:> I don''t suppose its your stack size? Whats the output of ''ulimit -a'' > on your box (as the user you were trying to run those command as of > course). Mine is 8192 kb.Bingo. Someone had set it to 128 for all users (without my knowledge). I changed it to only affect the relevant users and Puppet fires right up. Thanks. -- Rob McBroom <http://www.skurfer.com/> Don''t try to tell me a thing is important to you if the whole of your “support” entails forcing others to spend time and money on 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-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.
Bruce Richardson
2010-Apr-09 13:10 UTC
Re: [Puppet Users] Re: Puppet commands giving nothing but a stack trace
On Fri, Apr 09, 2010 at 08:56:39AM -0400, Rob McBroom wrote:> > Bingo. Someone had set it to 128 for all users (without my knowledge). > I changed it to only affect the relevant users and Puppet fires right > up. Thanks.You''re running Puppet and somebody changed the ulimit config on the box without telling you? There''s ironic and there''s plain contrary. -- Bruce Explota!: miles de lemmings no pueden estar equivocados.