Bug #13051

AtoM Web Installer 504 timeout issue

Added by Steve Breker 5 months ago. Updated 5 months ago.

Status:NewStart date:05/23/2019
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Installation
Target version:Release 2.6.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

The sfInstallPlugin process has a long running fastcgi call (loaddata) that sets up the db schema, loads all settings, and populates the ES index on a new AtoM install. On some systems this task runs longer than NGINX's fastcgi_read_timeout default of 60 seconds triggering 504 timeout errors in the browser during the install process. Adding a fastcgi_read_timeout value of 120 in the nginx/sites-enabled/atom file in the index.php section gets rid of the error. On a test VBox VM it was taking about 1 min 15 secs to complete and producing 504 errors in the browser.

It is called from here:
https://github.com/artefactual/atom/blob/qa/2.6.x/plugins/sfInstallPlugin/modules/sfInstallPlugin/actions/configureSearchAction.class.php#L55

The long running server side tasks are run sequentially here:
https://github.com/artefactual/atom/blob/qa/2.6.x/plugins/sfInstallPlugin/modules/sfInstallPlugin/templates/loadDataSuccess.php

Break these tasks up so that they can each complete in less than the default fastcgi_read_timeout setting of 60 secs.
Possible to break out into separate controllers? Maybe remove the ES index task so that this can just be run manually afterwards using the CLI task (perhaps it's doing more than just a search:populate?)

It is possible to work around this 504 if it appears by just keying in the next uri in the sfInstall process. See thread here:

https://groups.google.com/d/msg/ica-atom-users/LKVkkvT1DkY/DTLXaKoABwAJ

History

#1 Updated by Steve Breker 5 months ago

  • Category set to Installation

Also available in: Atom PDF