Re: FastCGI process dies without being noticed and respawned

Jay Sprenkle <[email protected]> Wed, 3 Jul 2013 06:37:44 -0500
Newsgroups gmane.comp.web.fastcgi.devel
Message-ID <CAG19Bi6Az+1XwfgqjEPF2ehkEM+L2RwGH5d7xZ+KPRmMVwEOAw@mail.gmail.com>
--===============5400395459283663321==
Content-Type: multipart/alternative; boundary=90e6ba61467edf511d04e099e3b3

--90e6ba61467edf511d04e099e3b3
Content-Type: text/plain; charset=ISO-8859-1

You should see if the fastcgi program running but not accepting connections.
That would explain why the web server doesn't respawn it.

On Wed, Jul 3, 2013 at 3:40 AM, 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
>
>


-- 
*http://xkcd.com/1156/*
*
*

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

You should see if the fastcgi program running but not accepting connections=
.<br>That would explain why the web server doesn&#39;t respawn it.<br><br><=
div class=3D"gmail_quote">On Wed, Jul 3, 2013 at 3:40 AM, mephinet <span di=
r=3D"ltr">&lt;<a href=3D"mailto:[email protected]" target=3D"_blank">mephine=
[email protected]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div>Dear Fa=
stCGI devs,<br><br></div>we have a fastcgi program (written in C++) in prod=
uction 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 wi=
thout 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 class=3D"HOEnZb"><font color=3D"#888888">=
<br>
Mephinet<br></font></span></div>
<br>_______________________________________________<br>
FastCGI-developers mailing list<br>
<a href=3D"mailto:FastCGI-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org">FastCGI-developer=
[email protected]</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></blockquote></div><br><br clear=3D"all"><br>-- <br><i style=3D"font-si=
ze:12px;font-family:Verdana,Helvetica,sans-serif"><a href=3D"http://xkcd.co=
m/1156/" target=3D"_blank">http://xkcd.com/1156/</a></i><br><div><div><font=
 face=3D"Verdana, Helvetica, sans-serif"><span style=3D"font-size:12px"><i>=
<br>
</i></span></font><div><br></div></div></div>

--90e6ba61467edf511d04e099e3b3--

--===============5400395459283663321==
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

--===============5400395459283663321==--