On 06/27/2013 02:59 PM, jcbollinger wrote:
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.
And it's probably something user-specific because bunch of us are
running the same setup (RHEL/CentOS ruby + PuppetLabs puppet rpms) and
have no issues at all...
--
Jakov Sosic
www.srce.unizg.hr
--
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.
