On Friday, October 3, 2014 9:06:09 AM UTC-5, Brian Morris wrote: > > I was wrong, Jonathan. That error is actually somewhere in a manifest. You > can troubleshoot it the same way, though. Just start commenting out > sections of code in the order that your manifests are invoked in, until you > find the culprit.
The error appears to reflect a bug in your Ruby implementation. No segmentation fault can be *directly* attributed to your manifests. On the other hand, it is likely that the segfault arises from some form of unexpected input conveyed to Ruby by Puppet at the behest of one of your manifests, so you probably do have a contributory issue in one of your manifests and/or in a fact implementation. (The error does not arise from loading or evaluating a fact, but it may be related to a bad fact value.) Since the error is intermittent, I would start by trying to characterize the situations under which it occurs. For example, - Is the error specific to a subset of you client machines (or even to just one)? - Is there a specific time of day window in which the error usually occurs? - If you are load balancing across multiple masters, does the error always occur at the same master? It would be very much to your advantage in troubleshooting this if you can figure out conditions under which you can reliably produce the error. For one thing, that in itself might make the nature of the problem clear. Even if the problem remains mysterious at that point, being able to reproduce it will greatly facilitate finding the problem and verifying your fix. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/eb60afdb-bda1-47ef-8fcb-8373cc1aac48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
