Highlighted

In-place upgrade from AEM 6.3.1.2 to AEM 6.4

apolu

26-07-2018

Hi Everyone,

We are trying to do in-place upgrade from AEM 6.3.1.2 to 6.4 in our dev environment vy following the official adobe documnet

Performing an In-Place Upgrade

Preparation of the AEM Quickstart jar file

  • Stop the instance if it is running
  • Download the new  AEM6.4 jar file and use it to replace the old one outside the crx-quickstart folder.
  • Unpack the new quickstart jar by running:
  • java -jar AEM_6.4_author-p4504.jar –unpack

Note: Content Repository Migration step skipped as we are using AEM6.3

  • Determining the correct upgrade start command:
  • Modify the command by replacing the path to the existing jar (crx-quickstart/app/aem-quickstart*.jar in this case) with the new jar that is a sibling of the crx-quickstart folder. Using our previous command as an example, our command would be:
  • Started the java with command line as suggested in doc by replacing the latest AEM6.4 jar file

AEM services started fine by following above steps except system console all other modules like (welcome/crx/siteadmin) etc is not loading ,from the console and logs here is my observations

My repository size is around 300GB and since 24hrs am waiting to see the server coming up but no luck, Kindly someone suggested what could be the cause or do i need to stop the service and start it again?

Note: Error.log is keep writing below mention data

Console output when we accessed the crx/welcome/siteadmin page

Startup in progress

Running CQ62Html5SmartFileUpgrade: Migrating html5smartfile resources

From the upgarde.log

26.07.2018 14:53:23.251 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.StatusNode Upgrade recorded, /var/upgrade/status/Cq62TargetCampaignsContentUpgrade set to Thu Jul 26 14:53:23 IST 2018

26.07.2018 14:53:23.252 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK DONE: Cq62TargetCampaignsContentUpgrade

26.07.2018 14:53:23.475 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.StatusNode /var/upgrade/status/Cq62MediaContentUpgrade does not exist, upgrade needed

26.07.2018 14:53:23.475 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK STARTING: Cq62MediaContentUpgrade

26.07.2018 14:53:23.930 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade starting to migrating /etc/cloudservices/dps ACLs

26.07.2018 14:53:23.989 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade finsihed migrating /etc/cloudservices/dps ACLs

26.07.2018 14:53:23.989 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade starting to migrating /content/publications ACLs

26.07.2018 14:53:24.049 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade finsihed migrating /content/publications ACLs

26.07.2018 14:53:24.049 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade starting to migrating /content/publications ACLs

26.07.2018 14:53:24.065 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade finsihed migrating /content/publications ACLs

26.07.2018 14:53:24.985 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.Cq62MediaContentUpgrade All done.

26.07.2018 14:53:25.313 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.StatusNode Upgrade recorded, /var/upgrade/status/Cq62MediaContentUpgrade set to Thu Jul 26 14:53:25 IST 2018

26.07.2018 14:53:25.314 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK DONE: Cq62MediaContentUpgrade

26.07.2018 14:53:25.439 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.StatusNode /var/upgrade/status/CQ62Html5SmartFileUpgrade does not exist, upgrade needed

26.07.2018 14:53:25.440 *INFO* [FelixStartLevel] com.adobe.cq.upgradesexecutor.Activator UPGRADE TASK STARTING: CQ62Html5SmartFileUpgrade

26.07.2018 14:53:25.641 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.CQ62Html5SmartFileUpgrade Migrating html5smartfile resources

26.07.2018 14:53:25.641 *INFO* [FelixStartLevel] com.day.cq.compat.codeupgrade.impl.cq62.CQ62Html5SmartFileUpgrade Waiting indexing to be done for property xtype

From Error.log:

27.07.2018 08:32:42.066 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Reindexing Traversed #440000 /jcr:system/jcr:versionStorage/ac/13/7c/ac137c3f-2acf-4a96-b1e4-79cdd22bbdb0 [1473.40 nodes/s, 5304227.75 nodes/hr] (Elapsed 4.382 min, Expected 37.53 min, Completed 11.71%)

27.07.2018 08:32:46.948 *INFO* [async-index-update-async] org.apache.jackrabbit.oak.plugins.index.IndexUpdate Reindexing Traversed #450000 /jcr:system/jcr:versionStorage/11/b1/a6/11b1a668-be55-4ddc-8589-1cfa191fa3de/1.0/jcr:frozenNode/jcr:content/related [1486.46 nodes/s, 5351270.84 nodes/hr] (Elapsed 4.464 min, Expected 37.10 min, Completed 11.97%)

Thanks,

Amarnath Polu

Replies

Kunwar

Employee

27-07-2018

I don't see any issue with these logs. There are 26 upgrade tasks and they need to complete before  the upgrade is complete. CQ62Html5SmartFileUpgrade is one of those steps.

I suspect these environment has many many nodes where you it's parsing coz the version purge and other maintenance activities were not performed before the upgrade was started.

Highlighted

apolu

29-07-2018

Hi All,

Thanks for the valuable replies, 

"There are 26 upgrade tasks and they need to complete before  the upgrade is complete. CQ62Html5SmartFileUpgrade is one of those steps."

is there any way to see the progress on completion of all the 26 tasks? i mean, when can the total activity completed (from system console/tool/logs etc..)

Kunwar​, i have tried with other environment where i have cleanup activities, old package cleanup, offline compaction, version purge( weekly configured) etc.

total crx-quickstart(80GB), repository (70GB)

But in this scenario also am observing the same situation(re-indexing going on) whatever i explained in my initial thread

Can someone guide me further steps except raising a  ticket to adobe

Thanks,

Amarnath Polu

Highlighted

Kunwar

Employee

30-07-2018

You can just monitor the logs for the status on this as these are sequential steps and complete one after the other.

I'd expect this index cycle and would wait till the reindexing to complete. This would eventually come up unless there are any errors in the upgrade.log

If you think, it isn't moving only thing I can think of is to engage support so they can have an indepth review of the lgs