Any ideas? I was under the impression that "IPCCommTimeout" was what was causing the timeout... But even setting it to 7200 didn't help.

Click to expand...

You are correct, this is the right directive for setting the fastCGI timeout. However, in many installations, this directive is is placed in several config files, and the last one wins. So unless you hit by chance the last place where this parameter is set, you are screwed.

It took me about a day's work to I finally figure out where to put this directive in a Debian/Linux system managed under Plesk. The files is
/var/www/vhosts/<yourhostname>/vhost.conf

This file vhost.conf will usually not exist, unless you have already done some non-standard vhost configuring already. So you need to create it.

Then just put contents like:

# set time limit to be greater than the longest reasonable php module
# execution time
#
# Note: some (drupal..) modules advertize themselves as long and tell you
# to tweak php set_time_limit(). But this is ineffective by itself, unless you
# are running PHP as a module. For PHP in CGI and FasCGI modes, the
# shorter of the php time limit and cgi time limit will win, so you need to
# relax both constraints