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

Stanley Gambarin (gambarin@OpenMarket.com)
Wed, 29 Jan 1997 10:31:42 -0500

Message-Id: <199701291531.KAA22748@u4-138.openmarket.com>
To: anthonyr@ce.com.au (Anthony Rumble)
Subject: Re: Just a note about my FastCGI-Apache socket lockup problem 
In-Reply-To: Your message of "Tue, 28 Jan 1997 09:59:47 +1100."
             <m0vp01j-0002VpC@enterprise.ce.com.au> 
Date: Wed, 29 Jan 1997 10:31:42 -0500
From: Stanley Gambarin <gambarin@OpenMarket.com>

> [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)

> 
> 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.
					Hope that was of some help.
							Stanley.

-- 
*******************************************************************************
* To unsubscribe from the fastcgi-developers mailing list		      *
* 		mailto: fastcgi-developers-request@openmarket.com      	      *
*		with body containing: unsubscribe       		      *
* To request help for using the fastcgi-developers mailing list		      *
* 		mailto: fastcgi-developers-request@openmarket.com      	      *
*		with body containing: help		       		      *
*******************************************************************************

*******************************************************************************
* Stanley Gambarin			Open Market Inc.		      *
* FastCGI (soon-to-be) Guru		245 First St. Cambridge MA 02142      *
*					(617) - 949 - 7487		      *
* mailto:gambarin@openmarket.com					      *
* 				http://acs2.bu.edu:8001/~stanleyg (school)    *
*				mailto:stanleyg@cs.bu.edu		      *
*******************************************************************************