FAQ  |  Search  |  Register  |  Profile  |  Log in to check your private messages  |  Log in

fastcgi.log: Finding timeout culprits

 
Post new topic   Reply to topic    Aprelium Forum Index -> General Questions
View previous topic :: View next topic  
Author Message
lestat
-


Joined: 15 Sep 2003
Posts: 127

PostPosted: Wed Nov 10, 2010 6:49 pm    Post subject: fastcgi.log: Finding timeout culprits Reply with quote

Hi all.

I've been finding my fastcgi.log full of timeout errors. It's been that way for quite a while. I've only recently discovered I can use this log to find busted scripts etc.

The errors look like so:
Code:

10/Nov/2010:11:00:02 -0600   SUID: 2301   PUID: 2301   RUID: 0   URI:    Reading 0 bytes failed = The process cannot access the file because it is being used by another process.
10/Nov/2010:11:00:02 -0600   SUID: 2301   PUID: 2301   RUID: 0   URI:    timeout-header2!


Usually repeated probably 10 times per day. I'm assuming I have a runaway script causing such a problem. Server runs mainly as an intranet running php. How can I use this information to track this down?

Thanks for any suggestions.
_________________
XP Pro sp2
Abyss Web Server X2 (v 2.9.3.5)
PHP 5.3.8
Back to top
View user's profile Send private message MSN Messenger
sckds
-


Joined: 05 Nov 2005
Posts: 6

PostPosted: Thu Nov 11, 2010 1:25 pm    Post subject: Reply with quote

this is fastcgi bug

everytime u create a new php-cgi.exe
it will have these logs

if u want less these logs , extend the fastcgi timeout time
Back to top
View user's profile Send private message
lestat
-


Joined: 15 Sep 2003
Posts: 127

PostPosted: Fri Nov 12, 2010 3:13 pm    Post subject: Reply with quote

Thanks sckds.

Quote:
if u want less these logs , extend the fastcgi timeout time

Is this the setting in:
Console:edit hosts:scripting parameters:FastCGI Parameters:FastCGI Process Timeout ? If so I can change this no problem.

Quote:
everytime u create a new php-cgi.exe

How exactly is a new php-cgi.exe "created". I don't know too much about servers.

Since this is a bug of fastCGI, is changing the timeout time a workaround for some scripts gone awry, or a remedy for cgi bug? I'd like to make sure I'm not just creating a workaround for something I'm not doing "properly"

Thanks!
Back to top
View user's profile Send private message MSN Messenger
Display posts from previous:   
Post new topic   Reply to topic    Aprelium Forum Index -> General Questions All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB phpBB Group