Invalid PDF structure errors after Prov upgrade

alcoma

After updating Providence from 2.0.9 to latest, I've noticed that many pdfs are throwing the error (in viewer):

Invalid or corrupted PDF file. More Information

PDF.js v2.4.456 (build: 228a591c)
Message: Invalid PDF structure.

I can see the thumbnail in object records, but if clicked on, the viewer shows this error. I thought it was only happening with one corrupt file but as I started browsing records with pdf reps, I'm seeing the same thing for a lot of objects, even ones I know were viewable before. What's interesting is that some of these pdfs that won't load in the Providence viewer can be viewed on the Pawtucket side. However, some of them also do not load at all in the viewer on the Pawtucket side, but thumbnails are seen.

Media Display conf shows the default pdfjs viewer. I haven't changed any settings in app.conf but don't have anything set under Media processing tweaks.

alcoma

An update: In changing the display version from compressed to original in media_display conf, the error quoted above went away but there is still no actual pdf file to view. I have been discovering that even though the media rep fields show meta for the file (name, size, etc.) the file does not exist in the media directory. I've tried using some of the caUtils commands to troubleshoot (like reprocess media for specific rep id) but nothing really happens even though the progress bar shows 100% right away and no errors are presented. Makes sense if there is no file, but why is the database retaining info about the upload ?

Is there a bulk way to find representations that are missing original media files ?