On Thursday, June 27, 2013 6:25:57 AM UTC-5, Jonathan Gazeley wrote: > > Hi chaps, > > Since overnight, my puppetmaster has been crashing every now and then > (it has crashed about 5 times this morning). We upgraded to puppet 3.2.2 > about a week ago but the problems only started this morning. There was > nothing in the logs so I ran it in debug mode and captured this: > > /usr/lib/ruby/site_ruby/1.8/puppet/util/methodhelper.rb:14: [BUG] > Segmentation fault > ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] > > We're running puppet-3.2.2-1.el6.noarch on CentOS, direct from the > puppetlabs yum repo. > > Any ideas on how to fix this, or capture more debugging info? > > A segmentation fault surely indicates a bug in the underlying Ruby or in one of the system libraries on which it depends, unless Puppet provides native Ruby extensions of which I am unaware. Pure Ruby code will not generate segfaults unless the Ruby implementation is buggy in some way.
You could run the master under gdb to enable you to get a stack trace of the failure (this will be more useful if you install the relevant debug symbols). You can run it under strace to gather information about the syscalls leading up to the segfault, which might provide a clue about what's happening. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
