Getting an error after restarting the server that "Possible reason is missing Repository service. Check AuthenticationSupport dependencies" | Community
Skip to main content
sundarramanr306
sundarramanr306
Level 2
June 8, 2017
Solved

Getting an error after restarting the server that "Possible reason is missing Repository service. Check AuthenticationSupport dependencies"

  • June 8, 2017
  • 5 replies
  • 19275 views

Hi,

I restarted the server by stopping it, checked if any process is running and then started it again. It showed that it is started but the server is not up. I checked the logs and it shows the following error:

GET / HTTP/1.1] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request.

org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

I checked the memory usage and it is fine(47% used)

Does anybody have an idea why this error is coming and why the server is not up?

    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 cmsh43398811

    After deleting index if its not recoverable then there are some issue with your tar balls.

    The best way to recover using oak-run

    java -jar /tmp/oak-run-*.jar checkpoints /crx-quickstart/repository/segmentstore

    java -Dtar.memoryMapped=true -Xms8g -Xmx8g -jar /tmp/oak-run-*.jar  check -d1 -p /crx-quickstart/repository/segmentstore

    [main] INFO  o.a.j.o.p.s.f.t.ConsistencyChecker – Found latest good revision 12b60e9c-ecb9-45ae-a863-2ba1f467bb53:261684

    4) Revert the repository to this revision by editing ./crx-quickstart/repository/segmentstore/journal.log and deleting all lines after the line containing the latest good revision.

    I.e. after 12b60e9c-ecb9-45ae-a863-2ba1f467bb53:261684 The bad one (which is bd57b402-6579-4f00-a9b7-24b30a954db0:261492)

    5)Save journal.log file.

    6) Delete the file ‘repo.lock’ and restart server.

    5 replies

    Sh1ju
    Sh1ju
    Level 4
    June 9, 2017

    Are you using S3 DataStore ?

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    June 12, 2017

    1. Stop your instance.

    2.go to > crx-quickstart\repository\index and delete index folder.

    3. Restart the instance

    Reference post :-

    ~kautuk

    Kautuk Sahni
      sundarramanr306
      sundarramanr306Author
      Level 2
      June 12, 2017

      Hi Kautuksahni,

      This has been done already but still it is showing the same. Is there a possibility that the AEM JAR is corrupted?

      C
      cmsh43398811Accepted solution
      June 12, 2017

      After deleting index if its not recoverable then there are some issue with your tar balls.

      The best way to recover using oak-run

      java -jar /tmp/oak-run-*.jar checkpoints /crx-quickstart/repository/segmentstore

      java -Dtar.memoryMapped=true -Xms8g -Xmx8g -jar /tmp/oak-run-*.jar  check -d1 -p /crx-quickstart/repository/segmentstore

      [main] INFO  o.a.j.o.p.s.f.t.ConsistencyChecker – Found latest good revision 12b60e9c-ecb9-45ae-a863-2ba1f467bb53:261684

      4) Revert the repository to this revision by editing ./crx-quickstart/repository/segmentstore/journal.log and deleting all lines after the line containing the latest good revision.

      I.e. after 12b60e9c-ecb9-45ae-a863-2ba1f467bb53:261684 The bad one (which is bd57b402-6579-4f00-a9b7-24b30a954db0:261492)

      5)Save journal.log file.

      6) Delete the file ‘repo.lock’ and restart server.

        jezwn
        jezwn
        Level 5
        October 9, 2019

        I'm getting this error on running, java -jar /tmp/oak-run-*.jar checkpoints /crx-quickstart/repository/segmentstore


        Unable to access jarfile /tmp/oak-run-*.jar

          Terms & ConditionsAccessibility statement

          Loading footer...