need help !!!

[Rakesh Kathpal]

Hi,

I am using puppet 2.7.20 server on linux and windows client with same version of puppet.

Until recently everything was working fine but lately I have started getting the error below

[0m
[0;32minfo: Caching catalog for node_windows [0m
[0;37mdebug: Puppet::Type::Exec::ProviderShell: feature posix is missing [0m
[0;37mdebug: Puppet::Type::Exec::ProviderPosix: feature posix is missing [0m
[0;37mdebug: Creating default schedules [0m
[1;35merr: Got an uncaught exception of type SystemStackError: stack level too deep [0m
[0;37mdebug: Storing state [0m
[0;32minfo: Creating state file C:/ProgramData/PuppetLabs/puppet/var/state/state.yaml [0m
[0;37mdebug: Stored state in 0.16 seconds [0m
[0;36mnotice: Finished catalog run in 0.23 seconds [0m
[0;37mdebug: Value of 'preferred_seriali

Please note I use a new windows client every time and do unattended installation of the puppet client and then run the puppet command to fetch the catalog.

Request you guys to help out asap.

Thanks & Regards,

Rakesh K.

[Rakesh Kathpal]

One thing that I have observed is.. I get the error only during the first run... when I execute the puppet command for the second time, it runs without any issues...

[Rakesh Kathpal]

Can someone please help or let me knw if you need any info from side ?

This is really urgent for me..

[jcbollinger]

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

[Rakesh Kathpal]

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.

--
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...@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.

[liam.j.bennett]

I am also seeing this error with 2.7 but I do not have the winfacts module in my module path.

Do we have any way or debugging this sort of error?

[Rakesh Kathpal]

I actually followed the advice given by john,

1) Start with default.. i.e no modules to be declared for the node.. if you get the same error in this case then probably you have some module in the module path that is getting loaded by default which is causing this issue.

2) If you do not get the error in step 1.. then slowly add you classes one by one to see which class is giving you the error.

Please note after each change you do in the node file, you need to puppet agent on the client node to verify.

--
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...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/309c39fc-dd08-4302-86fa-bda02111f191%40googlegroups.com.