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

[oleksandrr13925]

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/

[shelly-goel · Accepted solution]

@oleksandrr13925 

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

[oleksandrr13925]

https://issues.apache.org/jira/browse/SLING-6313

[oleksandrr13925]

I think this Sling bug, causing my issue with upgrade.log file. In error.log file I have this multiple times about different log files:

05.01.2021 18:23:27.362 *ERROR* [CM Configuration Updater (Update: pid=org.apache.sling.commons.log.LogManager.factory.config~upgrade.config)] org.apache.felix.configadmin Service [org.apache.felix.cm.ConfigurationAdmin,18, [org.osgi.service.cm.ConfigurationAdmin]] [org.osgi.service.cm.ManagedServiceFactory, id=10, bundle=1/slinginstall:org.apache.sling.commons.log-4.0.2.jar]: Updating property org.apache.sling.commons.log.names of configuration org.apache.sling.commons.log.LogManager.factory.config~upgrade.config caused a problem: Category com.day.cq.compat.codeupgrade already defined by configuration org.apache.sling.commons.log.LogManager.factory.config.1aa73e9b-9393-4a08-9f17-70f24d89c7c0 (org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names : Category com.day.cq.compat.codeupgrade already defined by configuration org.apache.sling.commons.log.LogManager.factory.config.1aa73e9b-9393-4a08-9f17-70f24d89c7c0)
org.osgi.service.cm.ConfigurationException: org.apache.sling.commons.log.names : Category com.day.cq.compat.codeupgrade already defined by configuration org.apache.sling.commons.log.LogManager.factory.config.1aa73e9b-9393-4a08-9f17-70f24d89c7c0
at org.apache.sling.commons.log.logback.internal.config.LoggerManagedServiceFactory.updated(LoggerManagedServiceFactory.java:36)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.updated(ManagedServiceFactoryTracker.java:159)
at org.apache.felix.cm.impl.helper.ManagedServiceFactoryTracker.provideConfiguration(ManagedServiceFactoryTracker.java:93)
at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1400)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.sling.commons.log.logback.internal.config.ConfigurationException:
at org.apache.sling.commons.log.logback.internal.LogConfigManager.updateLoggerConfiguration(LogConfigManager.java:538)
at org.apache.sling.commons.log.logback.internal.config.LoggerManagedServiceFactory.updated(LoggerManagedServiceFactory.java:34)
... 6 common frames omitted

[oleksandrr13925]

So after upgrade I have duplicate factory configurations in Felix admin /system/console/configMgr, but I am not 100%.

[shelly-goel]

@oleksandrr13925 Yes I faced the duplicate factory config issue as well in one of the upgrades and deleting them manually (I had quite a less number) fixed it. On the same link shared by you, there's a tool to find duplicates and delete them which you can use: https://github.com/cqsupport/felix-osgi-utils/tree/master/felix-osgi-config-repair