Re: Just a note about my FastCGI-Apache socket lockup problemu

Anthony Rumble (anthonyr@ce.com.au)
Thu, 30 Jan 1997 10:16:15 +1100 (EST)

Message-Id: <m0vpjEm-0002VpC@enterprise.ce.com.au>
Subject: Re: Just a note about my FastCGI-Apache socket lockup problemu
To: gambarin@OpenMarket.com (Stanley Gambarin)
Date: Thu, 30 Jan 1997 10:16:15 +1100 (EST)
In-Reply-To: <199701291531.KAA22748@u4-138.openmarket.com> from "Stanley Gambarin" at Jan 29, 97 10:31:42 am
From: anthonyr@ce.com.au (Anthony Rumble)

> > [snip]
> > BUT.. I notice occasionally the FastCGI apps die and close
> > with an error 9
> > 
> 	It would be helpful to know which directive has errno=9, since
> the mapping between names for errno and the actual values is machine
> dependent (and usually declared in /usr/include/sys/errno.h)

Errno 9 = #define EBADF            9      /* Bad file number */

> > I also get these.. but these could be something else :- 
> > 
> > [Tue Jan 28 05:20:33 1997] mod_fastcgi: AppClass /home/httpd/html/matilda/level1
> > /level1.fcg pid 24521 terminated due to uncaught signal 13.
> > [Tue Jan 28 05:20:33 1997] mod_fastcgi: AppClass /home/httpd/html/matilda/level1
> > /level1.fcg restarted with pid 28118.
> > [Tue Jan 28 05:21:32 1997] read script input or send script output timed out for
> >  205.169.44.13
> > [Tue Jan 28 05:21:32 1997] access to /home/httpd/html/matilda/level1/level1.fcg 
> > failed for 205.169.44.13, reason: mod_fastcgi: OS error 'Interrupted system call
> > ' while communicating with app
> > [Tue Jan 28 05:21:51 1997] read script input or send script output timed out for
> >  168.121.229.39
> 	I am assuming that signal=13 is SIGPIPE (declared in 
> /usr/include/sys/signal.h).  In that case, the problem could be related
> in the fact that FastCGI application terminates before web server
> could connect to it, so when the web server tries to write to the
> socket, we get SIGPIPE.
> 	The 'Interrupted system call' was a known problem is the v. 1.5
> of the FastCGI Developer's Kit, due to some failed calls to accept() and
> connect().  A minor update in v1.5.1 (available on http://www.fastcgi.com)
> should have fixed the problem.  If you are still having problems, please
> send email with a better description of when the bug occurs.
> 	Finally, timeout problem could be due to certain bugs in the
> Apache server, which are mentioned in http://www.worldgate.com/~marcs/fin_wait_
> 2.html and are related to closing
> network sockets and shutting down client/server connections.

I am trialling the new 1.2b6 server now with what is (It think) the latest
fastcgi.c

Can I make a big request here... can you PLEASE rename apache-fastcgi.tar.Z
to something like apache-fastcgi-v1.5.1.tar.Z or something..

It's allmost impossible to know wether I have the right one.. or if
there is a new one available...

-- 
Anthony Rumble - Online Ordering Systems
Corporate Express Australia Limited
Phone 02-9335-0669 Fax 02-9335-0753 Mobile 015-955-042 Pager 016-634-997