Re: FastCGI process dies without being noticed and respawned

Santosh Mankar <[email protected]> Wed, 3 Jul 2013 19:44:46 +0530
Newsgroups gmane.comp.web.fastcgi.devel
Message-ID <CAFGhAso8gRRuTVmvG5ozyp+07DX+4OFZJcVhnV6KBxrrth+=AQ@mail.gmail.com>
--===============4183886978785807116==
Content-Type: multipart/alternative; boundary=20cf30334df371d80704e09c1545

--20cf30334df371d80704e09c1545
Content-Type: text/plain; charset=ISO-8859-1

> 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 <[email protected]> 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-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
>> http://mailman.fastcgi.com/mailman/listinfo/fastcgi-developers
>>
>>
>

--20cf30334df371d80704e09c1545
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div>I dont think your fast CGI process got killed. it could be possible th=
at the apache process which is managing fastcgi process got into some probl=
em.</div>
<div>=A0</div>
<div>you can easily reproduce the problem by sending SIGTERM to apache proc=
ess which is managing fastcgi processes.</div>
<div>=A0</div>
<div>Regards,</div>
<div>Santosh<br><br></div>
<div class=3D"gmail_quote">
<div>
<div class=3D"h5">On Wed, Jul 3, 2013 at 2:10 PM, mephinet <span dir=3D"ltr=
">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
t</a>&gt;</span> wrote:<br></div></div>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div>
<div class=3D"h5">
<div dir=3D"ltr">
<div>
<div>
<div>
<div>Dear FastCGI devs,<br><br></div>we have a fastcgi program (written in =
C++) in production for several years now. On one of our systems, we see thi=
s phenomenon, that the process suddenly dies without any information in the=
 logs and without being respawned.<br>
<br>Normally, respawning works fine:<br><br>[Tue Jul 02 07:55:19 2013] [war=
n] FastCGI: server &quot;.../catcgi.fcgi&quot; restarted (pid 9274)<br>[Tue=
 Jul 02 08:08:57 2013] [warn] FastCGI: server &quot;.../catcgi.fcgi&quot; r=
estarted (pid 8632)<br>
[Tue Jul 02 15:01:53 2013] [warn] FastCGI: server &quot;.../catcgi.fcgi&quo=
t; restarted (pid 28313)<br>[Tue Jul 02 15:04:02 2013] [warn] FastCGI: serv=
er &quot;.../catcgi.fcgi&quot; restarted (pid 1906)<br><br>however, two hou=
rs later:<br>
<br>[Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] (111)Connecti=
on refused: FastCGI: failed to connect to server &quot;.../catcgi.fcgi&quot=
;: connect() failed<br>[Tue Jul 02 16:53:11 2013] [error] [client 194.158.1=
59.8] FastCGI: incomplete headers (0 bytes) received from server &quot;.../=
catcgi.fcgi&quot;<br>
[Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8] (111)Connection r=
efused: FastCGI: failed to connect to server &quot;.../catcgi.fcgi&quot;: c=
onnect() failed<br>[Tue Jul 02 16:53:11 2013] [error] [client 194.158.159.8=
] FastCGI: incomplete headers (0 bytes) received from server &quot;.../catc=
gi.fcgi&quot;<br>
...<br><br></div>The server configuration:<br><br>LogLevel=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 warn<br>FastCgiServer .../catcgi.fcgi \<br>=
=A0=A0=A0 -initial-env ... \<br>=A0=A0=A0 -idle-timeout 120<br><br></div>Ho=
w can that happen that the fastcgi process dies (or ceases to accept connec=
ts) without the fastcgi process manager taking notice, logging an error and=
 respawning it?<br>
<br>The system is:<br>Red Hat Enterprise Linux Server release 5.6 (Tikanga)=
<br>Apache/2.2.3<br>mod_fastcgi/2.4.6<br>Linux 2.6.18-238.1.1.el5<br><br></=
div>Thanks for your support!<span><font color=3D"#888888"><br>Mephinet<br>
</font></span></div><br></div></div>
<div class=3D"im">_______________________________________________<br>FastCG=
I-developers mailing list<br><a href=3D"mailto:[email protected]=
astcgi.com" target=3D"_blank">FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org</a><br=
>
<a href=3D"http://mailman.fastcgi.com/mailman/listinfo/fastcgi-developers" =
target=3D"_blank">http://mailman.fastcgi.com/mailman/listinfo/fastcgi-devel=
opers</a><br><br></div></blockquote></div><br></blockquote></div><br>

--20cf30334df371d80704e09c1545--

--===============4183886978785807116==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
FastCGI-developers mailing list
FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
http://mailman.fastcgi.com/mailman/listinfo/fastcgi-developers

--===============4183886978785807116==--