AEM 6.5 Service package install issues with SP 22 and 23 | Community
Skip to main content
V
VikramP8
Level 2
August 4, 2025
Question

AEM 6.5 Service package install issues with SP 22 and 23

  • August 4, 2025
  • 1 reply
  • 353 views

Hi Team,

 

We are using AEM 6.5 On-premise application hosted in aws ec2 linux servers. On trying to update the current version of AEM from aem-service-pack-6.5.19 to 6.5.22/6.5.23   we are facing issues with successful installation of service pack and it's not getting completed with below logs in error.log

 

Even waiting for long time the installation is not getting complete.

We are using AWS s3 data store and with in the install folder we have configs related to s3 datastore and the size of repository datastore is about 39GB. Also updated the oak-blob-store version from 1.22.6.jar to 1.22.22.jar

 

 

22.07.2025 09:14:01.226 *INFO* [Thread-1939] updater.aem-service-pkg Service [15057, [org.apache.sling.installer.api.event.InstallationListener]] ServiceEvent REGISTERED
22.07.2025 09:14:01.876 *INFO* [Thread-1939] com.adobe.granite.installer.Updater Waiting for installer to install/process packages...
22.07.2025 09:16:49.440 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Starting purge of uploaded files, current size [0 B]
22.07.2025 09:16:49.441 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Finished removal of [0] files, current size [0 B]
22.07.2025 09:21:49.440 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Starting purge of uploaded files, current size [0 B]
22.07.2025 09:21:49.441 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Finished removal of [0] files, current size [0 B]
22.07.2025 09:26:49.440 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Starting purge of uploaded files, current size [0 B]
22.07.2025 09:26:49.441 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Finished removal of [0] files, current size [0 B]
22.07.2025 09:31:49.440 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Starting purge of uploaded files, current size [0 B]
22.07.2025 09:31:49.441 *INFO* [oak-ds-cache-scheduled-thread-1] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Finished removal of [0] files, current size [0 B]
22.07.2025 09:36:49.440 *INFO* [oak-ds-cache-scheduled-thread-2] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Starting purge of uploaded files, current size [0 B]
22.07.2025 09:36:49.441 *INFO* [oak-ds-cache-scheduled-thread-2] org.apache.jackrabbit.oak.plugins.blob.UploadStagingCache Finished removal of [0] files, current size [0 B]

 

After uploading and installing the package. The localhost is not accessible with below error

 

Any suggestion on the above please.

 

Thanks

1 reply

S
ShivamKumar
Level 4
August 4, 2025

Hi @vikramp8 ,

I think AEM 6.5.22/6.5.23 service pack install hangs due to S3 datastore config interference and oak-blob-store version mismatch, which block installer execution and bundle activation, especially with large repo size and configs placed in /install during upgrade.

Try these things - 

 

  1. Stop AEM Instance.
  2. Clean Installer Cache: Delete contents of:- /crx-quickstart/launchpad/installer
  3. Revert oak-blob-store JAR:- Replace 1.22.22.jar with 1.22.6.jar (known stable with SP19–SP21).
  4. Temporarily Remove S3 Configs: Move S3-related .config files out of /install during SP installation.
  5. Restart AEM.
  6. Install SP via Package Manager UI:- Use /crx/packmgr to upload and install AEM-6.5-Service-Pack-23-6.5.23.zip.
  7. Verify Installation: Check:-
/system/console/bundles → All bundles should be Active/Resolved. /system/console/status-productinfo → Should show 6.5.23.0. /libs/system/aem-service-pckg-6.5.23 in CRXDE.

 

Let me know if this works.

    V
    VikramP8Author
    Level 2
    August 4, 2025

    Hi @shivamkumar 

    I have tried the above approach. I have moved the config files from install folder. On starting back the instance can't able to access /system/console and /crx/packmgr.

     

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...