OK, the problem just got a little stranger. my previous puppetruns were done on RHEL6 installed on a kvm, with a kvm host installed with SLES11sp1
I now installed a physical host with RHEL6, using the same resources, and on that system the same puppetruns run without error. I tried both aforementioned motd and issue modules. This would imply it would be more a problem with virtualisation, then with puppet/ruby. It would mean, I have to report this elsewhere (not sure where yet) @ jcbolllinger: the Ruby that was used, is shipped with RHEL6 On Apr 4, 3:02 pm, jcbollinger <john.bollin...@stjude.org> wrote: > On Apr 4, 3:45 am, JohnW <boerma....@gmail.com> wrote: > > > info: Applying configuration version '1301906526' > > debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw > > yaml; using pson > > debug: /File[/etc/issue.net]/content: Executing 'diff -u /etc/ > > issue.net /tmp/puppet-file20110404-27227-u2uokh-0' > > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:341: [BUG] Segmentation > > fault > > ruby 1.8.7 (2010-06-23 patchlevel 299) [x86_64-linux] > > > Aborted (core dumped) > > > It seems like the execution of a system command from within the ruby > > script fails, but I'm not to good with ruby. > > A segmentation fault in a Ruby program likely signals a problem in the > Ruby runtime, not the program. Does the Ruby you are using ship with > RHEL 6? If it was built with a different toolchain or against a > different version of the system libraries than RHEL 6 provides, then > you might see any number of odd behaviors, segmentation faults among > them. > > John -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
