Expand my Community achievements bar.

SOLVED

How to fix error InputStream for blobId not found?

Avatar

Level 2

Hi 

 

I am using AEM 6.4 , and it is observed that we have getting frequently below error 

Error occurred while obtaining InputStream for blobId {.....}.

How can I fix this error and if i did not found blob id  related files , then how can i remove this reference from repository.

 

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

If you get these types of errors, you have an inconsistency between the datastore and the segmentNodeStore. That's unfortunate and it shouldn't happen at all. Is this a shared file datastore?

I recommed to contact Adobe support, let them know about this issue and ask if they can assist with performing a consistency check.

View solution in original post

7 Replies

Avatar

Community Advisor

@at_mahajan23 
Try generating the report for the references to the Id that you mentioned using query or use

Nikhil_Kumar_AEM_0-1598285584811.png
Or the best would be to go with ACS AEM Commons Report generator: http://localhost:4502/apps/acs-commons/content/reports.html

Nikhil_Kumar_AEM_1-1598285736785.png

Thanks,
Nikhil

 

 

Avatar

Correct answer by
Employee Advisor

If you get these types of errors, you have an inconsistency between the datastore and the segmentNodeStore. That's unfortunate and it shouldn't happen at all. Is this a shared file datastore?

I recommed to contact Adobe support, let them know about this issue and ask if they can assist with performing a consistency check.

Avatar

Employee

Hello,

 

You can start with datastore consistency check [1] and then recover the missing files or cleanup references using steps mentioned in helpx doc [2]

Use oak-run export option [3] to create a json file "nodestates.json" in the output dir containing nodes content in json format. Then, you can search BlobIDs in the generated json.

Example command: java -jar oak-run-x.x.x.jar export -p /  --fds-path=crx-quickstart/repository/datastore  crx-quickstart/repository/segmentstore  -b=true

 

[1] https://helpx.adobe.com/ca/experience-manager/kb/How-to-run-a-datastore-consistency-check-via-oak-ru...

[2] https://helpx.adobe.com/ca/experience-manager/kb/oak-blobstore-inconsistency-blobId.html

[3] https://github.com/apache/jackrabbit-oak/tree/trunk/oak-run

Regards,

Vishu

 

Avatar

Level 2

@Vish_dhaliwal

How can I  clean the  entries of blobid which are not found on author instance. I don't have missing files in Any back.

Hence I  want to clean it so that it would not refer for any activity.

 

Thanks

Atul

Avatar

Community Advisor

No matter whatever you do , very difficult to get rid of this issue. If its lower environment or local instance create a fresh instance and reinstall the content and code. If its production you can follow the process to recover.

 

I am suggesting to recreate the instance for Lower and local environment - Because it will save lot of time.

Avatar

Employee

Hi @at_mahajan23,

If you see an error the one below this in the AEM logs then it is likely you are experiencing a bug with Datastore GC cleaning up files that are in use.  If you are using a FileDataStore then see this article for details on how to repair the corruption.

 

10.09.2015 10:38:04.220 *ERROR* [pool-9-thread-3] org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job execution of org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate@7fe7e8fa : Error occurred while obtaining InputStream for blobId [add1dd8fc5093b27b1fae1b753cb48b24ef3231f#101983]
java.lang.RuntimeException: Error occurred while obtaining InputStream for blobId [add1dd8fc5093b27b1fae1b753cb48b24ef3231f#101983]

 

https://helpx.adobe.com/experience-manager/kb/oak-blobstore-inconsistency-blobId.html

 

Thanks!!

Avatar

Level 1

Replaying too late, but as I encountered this error recently, would like to share if someone else has the same issue.

My blobIds got corrupted while trying to deploy the project with wrong Ports configuration. Afterwards when running with correct Ports configuration, I've encountered this error. 
Luckily it was local ENV, there was no other fix then creating fresh instance.