SDK local instance - Restart - Error 503 authentication | Community
Skip to main content
A
ancara
Level 2
December 16, 2021

SDK local instance - Restart - Error 503 authentication

  • December 16, 2021
  • 4 replies
  • 9697 views

Hi!

I am working with an author instance. I have a sdk file and I have created a new instance, without any content or additional configuration, it's an empty and clean instance. I restart it and it does not work again. 503 service unathorized error is thrown.

 

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

 

I have not tried to fix repository or index because it does not have sense on an clean instance, but I do not understand which mistake breaks my instance.

Any suggestions?

Thanks!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

Pavan_Kalyan-1
Pavan_Kalyan-1
Level 3
December 16, 2021

Hi @ancara 

The 503 error Basically Indicates sling not able to connect to repository. It may be corruption Or last install broke it.

try these steps

  1. try accessing your crx/de if that redirection works login there check if any package is showing an error
  2. go to your system/console/bundles and see if all your bundles are in active state.
  3. if you don't find any issues anywhere there must be a mismatch in the versions you are using (eg: using java 11 for aem 6.4) .
  4. if your a backup of your project in your local, then you can turn off your AEM instance and delete your quickstart and do a fresh install.

try these and update us.

thanks

    A
    ancaraAuthor
    Level 2
    December 16, 2021

    Thanks for your suggestions!!

    It is a strange behavior. I have a clean instance with SDK version (2021.9.5852.20210917T073206Z-210800) and I have java 11. 

    I have created a mvn project with archetype and when I compile, my instance fails. 

    I have all bundles active, I have deleted index folder, but I can not start instance correctly again. It is a bit frustrating because everything is clean (project and instance) and when I compile, instance dead and I have to generate another. 

     

    Thanks!

      Pavan_Kalyan-1
      Pavan_Kalyan-1
      Level 3
      December 16, 2021

      do you see any error message in your error.logs file.? (located in quickstart/logs/error.logs file),

      this might give us the reason for this issue.!

      if not just delete your quickstart and do a fresh install

       

        Shubham_borole
        Community Advisor
        Shubham_boroleCommunity Advisor
        Community Advisor
        December 16, 2021

        @ancara 

        503 service unathorized error may indicate a corrupt instance. 

        However if possible can you also try to switch to java 8 and see if same issue exists?

          A
          ancaraAuthor
          Level 2
          December 17, 2021

          Hi! I can not use java 8, AEM as Cloud Service (my instance is a SDK file jar) requires at least Java 11 .  Thanks for your suggestion!.

            Raja-Karuppsamy
            Community Advisor
            Raja-KaruppsamyCommunity Advisor
            Community Advisor
            January 5, 2022

            @ancara Looks like repository is corrupted. Please change the ERROR log level to DEBUG and the tail the logs.

            1. Check whether your Apache Sling Authentication Service Bundle is active or not (http://localhost:4502/system/console/bundles/)- if not active then try to activate it manually.
            2. Stop the AEM instance - Go to folder crx-quickstart/repository/remove folder index -> Start the AEM
            3. Go for a re-indexing - http://www.wemblog.com/2011/12/how-to-rebuild-index-in-cq5-wem.html"
            4. Delete the file if exist -> /author/crx-quickstart/launchpad/felix/cache.lock

             

            Regards,

            Raja

              A
              ancaraAuthor
              Level 2
              March 17, 2022

              Hello,

               

              Finally I found what breaks my instance. When a project is created, there is a configuration file which when you restart instance breaks it. 

               

              Related info:  github.com/adobe/aem-project-archetype/issues/852

               

              Thanks all!

              Terms & ConditionsAccessibility statement

              Loading footer...