Hi all,
I''m getting the floowing error when I run Puppet agent -t
[...]
Finished catalog run in 209.01 seconds
Error: Could not send report: Could not render to yaml: Stack overflow in regexp
matcher: /\A(?: # ?: non-capturing group (grouping with no back references)
[\x09\x0A\x0D\x20-\x7E] # ASCII
| [\xC2-\xDF][\x80-\xBF] # non-overlong 2-byte
| \xE0[\xA0-\xBF][\x80-\xBF] # excluding overlongs
| [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte
| \xED[\x80-\x9F][\x80-\xBF] # excluding surrogates
| \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3
| [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15
| \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16
)*\z/mxn
I''m running Puppet 3.0.1 on server and client and both are under Amazon
Linux (compatible Centos).
Here is my master''s Puppet.conf : http://pastebin.com/CpbXbuuK ...and
the
client Puppet.conf :http://pastebin.com/irs20s7Y
Do you have any idea of what it is and how to solve it ? Thank you !
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/YSSt-9n-7I0J.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Jeff McCune
2012-Nov-27 18:46 UTC
Re: [Puppet Users] StackOverflow when running Puppet agent -t
On Tue, Nov 27, 2012 at 8:36 AM, Med75 <mohamed.hadrouj@viavoo.com> wrote:> Hi all, > > I''m getting the floowing error when I run Puppet agent -t > > [...] > Finished catalog run in 209.01 seconds > Error: Could not send report: Could not render to yaml: Stack overflow in > regexp matcher: /\A(?: # ?: non-capturing group (grouping with no back > references) > [\x09\x0A\x0D\x20-\x7E] # ASCII > | [\xC2-\xDF][\x80-\xBF] # non-overlong 2-byte > | \xE0[\xA0-\xBF][\x80-\xBF] # excluding overlongs > | [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte > | \xED[\x80-\x9F][\x80-\xBF] # excluding surrogates > | \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3 > | [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15 > | \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16 > )*\z/mxnCould you please run the agent with the --trace --verbose --debug options turned on and then paste the complete stack trace that results in this error? This information will help me diagnose this further. Thanks, -Jeff -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
The problem disappeared after a reboot of the client. I saw your answer too late so I haven''t had the chance to run the agent with --debug and --trace... I''ll update this thread once it will be back again. meanwhile, and after a couple of agent run, I''m now getting a different message, here is the full stack trace: http://pastebin.com/yLdBhcyN I don''t know if this is related or not, and if it would be better to create a new thread. Thanks! Le mardi 27 novembre 2012 19:47:42 UTC+1, Jeff McCune a écrit :> > On Tue, Nov 27, 2012 at 8:36 AM, Med75 <mohamed...@viavoo.com<javascript:>> > wrote: > > Hi all, > > > > I''m getting the floowing error when I run Puppet agent -t > > > > [...] > > Finished catalog run in 209.01 seconds > > Error: Could not send report: Could not render to yaml: Stack overflow > in > > regexp matcher: /\A(?: # ?: non-capturing group (grouping with no back > > references) > > [\x09\x0A\x0D\x20-\x7E] # ASCII > > | [\xC2-\xDF][\x80-\xBF] # non-overlong > 2-byte > > | \xE0[\xA0-\xBF][\x80-\xBF] # excluding > overlongs > > | [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte > > | \xED[\x80-\x9F][\x80-\xBF] # excluding > surrogates > > | \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3 > > | [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15 > > | \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16 > > )*\z/mxn > > Could you please run the agent with the --trace --verbose --debug > options turned on and then paste the complete stack trace that results > in this error? This information will help me diagnose this further. > > Thanks, > -Jeff >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/KGt7j0sm2d0J. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Jeff McCune
2012-Nov-28 17:34 UTC
Re: [Puppet Users] StackOverflow when running Puppet agent -t
On Wed, Nov 28, 2012 at 5:42 AM, Med75 <mohamed.hadrouj@viavoo.com> wrote:> The problem disappeared after a reboot of the client. I saw your answer too > late so I haven''t had the chance to run the agent with --debug and > --trace... I''ll update this thread once it will be back again. > > meanwhile, and after a couple of agent run, I''m now getting a different > message, here is the full stack trace: http://pastebin.com/yLdBhcyN > I don''t know if this is related or not, and if it would be better to create > a new thread.How much memory does the machine have, and how much memory free? It looks like the system is running dry: Cannot allocate memory - fork FYI, In Puppet 3 we''re now using fork when doing catalog runs, which may increase memory utilization relative to previous versions of Puppet. -Jeff -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Mohamed Hadrouj
2012-Nov-28 22:00 UTC
Re: [Puppet Users] StackOverflow when running Puppet agent -t
the system still have free memory, here is what get when I run free command:
total used free shared buffers
cached
Mem: 609600 455840 153760 0 1256 105236
-/+ buffers/cache: 349348 260252
Swap: 0 0 0
2012/11/28 Jeff McCune <jeff@puppetlabs.com>
> On Wed, Nov 28, 2012 at 5:42 AM, Med75 <mohamed.hadrouj@viavoo.com>
wrote:
> > The problem disappeared after a reboot of the client. I saw your
answer
> too
> > late so I haven''t had the chance to run the agent with
--debug and
> > --trace... I''ll update this thread once it will be back
again.
> >
> > meanwhile, and after a couple of agent run, I''m now getting a
different
> > message, here is the full stack trace: http://pastebin.com/yLdBhcyN
> > I don''t know if this is related or not, and if it would be
better to
> create
> > a new thread.
>
> How much memory does the machine have, and how much memory free? It
> looks like the system is running dry:
>
> Cannot allocate memory - fork
>
> FYI, In Puppet 3 we''re now using fork when doing catalog runs,
which
> may increase memory utilization relative to previous versions of
> Puppet.
>
> -Jeff
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.