AEM 6.1 to AEM6.3 in-place upgrade issue | Community
Skip to main content
Level 3
July 11, 2018

AEM 6.1 to AEM6.3 in-place upgrade issue

  • July 11, 2018
  • 2 replies
  • 6512 views

Hi All,

I am upgrading AEM 6.1 to 6.3 and encountered some issue along the way.

Content migration process:

java -Xmx4096m -jar cq-author-p4502.jar -v -x crx2oak -xargs -- --load-profile segment-no-ds

Upgrade command:

java -Xmx4096m -XX:MaxPermSize=2048m -jar aem6-author-p4502.jar -Dsling.run.modes=author,crx3,crx3tar

Below is the log error:

10.07.2018 22:20:08.477 *WARN* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade Exception in Cq62MediaContentUpgrade.run()

java.lang.NullPointerException: null

at org.apache.jackrabbit.oak.jcr.delegate.AuthorizableDelegator.unwrap(AuthorizableDelegator.java:65)

at org.apache.jackrabbit.oak.jcr.delegate.GroupDelegator$4.perform(GroupDelegator.java:121)

at org.apache.jackrabbit.oak.jcr.delegate.GroupDelegator$4.perform(GroupDelegator.java:117)

at org.apache.jackrabbit.oak.jcr.delegate.SessionDelegate.perform(SessionDelegate.java:208)

at org.apache.jackrabbit.oak.jcr.delegate.GroupDelegator.isMember(GroupDelegator.java:117)

at com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade.doUpgrade(Cq62MediaContentUpgrade.java:130)

at com.day.cq.compat.codeupgrade.impl.AbstractCodeUpgradeTask.run(AbstractCodeUpgradeTask.java:64)

at com.adobe.cq.upgradesexecutor.Activator.runUpgradeTasks(Activator.java:350)

at com.adobe.cq.upgradesexecutor.Activator.finishUpgradeExecution(Activator.java:220)

at com.adobe.cq.upgradesexecutor.Activator.start(Activator.java:170)

at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)

at org.apache.felix.framework.Felix.activateBundle(Felix.java:2227)

at org.apache.felix.framework.Felix.startBundle(Felix.java:2145)

at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1372)

at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308)

at java.lang.Thread.run(Thread.java:748)

10.07.2018 22:20:08.478 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK FAILED: Cq62MediaContentUpgrade

10.07.2018 22:20:40.310 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE FINISHED: 20 CodeUpgradeTasks executed , 1 CodeUpgradeTasks failed (out of 25), total time about 33 seconds

Other than the above exception and task failure, all other things looks normal. “toprocess” folder is empty and “mergestatus” is also completed.

Any pointers to resolve the above failed task? is there any way we can resume from the current state of the server or do we have to revet back to AEM 6.1 and we have to start upgrading from scratch again?

Thanks!

Dinesh kumar L.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Adobe Employee
July 11, 2018

You would need to provide the upgrade.log for review or carefully go though warning and errors as this would give an indication why this task failed

Level 3
July 11, 2018
Content backfill required
Adobe Employee
July 11, 2018

Dinesh, we already have a ticket raised by your team to troubleshoot this. The support team would get intouch with you soon over the Daycare portal.

Adobe Employee
July 11, 2018

Can you check if mp-editors and content-authors group exists in the CRX ? Also, check if the "random authorizable" setting ws changed in AEM 6.1 ? If yes, this would have to reverted prior to the upgrade to 6.3

Level 3
July 16, 2018

Thanks Kunwar,

As you highlighted, the issue got resolved after reverting back mp-editors and content-authors groups to OOTB permission settings. These two groups were not having read accessing to /libs and /apps.