2014-04-28 17:50 GMT+02:00 Ádám Sándor <[email protected]>: > Viewing the process tree doesn't show anything new, it doesn't look like > puppet is forking any new processes. It's just using more and more memory > and 94% of CPU. This happens even if I run the provisioning after everything > is set up so it doesn't even have to do much. > > Something I left out from my original post is that I'm running in a vserver > environment. When I tried to replicate that environment locally in my > vagrant box by disabling swap space and setting memory to 512MB puppet > didn't have a problem, so this could be vserver related. Does anyone have a > similar experience? > > On Monday, April 28, 2014 4:14:45 PM UTC+2, Ádám Sándor wrote: >> >> Thanks for the reply. It seems that the Killed message is coming from the >> vserver manager (or whatever it's called, I don't know much about the >> technology), because the process is using too much memory. Which is a >> problem because it means that puppet is using more memory then the >> application actually needs. I'll look into it more closely and try the stuff >> you posted see what that shows. >> >> On Friday, April 25, 2014 2:38:18 PM UTC+2, Felix.Frank wrote: >>> >>> Hi, >>> >>> can you find out wether that is reproducible with Puppet 3.4? If not, >>> you may just want to hold out for 3.6, wait if it works better. >>> >>> For debugging this, I would try two things. >>> >>> First, keep an eye on 'ps auxwf' output while puppet is seemingly >>> frozen, see wether and what is being forked. >>> >>> If that doesn't help, you can try with `strace -f`, although there's a >>> fair chance that it won't yield very conclusive traces. >>> >>> HTH, >>> Felix >>> >>> On 04/21/2014 12:01 PM, Ádám Sándor wrote: >>> > Hi, >>> > >>> > I'm having a problem with my puppet script hanging for a while then >>> > dying with the message "Killed" printed to the console. There is no >>> > further explanation of what happened but I'm suspecting some event >>> > propagation might get stuck and puppet may have some mechanism to kill >>> > the process if it hangs for too long. That's just a guess though, so >>> > please let me know if anyone has some insight on this problem. Thanks! >>> > >>> > I'm running on Debian 7, Puppet 3.5.1. >>> > Tail of the output of "puppet apply --verbose --debug >>> > --modulepath=/root/puppet/modules /root/puppet/ks-prod.pp" is: > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/e4ebdcdc-4bc2-46d0-8e79-24370336ba17%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
Hi, I had a similar problem with another software and the reponsible of killing the process was the "Out-of-Memory Process Killer" Probably your server has not enough memory and no swap and when the puppet process runs the Out-of-Memory Process Killer kills it. Solutions /workarounds: Add some swap to the server Add some memory Hope it helps Best regards -------------------------------------------------------------------------------------- Juan Sierra Pons [email protected] Linux User Registered: #257202 Web: http://www.elsotanillo.net Git: http://www.github.com/juasiepo GPG key = 0xA110F4FE Key Fingerprint = DF53 7415 0936 244E 9B00 6E66 E934 3406 A110 F4FE -------------------------------------------------------------------------------------- -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CABS%3Dy9vh1wo5cZ08a%3DmtBbw0EQc%3DCqCDOqA5yRF93-C%2BVhsd3Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
