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

SOLVED

Upgrade from 6.4 to 6.5.9, then AEM cannot be restarted

rickyaut
Level 2
Level 2

I am working on an upgrade project, the current AEM being used is 6.4.8, I upgraded it to 6.5.0, good as expected. Then installed 6.5.9 service pack, it is initially working and I can see the version number change in system console product information, however, when I trigger restart, AEM failed and generated a lot of errors in stdout.log.

I tried a lot of different upgrade path, only 6.5.0->6.5.9 succeeded.

Failed upgrade path

6.4.0->6.4.8->6.5.0-x>6.5.9

6.4.0->6.4.8->6.5.0-x>6.5.8

6.4.0->6.4.8->6.5.0-x>6.5.7

6.4.0->6.4.8->6.5.0->6.5.6-x>6.5.7

6.4.0->6.4.8->6.5.0->6.5.6-x>6.5.8

6.4.0->6.4.8->6.5.0->6.5.6-x>6.5.9

 

Here is the initial error in stdout.log

28.07.2021 21:28:54.621 *ERROR* [FelixStartLevel] ERROR: Bundle '1' Error starting slinginstall:com.adobe.granite.crypto-3.4.12.jar (org.osgi.framework.BundleException: Unable to resolve com.adobe.granite.crypto [1](R 1.2): missing requirement [com.adobe.granite.crypto [1](R 1.2)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.6)(!(version>=2.0.0))) [caused by: Unable to resolve slf4j.api [4](R 4.0): missing requirement [slf4j.api [4](R 4.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j.impl)(version>=1.6.0)) [caused by: Unable to resolve org.apache.sling.commons.log [9](R 9.1): missing requirement [org.apache.sling.commons.log [9](R 9.1)] osgi.wiring.package; (osgi.wiring.package=javax.xml.namespace)]] Unresolved requirements: [[com.adobe.granite.crypto [1](R 1.2)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.6)(!(version>=2.0.0)))])
org.osgi.framework.BundleException: Unable to resolve com.adobe.granite.crypto [1](R 1.2): missing requirement [com.adobe.granite.crypto [1](R 1.2)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.6)(!(version>=2.0.0))) [caused by: Unable to resolve slf4j.api [4](R 4.0): missing requirement [slf4j.api [4](R 4.0)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j.impl)(version>=1.6.0)) [caused by: Unable to resolve org.apache.sling.commons.log [9](R 9.1): missing requirement [org.apache.sling.commons.log [9](R 9.1)] osgi.wiring.package; (osgi.wiring.package=javax.xml.namespace)]] Unresolved requirements: [[com.adobe.granite.crypto [1](R 1.2)] osgi.wiring.package; (&(osgi.wiring.package=org.slf4j)(version>=1.7.6)(!(version>=2.0.0)))]
at org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:4368)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2281)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1539)
at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)
at java.lang.Thread.run(Thread.java:748)
1 Accepted Solution
sprince1504
Correct answer by
Level 2
Level 2

do you have anything generated on error.log

View solution in original post

2 Replies
sprince1504
Correct answer by
Level 2
Level 2

do you have anything generated on error.log

View solution in original post

rickyaut
Level 2
Level 2

hi, @sprince1504:

There is no information in error.log, only above information in stdout.log.

My upgrade process was found incorrect in the end: After I run java command with `unpack` option, I deleted 6.4.0.jar from crx-quickstart/app manually and ran bin/start to start AEM. Although it was started successfully, it is not following the correct upgrade process and is a problematic upgrade even though it is showing version number change and can be upgraded to 6.5.6.

 

For reference, please follow AEM In-place upgrade document