Aspace-Preservica Objects not Syncing Automatically

[laurenb33]

A number of objects from Preservica/Aspace are not syncing automatically in Management Production. This is evident in recent batch processes for creation of new objects.

In the batch process in the link below, 66 out of 100 parent objects have a failure: https://collections.library.yale.edu/management/batch_processes/16562

Here is the message that is showing for a failed object: Request error 502 502 Proxy Error Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET/api/entity/content-objects/30f7f7dd-8130-40b1-944b-0adbe7d76342/generations/1/bitstreams/1/content. Reason: Error reading from remote server Additionally, a 502 Bad Gateway error was encountered while trying to use an ErrorDocument to handle the request.

After manually pressing the sync button, the objects have been syncing and showing accurately in DCS. The objects in the batch above have been manually synced, so they're working now.

Here is the link to an object that has this error, but has not been resynced: https://collections.library.yale.edu/management/parent_objects/33179743

This object is from the Papyri migration - some objects are getting the above 502 error; others are throwing: Checksum error Network timeout errors

[laurenb33]

Here's an update from @decirella on this issue:

For the 502 errors, there is a configuration change that the Preservation team identified to lengthen the KeepAlive time for API call responses from Preservica. We'll roll it out on Test first, Prod will most likely be next week. We'll keep the team posted.

Overall, these errors are either system-capacity based (the 502 errors, maybe the Aviary errors) or storage recall speed (papyri), the config change should definitely help with the former and have some positive effect on results with the later.