Bug 25810 - Stage MARC records for import progress meter sticks at 0%
Summary: Stage MARC records for import progress meter sticks at 0%
Status: RESOLVED DUPLICATE of bug 26854
Alias: None
Product: Koha
Classification: Unclassified
Component: MARC Bibliographic record staging/import (show other bugs)
Version: 19.11
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-19 02:22 UTC by Andy Boze
Modified: 2020-10-29 02:54 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Gateway time-out error during staging records (105.46 KB, image/png)
2020-06-19 02:22 UTC, Andy Boze
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Boze 2020-06-19 02:22:07 UTC
Created attachment 106031 [details]
Gateway time-out error during staging records

This is somewhat similar to bug 1816 and bug 18719. We are using Koha 18.11 and upgrading to 19.11, and experience it in both versions.

We are importing large sets of biblios on a quarterly basis, around 70,000 records broken into files of 10,000. In the "Stage MARC for import" tool, after clicking the "Stage for import" button, the progress meter sticks at 0%. After about 90 seconds a popover message displays with a "504 Gateway Timeout" and an error saying that the import of records failed. The page doesn't update further, although after waiting a sufficiently long period of time, the "Staged MARC management" tool shows that the records have been staged.

We are using nginx as a load balancer, which is what I suspect causes the gateway timeout error. If the progress meter were receiving data to update it, this would probably prevent the timeout and the page would finish uninterrupted.

I'm attaching an image of the error.
Comment 1 David Cook 2020-10-29 02:54:28 UTC

*** This bug has been marked as a duplicate of bug 26854 ***
Comment 2 David Cook 2020-10-29 02:54:50 UTC
Fixing bug 26854 should fix this problem.