| Issue Number | 3915 |
|---|---|
| Summary | Error Publishing Media Document |
| Created | 2015-05-27 15:54:44 |
| Issue Type | Bug |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | alan |
| Status | Closed |
| Resolved | 2015-07-09 16:19:24 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.162008 |
There is a new media document on PROD that is failing to be published
since Friday. The media file itself gets created but the file is empty.
The document is CDR725190, the error message displayed is:
"Failure writing CDR0000725190.jpg: must be string or buffer, not
None"
Doesn't look as if any version of the document got saved with the blob (that is, there's a row in the doc_blob_usage table for 725190, but none in the version_blob_usage table).
I've asked CIAT to try and version the document again. I'm guessing that's when the version_blob_usage table gets populated.
~oseipokuw: Can you create a new version for this, making sure that the blob is included? Thanks.
It looks like this has been done and this media doc was published to Cancer.gov on 6/25, so I think this issue can now be closed. Alan, can you please confirm? Thanks.
Looking at the database and the document version history it appears that the problem with this document was resolved by Linda. No further action by William is required.
There have now been 8 versions of the Media document and 3 versions of the associated blob. According to what we have in the database, the first three versions of the Media document had no blob (i.e., image) associated with them, but the third one was marked publishable. The first Media doc version for which we have a blob was version 4, created by Linda very shortly after Bob requested it. The first Media doc publishable version with an associated blob was version 8, saved on June 25 and published multiple times since then.
So, indeed, the problem with this particular document is resolved.
I can think of two possible ways that the problem could have arisen. The least likely one, I think, is that one or more blob references were lost among the first three Media doc versions.
A more likely one is that no blob was saved for the first three Media doc versions, but our validation software doesn't check for a blob actually existing as a requirement for a Media document to be publishable. I can see why that would happen. It's not a schema issue and it's not something our link software can handle as it is now since there is no software for handling validation of links from an XML document (the Media doc) to a database object that is not a document (the image blob).
If we need to fix that, we should create a new issue. I don't think it will be extremely hard, but not extremely simple either.
Elapsed: 0:00:00.001199