SegmentNotFound Exception

Avatar

Avatar
Ignite 3
Employee
venkateshs73486
Employee

Likes

10 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Ignite 3
Employee
venkateshs73486
Employee

Likes

10 likes

Total Posts

32 posts

Correct reply

1 solution
Top badges earned
Ignite 3
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
venkateshs73486
Employee

23-09-2019

Team,

Our client face SegmentNotFoundException in their environment which is in 6.4.5.

while we know the standard adobe solution for this. ( i.e running oak-run command), we would like to know the rootcause for this.

Any guidance?

One of the Adobe docs mentioned that online tar compaction may have removed the segment. Is it possible?

We believe that this process would not remove the segments which are in usage.

Replies

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

23-09-2019

Try to go through the logs and find the first entry for segmentnotfound. Analyze 10-15 lines before the segmentnotfound error and you can see which request caused this issue.

Avatar

Avatar
Boost 5
Employee
tanyakapila
Employee

Likes

9 likes

Total Posts

13 posts

Correct reply

3 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile

Avatar
Boost 5
Employee
tanyakapila
Employee

Likes

9 likes

Total Posts

13 posts

Correct reply

3 solutions
Top badges earned
Boost 5
Boost 3
Boost 1
Applaud 5
Affirm 3
View profile
tanyakapila
Employee

23-09-2019

Hi venkateshs73486425 ,

A SegmentNotFoundException is returned when a segment is not present while any activity attempts to read the node. There can be different root causes for this:

1.The segment has been removed by manual intervention (e.g. rm -rf /).

2.The segment has been removed by revision garbage collection.

3.The segment cannot be found due to some bug in the code.

We had some issues with online tar compaction with 6.2 & early versions. We even advised to disable online tar compaction in <6.3 . The documents you might have referred might be for previous versions.

Avatar

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

103 likes

Total Posts

240 posts

Correct reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile

Avatar
Contributor
Employee
hamidk92094312
Employee

Likes

103 likes

Total Posts

240 posts

Correct reply

38 solutions
Top badges earned
Contributor
Shape 1
Ignite 1
Give Back 50
Give Back 5
View profile
hamidk92094312
Employee

23-09-2019

there are variety if reasons for this situation. It might be caused due to long running JCR sessions along with online compaction [1]. It can be caused by some older issues in Oak [2], ... etc. So the logs should shed some lights on the probable cause(s).

[1] Fix Inconsistencies by restarting AEM when SegmentNotFound Issue is reported in AEM 6.3

[2] Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

23-09-2019

Listing the common reasons for Segmentnotfound:

  • Unclean shutdown Or Force Shutdown using the kill command
  • AEM instance running out of memory
  • Antivirus updating the tar files. You need to exclude "crx-quickstart" from antivirus scan.
  • An issue with the disk where the segment is stored as tar file.

Avatar

Avatar
Give Back 5
Employee
SonDang
Employee

Likes

17 likes

Total Posts

43 posts

Correct reply

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

Avatar
Give Back 5
Employee
SonDang
Employee

Likes

17 likes

Total Posts

43 posts

Correct reply

9 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 5
View profile
SonDang
Employee

23-09-2019

If none of these possibilities could explain why you got the SNFE, I would recommend opening a ticket with the support team to assist further. If you have a reproducible scenario, it would be even better.