How to fix error InputStream for blobId not found?

Avatar

Avatar
Level 1
at_mahajan23
Level 1

Likes

0 likes

Total Posts

8 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
at_mahajan23
Level 1

Likes

0 likes

Total Posts

8 posts

Correct reply

0 solutions
View profile
at_mahajan23
Level 1

24-08-2020

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.

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,134 likes

Total Posts

3,161 posts

Correct reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,134 likes

Total Posts

3,161 posts

Correct reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

24-08-2020

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.

Answers (4)

Answers (4)

Avatar

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Vish_dhaliwal
Employee

24-08-2020

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

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

25-08-2020

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

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile
SundeepKatepally
Level 4

24-08-2020

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

Avatar
Boost 250
MVP
Nikhil-Kumar
MVP

Likes

251 likes

Total Posts

262 posts

Correct reply

38 solutions
Top badges earned
Boost 250
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile

Avatar
Boost 250
MVP
Nikhil-Kumar
MVP

Likes

251 likes

Total Posts

262 posts

Correct reply

38 solutions
Top badges earned
Boost 250
Validate 1
Ignite 3
Ignite 1
Give Back 5
View profile
Nikhil-Kumar
MVP

24-08-2020

@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