AEM upgrade from 6.3 to 6.5 publish instance upgrade.log file | Community
Skip to main content
Level 2
January 5, 2021
Solved

AEM upgrade from 6.3 to 6.5 publish instance upgrade.log file

  • January 5, 2021
  • 1 reply
  • 1977 views
29.12.2020 21:30:42.850 *INFO* [com.adobe.granite.quickstart.base.impl.upgrade.UpgradeUtil] UpgradeUtil.java:769 Writing installer state

During the in-place upgrade process, the author instance upgraded successfully with full description in upgrade.log file and log entry that upgrade process completed. In the case of publish instance that log file ends with the statement: "UpgradeUtil.java:769 Writing installer state".

Other post-upgrade checks passed.

STDOUT:
05.01.2021 15:46:31.196 *INFO* [com.adobe.granite.quickstart.base.impl.upgrade.UpgradeUtil] UpgradeUtil.java:769 Writing installer state
05.01.2021 15:46:33.056 *INFO * [main] Setting sling.home=/opt/aem/publish/crx-quickstart (command line)
05.01.2021 15:46:33.057 *INFO * [main] Starting Apache Sling in /opt/aem/publish/crx-quickstart
05.01.2021 15:46:33.059 *INFO * [main] Sling Extension Lib Home : /opt/aem/publish/crx-quickstart/launchpad/ext
05.01.2021 15:46:33.059 *INFO * [main] Checking launcher JAR in folder /opt/aem/publish/crx-quickstart/launchpad
05.01.2021 15:46:33.067 *INFO * [main] Installing new launcher: jar:file:/opt/aem/publish/crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar!/resources/org.apache.sling.launchpad.base.jar, 6.0.2.2_6_36 (org.apache.sling.launchpad.base.jar.1609861593067)
05.01.2021 15:46:33.068 *INFO * [main] Loading launcher class org.apache.sling.launchpad.base.app.MainDelegate from org.apache.sling.launchpad.base.jar.1609861593067
05.01.2021 15:46:33.069 *INFO * [main] Sling Extension jars found = [ /opt/aem/publish/crx-quickstart/launchpad/ext/certjFIPS-2.1.2.0.jar,/opt/aem/publish/crx-quickstart/launchpad/ext/bcprov-jdk15-1.35.jar,/opt/aem/publish/crx-quickstart/launchpad/ext/bcmail-jdk15-1.35.jar,/opt/aem/publish/crx-quickstart/launchpad/ext/cryptojcommon-6.0.0.jar,/opt/aem/publish/crx-quickstart/launchpad/ext/jcmFIPS-6.0.0.jar,/opt/aem/publish/crx-quickstart/launchpad/ext/cryptojce-6.0.0.jar, ]
05.01.2021 15:46:33.101 *INFO * [main] Setting org.apache.felix.http.context_path=crx-quickstart
05.01.2021 15:46:33.101 *INFO * [main] Setting sling.properties=conf/sling.properties
05.01.2021 15:46:33.101 *INFO * [main] Setting sling.home=/opt/aem/publish/crx-quickstart
05.01.2021 15:46:33.106 *INFO * [main] Setting sling.launchpad=/opt/aem/publish/crx-quickstart/launchpad
05.01.2021 15:46:33.106 *INFO * [main] Setting org.osgi.service.http.port=4503
05.01.2021 15:46:33.106 *INFO * [main] Starting launcher ...
05.01.2021 15:46:33.112 *INFO * [main] HTTP server port: 4503
05.01.2021 15:46:40.051 *INFO * [main] Startup completed

And no further logs in upgrade.log


UPDATE: 
At the end of the story issue was related to log config duplication and this article helped to fix it
http://www.aemcq5tutorials.com/tutorials/duplicated-osgi-configurations-upgrade/

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by shelly-goel

@oleksandrr13925 

That should be fine. Do you see any errors or issues?

1 reply

shelly-goel
Adobe Employee
shelly-goelAdobe EmployeeAccepted solution
Adobe Employee
January 6, 2021

@oleksandrr13925 

That should be fine. Do you see any errors or issues?

Level 2
January 6, 2021