Local AEM instance won't start (500 error) | Community
Skip to main content
Codelime
Level 4
May 4, 2021 1:39 PM UTC

Local AEM instance won't start (500 error)

My local AEM instance has been working fine, but suddenly won't start. I restarted Docker, restarted my PC, updated and restarted Docker again, but I get HTTP ERROR 500:

 

localhost is currently unable to handle this request.

HTTP ERROR 500
 
I have Docker v20.10.5 running with aemdesign/aem started. CRXDE Lite opens but it's blank. Any ideas on what could be the cause?

35 replies

CodelimeAuthor
Level 4
May 5, 2021 12:27 PM UTC

This appears to be the culprit. If anyone knows how to fix, please let me know. Thanks.

Caused by: java.io.IOException: Unable to get component of class 'interface org.apache.sling.rewriter.Transformer' with type 'versioned-clientlibs'.

 

Translate
    Ritesh_Mittal
    Ritesh_Mittal
    New Participant
    May 5, 2021 12:53 PM UTC
     

    @codelime  Just install ASC commons versioned clientlib rewriter package or delete rewriter config node under /apps/project/config/rewriter.

     

    https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html

    Translate
      CodelimeAuthor
      Level 4
      May 5, 2021 12:59 PM UTC

      Thanks for the suggestions. Is /apps/project/config/rewriter a URL or a physical folder in File Explorer?

      Translate
        CodelimeAuthor
        Level 4
        May 5, 2021 11:49 AM UTC

        The error.log (http://localhost:4502/system/console/slinglog/tailer.txt?tail=1000&grep=*&name=%2Flogs%2Ferror.log) is now showing data:

        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Error while sending request: java.net.ConnectException: Connection refused (Connection refused)
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish ------------------------------------------------
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Sending message to localhost:4503
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> POST /bin/receive HTTP/1.0
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Action: Activate
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Referer: about:blank
        05.05.2021 11:40:50.228 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-19-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> ...spooling 104347 bytes...
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Error while sending request: java.net.ConnectException: Connection refused (Connection refused)
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish ------------------------------------------------
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish Sending message to localhost:4503
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> POST /bin/receive HTTP/1.0
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Action: Activate
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> Referer: about:blank
        05.05.2021 11:41:50.282 *ERROR* [sling-threadpool-c22b1d3e-9a33-48da-a8e2-de80197a7f71-(apache-sling-job-thread-pool)-20-com_day_cq_replication_job_publish(com/day/cq/replication/job/publish)] com.day.cq.replication.Agent.publish >> ...spooling 104347 bytes...

        Translate
        CodelimeAuthor
        Level 4
        May 5, 2021 11:26 AM UTC

        I've searched and cannot find an error.log file or a crx-quickstart folder. When I navigate here (http://localhost:4502/system/console/slinglog/tailer.txt?tail=10000&grep=*&name=%2Flogs%2Ferror.log), I get a blank page. Status Sling Settings shows this, but how can I navigate to this in my File Explorer? 

        Sling Home = /aem/crx-quickstart
Sling Home URL = file:/aem/crx-quickstart/

          

        Translate
          Ritesh_Mittal
          Ritesh_Mittal
          New Participant
          May 5, 2021 6:24 AM UTC
           

          @codelime ,

           

          Can you share your error.log file, which will be in your local file system, like below-

           

          Translate
            chintan97patel
            chintan97patel
            Level 2
            May 5, 2021 12:38 AM UTC

            Hi @codelime ,

            Can you check if your code bundle is active? Go to http://localhost:4502/system/console/bundles and search for your code bundle and make sure it is active.

            Translate
              CodelimeAuthor
              Level 4
              May 5, 2021 1:50 AM UTC
              Yes, it's active. I did a complete reboot of my system, started Docker, opened Eclipse, re-deployed using Maven in Eclipse, started the AEM server in Eclipse, made sure the bundle was active, etc.
              Translate
                BrianKasingli
                BrianKasingli
                New Participant
                May 4, 2021 10:23 PM UTC

                It seems like you have tried many things. Why don't you try to change the crx-quickstart folder name to something else, and then re-execute the .jar file? Even better, why don't you grab a working state of docker from your colleagues docker image; this is actually recommended, as all developers will have the same docker setup for devleopment.

                Translate
                  CodelimeAuthor
                  Level 4
                  May 4, 2021 11:39 PM UTC
                  Thanks for the suggestion. Could you go into more detail on the first suggestion (changing the folder name)? Also, to re-execute the .jar file, is that simply restarting Docker?
                  Translate
                    CodelimeAuthor
                    Level 4
                    May 4, 2021 7:39 PM UTC

                    I found the sling.properties file, which hasn't been modified anytime recently:

                     

                    sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
                    sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.*
                    org.apache.sling.commons.log.file=""
                    org.apache.sling.commons.log.level=ERROR
                    sling.ignoreSystemProperties=false

                    Translate
                      CodelimeAuthor
                      Level 4
                      May 4, 2021 7:26 PM UTC

                      When I go to http://localhost:4502/system/console/status-slingsettings, I get this for the two lines referencing Sling Home:

                      Sling Home = /aem/crx-quickstart
Sling Home URL = file:/aem/crx-quickstart/

                      However, I'm unable to navigate to http://localhost:4502/aem/crx-quickstart. I get "page not found". Is there another way to access and edit the sling.properties file?

                      Translate
                        CodelimeAuthor
                        Level 4
                        May 4, 2021 6:24 PM UTC

                        I searched my PC and found eight yaml files, but they're all related to WKND.

                        docker-compose-wdio-firefox.yaml

                        docker-compose-wdio-chrome.yaml

                        etc...

                        Translate
                          Prince_Shivhare
                          Prince_Shivhare
                          New Participant
                          May 4, 2021 5:28 PM UTC

                          I hope you have checked this page-

                          https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requirements.html?lang=en#servlet-engines-application-servers

                           

                          There could be a lot of reasons for this.

                          Can you please help us with the AEM version?
                          Also, the error.log file which you can find under crx-quickstart/logs.

                          you would be getting something *ERROR*. please check these logs and let us know.

                           

                          Thanks,

                          Prince

                          Translate
                            Show more replies
                            Terms & ConditionsAccessibility statement

                            Loading footer...