Sorry for the delay .. John.. thanks alot for the pointers, I managed to solve the problem following your suggestion. Apparently I had loaded the module "winfacts" in my module dir, though I was not using it for any node it was getting called and causing some looping issues.
As soon as I removed the module from modules dir, everything was back to normal. Thanks a lot for your help. Regards. Rakesh K. On Fri, Nov 1, 2013 at 7:59 PM, jcbollinger <john.bollin...@stjude.org>wrote: > > > On Thursday, October 31, 2013 9:03:08 AM UTC-5, Rakesh K wrote: >> >> Can someone please help or let me knw if you need any info from side ? >> >> > For an urgent issue you should consider seeking paid support from > PuppetLabs. Volunteer forumites do not tend to respond well to demands for > urgent attention. > > With that said, the exception you are encountering is in the "should not > happen" category. It indicates that the Ruby interpreter in which Puppet > is running has exhausted its available runtime stack space by executing too > many nested function calls (possibly through infinite recursion); the > meaning of "too many" depends in part on the size of the parameters and > local variables of each function involved. > > If the problem is a deep, but not infinite, nest of calls then it is > conceivable that you could resolve the issue (on Windows) by increasing > Ruby's stack reservation via an appropriate application of the "editbin" > program to the relevant ruby.exe. I cannot actually recommend doing this, > however, and I will not provide further information because if you pursue > that course then you need to understand exactly what you are doing. > Research it. > > Supposing, though, that the problem is inherent in the manifests you are > trying to apply -- perhaps an infinite recursion in a template or a custom > provider, for example -- it would be reasonable to attempt to narrow down > the issue to the resource(s) or class(es) that causes it. Start by > switching to an empty node declaration for the target node to verify that > the issue is tied to one or more classes or resources, then add classes > back in in a systematic way until you can reproduce the error. Try to > narrow it down to the minimum set of classes with which you can reproduce > the error. Once you have it narrowed down, if you have not yet identified > the issue then come back here with the class (or classes) that is causing > the issue. > > > 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/44dc99d0-e913-40f3-a52b-b77a4d644dad%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/CAEJrXMVmQ2pL4wMmTtXdCUqQduQyRx8DM7B90vZFi%3DQayWnMAg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
