AEM 6.5 Publisher startup issue

[kirankumark9814]

we are trying to upgrade from 6.3 to 6.5, We have taken fresh AEM 6.5 and deploying code and content from AEM 6.3 instance. After content migration, all AEM service hangs and stays in the startup in progress and most of the bundle shows resolved status

1. happening only on the publisher mode of the instance 
2. No significant error logs observed

[Vaibhavi_J]

Hi @kirankumark9814 , 

Have you checked stderr.log ? 

This will have the information about the errors during startup. 

[kirankumark9814]

Hi @Vaibhavi_J, I checked, No stderr.log coming. Is there any settings to need enable it ?

[Varun_Shakya]

After AEM 6.4 there is a change in repository and if you upgrading it to 6.5. I would suggest follow the guidelines provided by Adobe. 

https://docs.adobe.com/content/help/en/experience-manager-65/deploying/upgrading/upgrade.html

[Surabhi_Katiyar]

From the description, I understand that the issue is only coming in the Publisher and the Author has been upgraded successfully with any such issue.

So, in this case, check the upgrade logs if the upgrade has been done successfully without any errors. Then check the stderr.log file for errors during the startup of the AEM Publish instance.

[kirankumark9814]

It is not correct answer, just clicked by mistakenly. There are no stderr.log coming on the instance and we are not doing in-place upgrade here.

[Surabhi_Katiyar]

kirankumark9814 Try to create a new publisher again and check if the same issue comes up and if yes then open a support ticket so that this can be investigated in detail.

[kirankumark9814]

@Surabhi_KatiyarTried recreating multiple times and observed the same issue, also observed service will come up after 2 or 3 Hrs and again hangs in case if we restart. Too weird

During startup, I Can see this error

*ERROR* [FelixStartLevel] com.adobe.cq.deserfw.impl.DeserializationFirewallImpl Unable to load Attach API. Unable to dynamically load deserialization protection agent. This usually happens when running a JRE (instead of a JDK) or a JVM that doesn't provide the Attach API. Please review the AEM Java Deserialization Firewall documentation for how to load the deserialization agent via JVM command-line arguments.

[kirankumark9814 · Accepted solution]

RESOLVED:  The issue was with 2 wrong DNS on Health check nodes. in AEM 6.5.5 this has been addressed added timeout configuration on this.

com.adobe.cq.security.hc.dispatcher.impl.DispatcherAccessHealthCheck
com.adobe.cq.security.hc.webserver.impl.ClickjackingHealthCheck

[Aseema-Pandit]

Hello Kiran,

Do you mean you had to install SP5 to get the above issue resolved?