| Issue Number | 4474 |
|---|---|
| Summary | Media Document Hot-fix |
| Created | 2018-05-15 16:17:58 |
| Issue Type | Bug |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2018-05-18 13:21:04 |
| Resolution | Cannot Reproduce |
| Path | /home/bkline/backups/jira/ocecdr/issue.226115 |
When a modified media file (image) is being hot-fixed the document
gets created but not pushed to Gatekeeper.
It appears the diff applied to media documents isn't working correctly
at the moment.
Media documents can still get "hot-fixed" by running the "Republish" option of the Admin interface.
Examples, please?
Here are a few media docs that were hot-fixed yesterday.
779383
781921
779378
779381
~volker: I'm trying to dig into the push jobs for this ticket, and I'm hoping you can give me some help interpreting the failure messages I'm seeing; e.g.:
[2018-05-16 15:02:27.416000] HTTP error: 404 (Not Found) (occurred at Wed May 16 15:02:27 2018) (<!DOCTYPE html> <html> <head> <title>The resource cannot be found.</title> <meta name="viewport" content="width=device-width" /> <style> body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } @media screen and (max-width: 639px) { pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; } } @media screen and (max-width: 479px) { pre { width: 280px; } } </style> </head> <body bgcolor="white"> <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1> <h2> <i>The resource cannot be found.</i> </h2></span> <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif "> <b> Description: </b>HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. <br><br> <b> Requested URL: </b>/GateKeeper/GateKeeper.asmx<br><br> </body> </html> )It appears the diff applied to media documents isn't working correctly at the moment.
Can you provide some of the clues that lead to this conclusion? I've looked pretty carefully at the code, and it sure looks like it's making the determination as to whether the media itself has changed. It's true that there are no changes you can make to the XML Media document (other than the media type) which would result in a re-push of the media "document" as long as the bytes for the blob are the same, but that's as it should be, because there's nothing in the XML Media document (other than the media type) which ends up being pushed to the GateKeeper.
Are you seeing this error now? It was a problem on PROD yesterday until about 4pm when Blair fixed it.
~oseipokuw, you
mentioned in your email yesterday there was a problem with the
versioning of the media documents. That sounds to me there may not be a
problem with the publishing software after all.
Could you please run again the hot-fix you did yesterday? If this runs
successfully the publishing software is fine.
The error you saw yesterday with the push was unrelated.
I see that 14 out of the 16 image files published have been successfully pushed to gatekeeper and processed.
It looks to me that everything has worked as expected. Can you confirm, ~oseipokuw?
Yes, I received the two expected notifications and the Doc History indicates that the media docs were pushed to Cancer.gov. I will check the affected summaries to see if they have been updated accordingly.
Elapsed: 0:00:00.000505