Expand my Community achievements bar.

Join us in celebrating the outstanding achievement of our AEM Community Member of the Year!
SOLVED

AEM 6.5 HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.

Avatar

Level 3

Hi community

 

We are getting below error while restarting AEM

HTTP ERROR 503 AuthenticationSupport service missing. Cannot authenticate request.

AEM version 6.5 (on-premise)
SP 6.5.15

We have tried deleting below files and restarted still the issue persist

 

crx-quickstart/repository/segmentstore/repo.lock

crx-quickstart/launchpad/felix/cache.lock

crx-quickstart/repository/index

crx-quickstart/launchpad/config/org/apache/sling/jcr/repoinit

 

We have tried running oak-run-1.9.9 for offline compaction and finding good revision but its giving error

 

ERROR o.a.j.o.s.SegmentNotFoundExceptionListener - Segment not found: f015c6de-174b-41ea-ad44-785242643937. SegmentId age=169ms

org.apache.jackrabbit.oak.segment.SegmentNotFoundException: Segment f015c6de-174b-41ea-ad44-785242643937 not found

at org.apache.jackrabbit.oak.segment.file.AbstractFileStore.readSegmentUncached(AbstractFileStore.java:281)

 

Please suggest solution 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@adivj95 

 

You have already tried all the suggested options and the issue still persists.

 

If its a server, requesting you to please raise an Adobe ticket. They might be able to guide you on how to fix it or may revert to previous back-up


Aanchal Sikka

View solution in original post

3 Replies

Avatar

Community Advisor

can you check below points if you have verified?

  • Is this local or prod environment
  • can you make sure that oak-run jar version is correct for this SP of aem?
  • do you find journal.log inside crx-quickstart/repository/segmentstore 

normally oak-run.jar should be able to give you the good revision number for your repository and if not you can find the time stamp for each revision on journal.log which is machine readable and if you know the time your repository was correct you can reset the journal.log for that time by removing all the entry after that time stamp

also check https://www.nextrow.com/blog/adobe-experience-manager/restore-aem-instances-using-journal-log

 

Avatar

Correct answer by
Community Advisor

@adivj95 

 

You have already tried all the suggested options and the issue still persists.

 

If its a server, requesting you to please raise an Adobe ticket. They might be able to guide you on how to fix it or may revert to previous back-up


Aanchal Sikka

Avatar

Administrator

@adivj95 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni