[FASTCGI] FastCGI process dies without being noticed and respawned

Santosh Mankar mankar.san at gmail.com
Wed Jul 3 10:14:46 EDT 2013


> I dont think your fast CGI process got killed. it could be possible that
> the apache process which is managing fastcgi process got into some problem.
>
> you can easily reproduce the problem by sending SIGTERM to apache process
> which is managing fastcgi processes.
>
> Regards,
> Santosh
>
>  On Wed, Jul 3, 2013 at 2:10 PM, mephinet <mephinet at gmx.net> wrote:
>
>>    Dear FastCGI devs,
>>
>> we have a fastcgi program (written in C++) in production for several
>> years now. On one of our systems, we see this phenomenon, that the process
>> suddenly dies without any information in the logs and without being
>> respawned.
>>
>> Normally, respawning works fine:
>>
>> [Tue Jul 02 07:55:19 2013] [warn] FastCGI: server ".../catcgi.fcgi"
>> restarted (pid 9274)
>> [Tue Jul 02 08:08:57 2013] [warn] FastCGI: server ".../catcgi.fcgi"
>> restarted (pid 8632)
>> [Tue Jul 02 15:01:53 2013] [warn] FastCGI: server ".../catcgi.fcgi"
>> restarted (pid 28313)
>> [Tue Jul 02 15:04:02 2013] [warn] FastCGI: server ".../catcgi.fcgi"
>> restarted (pid 1906)
>>
>> however, two hours later:
>>
>> [Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] (111)Connection
>> refused: FastCGI: failed to connect to server ".../catcgi.fcgi": connect()
>> failed
>> [Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] FastCGI:
>> incomplete headers (0 bytes) received from server ".../catcgi.fcgi"
>> [Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] (111)Connection
>> refused: FastCGI: failed to connect to server ".../catcgi.fcgi": connect()
>> failed
>> [Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] FastCGI:
>> incomplete headers (0 bytes) received from server ".../catcgi.fcgi"
>> ...
>>
>> The server configuration:
>>
>> LogLevel                warn
>> FastCgiServer .../catcgi.fcgi \
>>     -initial-env ... \
>>     -idle-timeout 120
>>
>> How can that happen that the fastcgi process dies (or ceases to accept
>> connects) without the fastcgi process manager taking notice, logging an
>> error and respawning it?
>>
>> The system is:
>> Red Hat Enterprise Linux Server release 5.6 (Tikanga)
>> Apache/2.2.3
>> mod_fastcgi/2.4.6
>> Linux 2.6.18-238.1.1.el5
>>
>> Thanks for your support!
>> Mephinet
>>
>> _______________________________________________
>> FastCGI-developers mailing list
>> FastCGI-developers at mailman.fastcgi.com
>> http://mailman.fastcgi.com/mailman/listinfo/fastcgi-developers
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.fastcgi.com/pipermail/fastcgi-developers/attachments/20130703/6c3069d9/attachment.html>


More information about the FastCGI-developers mailing list