Local AEM instance won't start (500 error)

[Codelime]

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?

[Codelime]

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?

[Codelime]

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

[BrianKasingli]

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.

[Codelime]

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?

[chintan97patel]

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.

[Codelime]

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.

[kautuk_sahni]

@chintan97patel, Thank you for sharing answer with AEM community. Keep doing the wonderful work. We need great AEM SME's like here. Keep it up. Looking forward to see you more in the AEM community.

[Ritesh_Mittal]

@Codelime ,

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

[Codelime]

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/

[Codelime]

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...

[Codelime]

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'.

[Ritesh_Mittal]

@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

[Codelime]

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

[Ritesh_Mittal]

@Codelime 

Follow below steps

1. Start AEM server (it is fine it is showing error but you should be able to access CRXDE)

2. Open http://<HOST>:<PORT>/crx/de 

3. Go inside /apps/<YOUR PROJECT>/config/rewriter.

4. Delete rewriter folder and save.

5. Restart AEM, this time you should not face any issue.

OR

Install the ACS commons Versioned Clientlibs package

[Codelime]

This worked. Thank you. Now I need to find the "Correct answer" link so I can mark this as the correct answer.