On 4/1/2013 1:15 PM, iamauser wrote:
'sudo passenger-status' gives me a bunch of processes that are forked
from puppetmasterd.
I see that some of these processes are hung up for a long time, e.g.
PID: 5547 (see below). Is this expected behavior for Puppetmaster behind
Passenger ?
If not, how can I kill/cure/avoid these processes without
restarting/killinghttpd.
Thanks
------------------
]$ sudo passenger-status
----------- General information -----------
max = 6
count = 4
active = 1
inactive = 3
Waiting on global queue: 0
----------- Application groups -----------
/usr/share/puppet/rack/puppetmasterd:
App root: /usr/share/puppet/rack/puppetmasterd
* PID: 6185 Sessions: 0 Processed: 119 Uptime: 6m 6s
* PID: 6182 Sessions: 0 Processed: 146 Uptime: 6m 7s
* PID: 5547 Sessions: 0 Processed: 308 Uptime: 41m 38s
* PID: 6169 Sessions: 1 Processed: 236 Uptime: 6m 26s
Each pid is an app process waiting to process an incoming request. You
can read more here,
http://blog.phusion.nl/2010/07/29/the-road-to-passenger-3-technology-preview-4-adding-new-features-and-removing-old-limitations/
Ramin
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
