Issue #4777 has been updated by arnaud chong.
first: i486-linux second: x86_64-linux on both platform, puppet agent segfault. I noticed something (might be helpful): - the catalog file should be ~240Ko, I saw some catalog files at 3Mo - it works fine with one host When my puppet agents die, if I start one, it breaks on some error like "cannot have source, target and content on class.pp". Which is false, it does not. After removing catalog file, it works fine. I'm wondering if the puppetmasterd could send invalid data that makes the puppet agent segfault. ---------------------------------------- Bug #4777: puppet agent segfault http://projects.puppetlabs.com/issues/4777 Author: arnaud chong Status: Needs more information Priority: High Assignee: Category: executables Target version: 2.6.2 Affected version: 2.6.1 Keywords: Branch: After an upgrade from 0.25.4 to 2.6.1 my puppet agent segfault :( I have only a strace log 6192 nanosleep({0, 10000000}, {5, 3075828636}) = 0 6192 nanosleep({0, 10000000}, {5, 3075828636}) = 0 6192 nanosleep({0, 10000000}, <unfinished ...> 6185 --- SIGSEGV (Segmentation fault) @ 0 (0) --- 6185 write(2, "/usr/lib/ruby/gems/1.8/gems/puppet-2.6.1/lib/puppet/util/zaml.rb:233: "..., 70) = 70 6185 write(2, "[BUG] "..., 6) = 6 6185 write(2, "Segmentation fault"..., 18) = 18 6185 write(2, "\nruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux]\n\n"..., 53) = 53 6185 rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 I'm trying to have more data ... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
