While starting up AEM instance Getting 503 ERROR | Community
Skip to main content
Level 3
September 20, 2018
Solved

While starting up AEM instance Getting 503 ERROR

  • September 20, 2018
  • 3 replies
  • 12587 views

HTTP ERROR: 503

Problem accessing /. Reason:

    AuthenticationSupport service missing. Cannot authenticate request.
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vaibhavs7024655

rajs73651622 This is a very generic message and definitely not enough to point out the problem. However, this may signify some sort of repository inconsistency.

I would suggest you to check for SegmentNotFound errors in the error.log file and in case you find those you can refer to [1] in order to resolve the segment store inconsistencies.

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

3 replies

vaibhavs7024655
vaibhavs7024655Accepted solution
Level 3
September 20, 2018

rajs73651622 This is a very generic message and definitely not enough to point out the problem. However, this may signify some sort of repository inconsistency.

I would suggest you to check for SegmentNotFound errors in the error.log file and in case you find those you can refer to [1] in order to resolve the segment store inconsistencies.

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

sujeet_singhr48
April 13, 2021

It may also occur, if you are running AEM instance with a user other than expected user. For example, instance should start using aemuser but u are starting it with root user.

Level 1
January 18, 2023

Hi everyone.
This worked for me:


remove files:
/crx-quickstart/repository/segmentstore/repo.lock
/crx-quickstart/launchpad/felix/cache.lock

remove folder:
/crx-quickstart/repository/index/launchpad/config/org/apache/sling/jcr/repoinit

I hope this helps
Cheers

Rohan_Garg
Community Advisor
Community Advisor
March 9, 2023

Hi, I am not able to delete the repo.lock file as suggested -



 

 

 

April 25, 2023

turn of the server and try to delete it will work