Installing AEM6.5 on AWS and having issues

[companion31z]

Hello, 

I am trying to install AEM6.5 on AWS EC2 instance and similar to what we do on-prem, I am trying to execute the below to install 

java -jar cq5-author-p5502.jar -r author

It does create the crx-quickstart and all the respective folders but when i try to start the instance from bin/start it appears to get stuck at the below and generates core dump -

29.06.2022 11:12:37.227 *INFO* [FelixStartLevel] org.apache.tika.parsers BundleEvent STARTING
29.06.2022 11:12:37.365 *INFO* [FelixStartLevel] org.apache.tika.parsers Service [720, [org.apache.tika.detect.Detector]] ServiceEvent REGISTERED 

Below is what i see in the hotspot file, please let me know if anyone has faced such an issue and have been able to fix it. Appreciate it!

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fc6ad73bfe5, pid=636524, tid=0x00007fc6877ce700
#
# JRE version: OpenJDK Runtime Environment (8.0_332-b09) (build 1.8.0_332-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.332-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libopmpreloader.so+0xddfe5]
#
# Core dump written. Default location: /products/aem/v6.5-author/core or core.636524

# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

--------------- T H R E A D ---------------

Current thread (0x00007fc6a5d4f000): JavaThread "FelixStartLevel" daemon [_thread_in_native, id=636556, stack(0x00007fc6876c
e000,0x00007fc6877cf000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000000

Registers:
RAX=0x0000000000000000, RBX=0x0000000000000000, RCX=0x00000000fffffec0, RDX=0x0000000000000046
RSP=0x00007fc6877cb020, RBP=0x0000000000000000, RSI=0x00007fc6adb5b1ac, RDI=0x0000000000000001

[SantoshSai]

Hi @companion31z ,

• Run mode you are using in your command author is out-of-the-box, no need to specify it
  try to use 
  

  java -jar cq5-author-p5502.jar

• -r options is used to activate a custom run mode. eg 
  

  author + development
  publish + test
  publish + test + golive
  publish + intranet

Please read [0] documentation for more details to set flags according to your requirement while setting up environment

Additionally, confirm if your pre-requisite technical requirements are met as specified in [1] eg Java, Maven etc.
Based on your above error # JRE version: OpenJDK Runtime Environment (8.0_332-b09) (build 1.8.0_332-b09) - for AEM 6.5 recommended version is Java 11

OR

You can use -unpack flag to setup -

• Place the jar file in a folder where you want to deploy the AEM application.
• Open a terminal or command prompt, navigate to the folder where you placed the jar file,
• and run the command “java -jar aem-author-4502.jar -unpack”.
• Execute “./crx-quickstart/bin/quickstart”.

[0]: https://experienceleague.adobe.com/docs/experience-manager-65/deploying/configuring/configure-runmod...

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

Hope that helps!
Regards,

Santosh

[companion31z]

Thanks for your response Santosh! I did try to test it even with Java 11 but the behavior was similar. When i try using the unpack option and run quickstart i get the below segmentation error and it generates the core dump -

OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Loading quickstart properties: default
Loading quickstart properties: instance
./quickstart: line 122: 14049 Segmentation fault java $CQ_JVM_OPTS -jar $CQ_JARFILE $START_OPTS

[SantoshSai · Accepted solution]

@companion31z Please check this may help: https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16542.html?lang=en