Failed Upgrade of AEM 6.0 to AEM 6.1 | Community
Skip to main content
R
Rob_Curran__T4G
Level 3
March 7, 2016
Solved

Failed Upgrade of AEM 6.0 to AEM 6.1

  • March 7, 2016
  • 7 replies
  • 1955 views

Attempting to upgrade an AEM 6.0 (SP3) Author instance to AEM 6.1.

Following documentation that was successful on a previous AEM 6.0 install.  The only difference (that I can think of) is that this AEM 6.0 SP3 environment was originally upgraded from CQ 5.6.

Symptoms:

upgrade.log file should show "Startup mod is UPDATE" however it only contains one line:

07.03.2016 21:05:15.391 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE NOT NEEDED - StartupMode is INSTALL

Also, the following error shows up in the error.log:

07.03.2016 21:05:31.172 *ERROR* [qtp1358716119-36] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: AuthenticationSupport service missing. Cannot authenticate request. 07.03.2016 21:05:31.172 *ERROR* [qtp1358716119-36] org.apache.sling.engine.impl.SlingHttpContext handleSecurity: Possible reason is missing Repository service. Check AuthenticationSupport dependencies.

The cmd line executed was as follows:

D:\author>java -Xmx3072m -jar aem-6.1-author-p4502.jar Loading quickstart properties: default Loading quickstart properties: instance Low-memory action set to fork Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork argume nts=[-Xmx1024m, -XX:MaxPermSize=256m] The JVM reports a heap size of 2731 MB, meets our expectation of 1024 MB +/- 20 Setting properties from filename 'D:/author/aem-6.1-author-p4502.jar' Option '-quickstart.server.port' set to '4502' from filename aem-6.1-author-p450 2.jar Setting 'sling.run.modes' to 'author,qa' from sling.properties. Ignoring value '' from command line. Verbose option not active, closing stdin and redirecting stdout and stderr Redirecting stdout to D:\author\crx-quickstart\logs\stdout.log Redirecting stderr to D:\author\crx-quickstart\logs\stderr.log Press CTRL-C to shutdown the Quickstart server...

Any ideas on why this might not be upgrading?

Can you force an upgrade on AEM 6.0 like you could on CQ 5.6 by adding the cmd line parameter:  

-Dorg.apache.sling.launchpad.startupmode=update

Any help appreciated...

Thanks.

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 Rob_Curran__T4G

Ticket... 87197

 

Thanks.

7 replies

R
Rob_Curran__T4GAuthor
Level 3
March 7, 2016

Attempted with cmd line parameter startupmode=update

java -jar -Xmx3072m -Dorg.apache.sling.launchpad.startupmode=update aem-6.1-author-p4502.jar

Result was the same except for the update.log which shows:

07.03.2016 21:33:19.402 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE STARTS - StartupMode is UPDATE 07.03.2016 21:33:19.402 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator Collecting CodeUpgradeTasks 07.03.2016 21:33:19.402 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator NO UPGRADE TASKS - no com.day.cq.compat.codeupgrade.CodeUpgradeTask services found, nothing to do

 

Same Authentication error in error.log.

smacdonald2008
smacdonald2008
Level 10
March 7, 2016

HI - i asked support to look at this to see if there is a known issue. 

Sham_HC
Sham_HC
Level 10
March 7, 2016

can you add -nofork to the end & verify.

R
Rob_Curran__T4GAuthor
Level 3
March 7, 2016

Thanks for the reply.

 

Same result with the following cmd line:

java -jar -Xmx3072m -Dorg.apache.sling.launchpad.startupmode=update aem-6.1-author-p4502.jar -nofork
smacdonald2008
smacdonald2008
Level 10
March 8, 2016

Can you open a ticket for this one. 

R
Rob_Curran__T4GAuthorAccepted solution
Level 3
March 8, 2016

Ticket... 87197

 

Thanks.

R
Rob_Curran__T4GAuthor
Level 3
March 29, 2016

Resolved.

There were two issues at play.   

1) Unexpectedly the installation being upgraded had been running a pre-GA release of AEM 6.0.  This prevented the upgrade from succeeding.   After replacing the AEM jar and restarting the instance from the cmd line (effectively upgrading it to AEM 6.0 GA) this issue was resolved.

2) Secondly, we had to login to CRX/DE as admin and removed /var/upgrade/PreserveContentHook and /var/upgrade/status.  Additionally, removed the everyone Deny ACL from /var/upgrade.

After making these changes the upgrade was successful.

Thanks to Adobe support for their help. 

Terms & ConditionsAccessibility statement

Loading footer...