[
https://jira.nuxeo.com/browse/NXP-8694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=110106#comment-110106
]
Bruce Grant commented on NXP-8694:
----------------------------------
BTW - this has happened more than once on different DM/DAM 5.5 installs.
> Nuxeo 5.5 with DM/DAM Enabled - Asset blob pointers get re-hashed but on disk
> blobs remain in original hash
> -----------------------------------------------------------------------------------------------------------
>
> Key: NXP-8694
> URL: https://jira.nuxeo.com/browse/NXP-8694
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Core, DAM
> Affects Versions: 5.5
> Environment: Windows 7, DAM/DM 5.5, Postgres 8.4
> Reporter: Bruce Grant
> Priority: Blocker
>
> Installed a clean 5.5 with DM/DAM enabled - using Postgres 8.4 as the
> database. Added two JPG assets through the DAM importset interface and made a
> note of the four actual BLOBs created (original, thumbnail, medium and the
> EXIF data). These hashed to assets in the data directory of 8d/94, 9b/d3,
> 55/27, and eb/2d. Over a few days time I loaded/unloaded, navigated, ran in
> debug/standalone modes, made annotations, all in a structured manner. And
> everything was fine. Then today when I reloaded the server one of the assets
> I had annotated the previous day disappeared. Actually, the assets are still
> on disk hashed to the original locations. However the JPG asset in question
> now has a completely different ID and (obviously) a different hash. Following
> are the lines from the log file...
> 2012-01-20 17:24:58,711 WARN
> [org.nuxeo.ecm.core.storage.sql.DefaultBinaryManager] cannot fetch content at
> C:\nuxeo\demo\nuxeo-cap-5.5-tomcat-DAM\data\binaries\data\3d\5e\3d5e072a7d2cea1ad157bdc436ccc031
> (file does not exist), check your configuration
> 2012-01-20 17:24:58,713 WARN
> [org.nuxeo.ecm.core.storage.sql.DefaultBinaryManager] cannot fetch content at
> C:\nuxeo\demo\nuxeo-cap-5.5-tomcat-DAM\data\binaries\data\30\39\3039442583565bcf7dbb6bfd039381af
> (file does not exist), check your configuration
> 2012-01-20 17:24:58,716 WARN
> [org.nuxeo.ecm.core.storage.sql.DefaultBinaryManager] cannot fetch content at
> C:\nuxeo\demo\nuxeo-cap-5.5-tomcat-DAM\data\binaries\data\e5\04\e504ecfe06aa950b050fce98becc23a7
> (file does not exist), check your configuration
> 2012-01-20 17:24:58,720 WARN
> [org.nuxeo.ecm.core.storage.sql.DefaultBinaryManager] cannot fetch content at
> C:\nuxeo\demo\nuxeo-cap-5.5-tomcat-DAM\data\binaries\data\30\96\30960a1e6e765901f3069a75a4a9a94e
> (file does not exist), check your configuration
> For some reason the blob has a new ID but the on-disk asset doesn't reflect
> the change. Not sure what the root cause is OR which is the correct logic,
> but either way it's broken.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
ECM-tickets@lists.nuxeo.com
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
