If your system configuration has a low timeout threshold that is impacting your index build and sync, you may see a message in AdminCP on the Threadloom options page. Below, we list both a simple workaround, as well as more involved approached for permanently addressing this.
Change frequency of index sync
The simplest workaround for FastCGI and other server timeouts is to increase the frequency of your index sync from its default of once per hour, to once every 15 minutes.
- Go to AdminCP > Scheduled Tasks > Scheduled Task Manager.
- Find the "Threadloom Search Sync" scheduled task and under "Edit", click Go.
- On the edit page for the "Threadloom Search Sync" scheduled task, find Minute and select 15-minute intervals. So, for instance, if the first dropdown says "39" (as in the screenshot, meaning that it's set to sync every hour at Minute 39), then in the dropdowns next to it, select 54, 9, and 24. (Or if the math gives you a headache, 0/15/30/45 are fine, too.)
- Click Save.
- Go to AdminCP > Tools > Cron Entries.
- Find and click on "Threadloom Sync."
- Under Run at minutes, select 15-minute intervals. To select multiple values, hold down Ctrl (Windows) or Cmd (Mac) while selecting the interval minute value. So, for instance, if "21" is currently selected, add 36, 51, and 6. (Or, again, 0/15/30/45 are fine, too.)
- Click Save.
If you are running cgi-fcgi, you may see a suggestion to modify FcgidBusyTimeout and FcgidIOTimeout to 3000.
How do I tell if my server is running FastCGI?
Check your PHP start page, or off of your forum root directory, browse to /phpinfo.php. Look for CGI. If you see FastCGI next to it, you’re running FastCGI. Here is a sample screenshot:
How do I modify my FastCGI timeouts using WHM/cPanel?
If you are using mod_fcgid, go to WHM > Apache Configuration > Include Editor, and under the "Pre VirtualHost Include" section, enter the following:
Once you click update, it will ask you to restart Apache. Restart, and your new timeouts should be in effect.
How do I modify my FastCGI timeouts manually?
Steps will vary depending on your server OS and configuration. Most of the steps below have not yet been veririfed, so please proceed with caution. We will update this section as we confirm various configurations.
If you are using:
- (verified) mod_fcgid: Update FcgidBusyTimeout and FcgidIOTimeout to 3000 (seconds, or 50 minutes). These settings are often in your fcgid.conf or httpd.conf files.
- (not yet verified) mod_fastcgi: Update appconntimeout and idle-timeout to 3000.
- (not yet verified) mod_proxy_fcgi: Update ProxyTimeout or timeout to 3000.
- Note: ServerPilot uses mod_proxy_fcgi; however, ServerPilot’s FastCGI timeouts are by default configured to one hour. This is sufficient for most forums with fewer than 3 million posts. If your forum is larger, drop us a line.
- (not yet verified) ngx_http_fastcgi_module: Update fastcgi_read_timeout to 3000. This setting is typically in your timeout.conf file.
- (not yet verified) ngx_http_proxy_module (nginx as proxy, PHP-FPM disabled): Update proxy_connect_timeout, proxy_send_timeout, proxy_read_timeout, and send_timeout to 3000. These settings are typically in your timeout.conf file.
How do I disable FastCGI on a GoDaddy VPS?
If you are running Lite Speed, view this article for configuration instructions for Threadloom.
PHP safe mode
If you are running PHP in safe mode, you may see a suggestion to modify max_execution_time in php.ini to 3000 (seconds).