AEM upgrade 6.5 - Determining the correct upgrade start command not working

Avatar

Avatar
Validate 1
Level 2
ashishkhadpe
Level 2

Likes

4 likes

Total Posts

50 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
ashishkhadpe
Level 2

Likes

4 likes

Total Posts

50 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Ignite 1
Boost 3
Boost 1
View profile
ashishkhadpe
Level 2

26-11-2020

Hi All,

 

As per the steps provided on adobe site I have determined the start command after repository migration as below : 

 

java -server -Xms2g -Xmx8g -Djava.awt.headless=true -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=100000 -Doak.fastQuerySize=true -javaagent:/opt/newrelic/newrelic.jar -Dcom.sun.management.jmxremote.port=10060 -Dcom.sun.management.jmxremote.authenticate=true -Dcom.sun.management.jmxremote.password.file=/app/aem/crx-quickstart/bin/jmx_pass -Dcom.sun.management.jmxremote.access.file=/app/aem/crx-quickstart/bin/jmx_user -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.rmi.port=10061 -Dsling.run.modes=publish,crx3,crx3tar -jar cq65-publish-p4503.jar start -c crx-quickstart -i launchpad -p 4503 -Dsling.properties=conf/sling.properties

 

But when I execute it I get below error :

Loading quickstart properties: default

Loading quickstart properties: instance

org.apache.commons.cli2.OptionException: Unexpected start while processing Use these options on the Quickstart command line.

at org.apache.commons.cli2.commandline.Parser.parse(Parser.java:99)

at com.adobe.granite.quickstart.base.impl.Main.<init>(Main.java:594)

at com.adobe.granite.quickstart.base.impl.Main.main(Main.java:981)

 

Any idea what can be the issue?

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Vish_dhaliwal
Employee

27-11-2020

Hello Ashish,

 

I would recommend removing the extra params and try the startup command as described here:

https://experienceleague.adobe.com/docs/experience-manager-65/deploying/upgrading/in-place-upgrade.h...

 

You can add these params later in the startup script after the first start.

 

Regards,

Vishu

Answers (1)

Answers (1)

Avatar

Avatar
Affirm 50
Level 6
Bhuwan_B
Level 6

Likes

133 likes

Total Posts

124 posts

Correct reply

50 solutions
Top badges earned
Affirm 50
Give Back 5
Boost 100
Give Back 3
Affirm 25
View profile

Avatar
Affirm 50
Level 6
Bhuwan_B
Level 6

Likes

133 likes

Total Posts

124 posts

Correct reply

50 solutions
Top badges earned
Affirm 50
Give Back 5
Boost 100
Give Back 3
Affirm 25
View profile
Bhuwan_B
Level 6

26-11-2020

Check this article for step by step upgrade process to successfully transition into AEM version 6.5.

https://hashouttech.com/blog/How-to-Upgrade-Adobe-Experience-Manager-to-AEM-Version-6.5