Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Local AEM instance won't start (500 error)

Codelime
Level 4
Level 4

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
jbrar
Employee
Employee

Check the error.log file for errors. Also, Make sure the underlying Java version was not changed

Codelime
Level 4
Level 4
Thanks for the reply. Where do I find the error.log file? Java should not have changed.
Asutosh_Jena_
Community Advisor
Community Advisor

Hi @Codelime 

 

Please check for the errors in error.log located at aem location /crx-quickstart/logs/error.log

Also which version of AEM you are running and what is the Java version?

Have you done any change to any of the code and deployed which broke the system or this just happened all of sudden?

 

It will be in the file system where your AEM binary is installed and running.

If you still don't fine then try the below URL and check:

http://localhost:4502/system/console/slinglog/tailer.txt?tail=10000&grep=*&name=%2Flogs%2Ferror.log

 

Hi @Codelime 

 

Please navigate to http://localhost:4502/system/console/status-slingsettings
and check for Sling Home URL property which will give you the location of the AEM installation.

 

Navigate to the crx-quickstart/conf folder from the above location i.e. the AEM installation location and look for sling.properties file.

In the sling.properties file look for sling.bootdelegation.sun=sun.*,com.sun.*
and replace it with sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*

 

Restart the instance. Your instance should be back up and running.

 

Hope this helps!

 

Thanks

Codelime
Level 4
Level 4

I don't see an error log file when I navigate here: http://localhost:4502/crx/de/index.jsp#/crx-quickstart/logs/error.log

Asutosh_Jena_
Community Advisor
Community Advisor

It will be available in you aem installation location in file system followed by /crx-quickstart/logs/error.log

Asutosh_Jena_
Community Advisor
Community Advisor

Hi @Codelime 

It is not in crx/de. It will be in the file system where your AEM binary is installed and running.

If you still don't fine then try the below URL and check:

http://localhost:4502/system/console/slinglog/tailer.txt?tail=10000&grep=*&name=%2Flogs%2Ferror.log

 

Thanks!

Codelime
Level 4
Level 4

I tried that URL earlier, but get a blank screen.

 

Codelime_0-1620139182432.png

 

Asutosh_Jena_
Community Advisor
Community Advisor

Do you see all the bundles in active state here?

http://localhost:4502/system/console/bundles

Codelime
Level 4
Level 4

Yes, all the bundles are active here: http://localhost:4502/system/console/bundles

Codelime
Level 4
Level 4

java version "11.0.10" 2021-01-19 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.10+8-LTS-162)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.10+8-LTS-162, mixed mode)

 

Docker version 20.10.5, build 55c4c88

 

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\opt\apache-maven-3.6.3\bin\..
Java version: 11.0.10, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk-11.0.10
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Asutosh_Jena_
Community Advisor
Community Advisor

Hi @Codelime 

 

Please navigate to http://localhost:4502/system/console/status-slingsettings
and check for Sling Home URL property which will give you the location of the AEM installation.

 

Navigate to the crx-quickstart/conf folder from the above location i.e. the AEM installation location and look for sling.properties file.

In the sling.properties file look for sling.bootdelegation.sun=sun.*,com.sun.*
and replace it with sling.bootdelegation.sun=sun.*,com.sun.*,jdk.internal.reflect,jdk.internal.reflect.*

 

Restart the instance. Your instance should be back up and running.

 

Hope this helps!

Codelime
Level 4
Level 4

I have this URL bookmarked, which I've always been able to access, but now I get a blank screen:

Codelime_0-1620140847747.png

I navigated to http://localhost:4502/system/console/status-slingsettings

Codelime_1-1620140908422.png

But I get page not found when I go to http://localhost:4502/aem/crx-quickstart/

Codelime_2-1620141026109.png

 

Codelime
Level 4
Level 4

I found this:

Codelime_0-1620143291231.png

What's the recommended way to edit this file?

Asutosh_Jena_
Community Advisor
Community Advisor
Do you know where the AEM jar file is present. How are you starting the instance? You need to look for sling.properties file in the file system.
Codelime
Level 4
Level 4

My process for starting local AEM:

  1. Open Docker Desktop
  2. In Docker Desktop, start "author (aemdesign/aem)" container
  3. Open Eclipse
  4. In Eclipse, start "Adobe Experience Manager at localhost" server.
  5. In browser, navigate to http://localhost:4502/aem/start.html. This typically takes me to the AEM login page, but it's not working today.

I'm looking for the jar file. Would the jar file be named something specific for our project?

Asutosh_Jena_
Community Advisor
Community Advisor

Hi @Codelime 

Check the docker-compose.yaml or docker command which launched the container to see if a drive was mounted in a specific way.

 

See if you have something like:

C:\opt\aem\author\crx-quickstart

or may be like:

C:\opt\cq

 

Else you need to check with the person who has setup the AEM instance for you to identify the location.

Prince_Shivhare
Community Advisor
Community Advisor

I hope you have checked this page-

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/introduction/technical-requi...

 

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

Codelime
Level 4
Level 4

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