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 puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b7898b9e-24d3-4cea-9c31-8276bdce4675%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
