[rt-users] rt4-fcgi processes are dying after some debian package updates

[ktm at rice.edu]

On Tue, Aug 05, 2014 at 06:13:16AM -0700, saxmad wrote:
> Hi,
> 
> I'm running the following:
> Debian Wheezy RT 4.0.7 nginx fcgi
> 
> Up until the end of last week, RT had been very stable when running with
> three rt4-fcgi backends.  I would find that about every 3-4 months I would
> have to restart RT as the fcgi processes had died and I was getting "502 bad
> gateway" error messages.
> 
> ...
>
> I'm guessing one or more of the perl related packages is to blame, but
> without any kind of log content to give me any clues, I'm at a loss to
> understand what to try and fix.
> 
> Anyone got any suggestions as to what I can do to firstly get some useful
> log feedback regarding the dying fcgi processes, and secondly what I could
> do to resolve this.
> 
> Thanks,
> Gary
> 
Hi Gary,

As far as figuring out where the problem is, you will need to bump up
your logging level across the systems involved. To fix your immediate
problem of service outages caused when all the fcgi processes exit I
would recommend something like multiwatch to manage them and fire up
a new process automatically as needed:

http://redmine.lighttpd.net/projects/multiwatch/wiki

We use it with spawn-fcgi here and it works well.

Regards,
Ken