Author Topic: import timeouts (fastcgi nginx) - can we be cleverer about stopping them? (Read 1113 times)

Michael McAndrew · March 14, 2012, 12:40:12 pm

Hey there,

Was doing an import via the UI (ooh, crazy, I know, but) and I was getting timeout issues.

So I increased the fastcgi_read_timeout from 60 to 600.

My script then timed out at about 80%.

So then I increased the fastcgi_read_timeout from 600 to 6000 (aka 100 minutes - I don't reckon I'll be doing any UI imports that last longer than that).

When I was looking at the http://wiki.nginx.org/HttpFcgiModule#fastcgi_read_timeout docs, I saw that the docs say

"Directive sets the amount of time for upstream to wait for a fastcgi process to send data. Change this directive if you have long running fastcgi processes that do not produce output until they have finished processing. If you are seeing an upstream timed out error in the error log, then increase this parameter to something more appropriate."

The bit that stuck out was "that do not produce output". I am wondering if we can get our import script to ping back periodically to stop this happening. Thus allowing us to not worry about setting a setting like 100 minutes which seems a bit risky.
My nginx config is as follows:

Donald Lobo · March 14, 2012, 01:31:58 pm

import is actually two processes:

1. The one on the web, which periodically uses an ajax script to go to the web and refresh the status

2. A background AJAX initiated process which does the import and periodically writes the status file which the browser ajax process reads

would be great if you'll can experiment with a similar setup (using sleep etc) and see what needs to be done

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: import timeouts (fastcgi nginx) - can we be cleverer about stopping them? (Read 1113 times)

Michael McAndrew

import timeouts (fastcgi nginx) - can we be cleverer about stopping them?

Donald Lobo

Re: import timeouts (fastcgi nginx) - can we be cleverer about stopping them?