On 1-jul-2007, at 16:14, Dirk van Oosterbosch, IR labs wrote:
> This is the code I am using:
> http://dpaste.com/hold/13336/
>
I narrowed down the moment the extra processes are spawned by FastCGI
to be here:
form = UploadForm({'name1': slots[0]['name'], 'name2': slots[1]
['name'], 'name3': slots[2]['name']})
if request.method == 'POST':
>> here
if not (('poster' in request.FILES) or ('movie' in
request.FILES)):
form = UploadForm(request.POST)
Between line 174 and 175 of the code posted on dbpaste.
The log says:
[Sun Jul 01 20:58:23 2007] [warn] FastCGI: (dynamic) server "/domains/
ouwepikouwepijp.nl/www/mysite.fcgi" (uid 2195, gid 2063) restarted
(pid 59128)
That new process (pid 59128) then seems not be active at all, just
sitting there consuming memory and filling up my shared resources.
My guess is that while the upload data is coming in via the POST,
FastCGI sees the orginal process takes longer than normal to finish
or maybe even looks stalled (because the upload is not completely
received). And because of that FastCGI is restarting, creating a new
thread.
With the ultimate unfortunate consequence of returning nothing but
error 500.
Does anybody has an idea of how to tell FastCGI not to do that?
best
dirk
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
