A delay in the writing of the results file (results.zip) to the shared file system can cause one or more of the following errors leading to a failure of batch analysis:
Timeout: File is not a valid zip file ...results.zip
URL is not a file: ...results.zip
In vesions of ColumbusPlus up to 2.8.2 the following file on the server can be modified to increase the amount of time before reading the results.zip file:
/usr/local/PerkinElmerCTG/Columbus2.8/webapp/columbus/cluster/tasks.py
Change line 173 from
submit_results_to_columbus.apply_async((job, cluster_conf_dir),
countdown=5)
to
submit_results_to_columbus.apply_async((job, cluster_conf_dir),
countdown=30)
This example increases the countdown time to 30 seconds, though it may need to be increased further. After changing restart Columbus for changes to take effect
$ /etc/init.d/columbus restart
In versions above 2.8.2 (i.e soon to be released 2.9.0) the strategy to check the results is changed further. It features as timeout on line 50 of aforementioned file, however in light of new strategy it is highly unlikely this value need to be changed but is shown here for reference.