Supervisor does not kill processes, no matter how much cpu they consume, without instruction from the user.
Most likely the process crashes (segmentation fault), or it is a process like gunicorn that kills the workers if they don't respond to an http request after 30 seconds. On 6 October 2016 at 11:55, Javier Marcon <javiermar...@gmail.com> wrote: > I'm running several processes with supervisor 3.0a8-1.1 in ubuntu > precise, but there are a few processes that are very cpu intensive, and > when they are processing data, they are killed and started by supervisor. > > Is there a way to adjust the check method or check interval to avoid this? > > Thanks, > > Javier. > > -- > El matrimo es tan bueno que la gente se muere por casarse > con mujeres como Nazarena Velez, Margerie Orbin, > Jordania Linn Graham, Katherine Knight, Stacey Castor, etc. > > _______________________________________________ > Supervisor-users mailing list > Supervisor-users@lists.supervisord.org > https://lists.supervisord.org/mailman/listinfo/supervisor-users > -- Gustavo J. A. M. Carneiro Gambit Research "The universe is always one step beyond logic." -- Frank Herbert
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org https://lists.supervisord.org/mailman/listinfo/supervisor-users
