Package Manager - Uploading fails on ACS AEM Commons 5.0.14 | Community
Skip to main content
Sebastiane_Edberg_
Community Advisor
Sebastiane_Edberg_Community Advisor
Community Advisor
December 7, 2021

Package Manager - Uploading fails on ACS AEM Commons 5.0.14

  • December 7, 2021
  • 2 replies
  • 7353 views

Hi there, upload fails on the ACS AEM Commons 5.0.14 zip file with this error, what could be the reason for this?

 

Version Adobe Experience Manager 2021.11.6058.20211123T163652Z-211000

 

 

 

 

 

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

2 replies

Raja-Karuppsamy
Community Advisor
Raja-KaruppsamyCommunity Advisor
Community Advisor
December 7, 2021

@sebastiane_edberg_ What's the AEM version you are using ?  Can you check your error log for more information ?

 

Please refer this article: https://githubmemory.com/repo/Adobe-Consulting-Services/acs-aem-commons/issues/2566

 

    Sebastiane_Edberg_
    Community Advisor
    Sebastiane_Edberg_Community AdvisorAuthor
    Community Advisor
    December 7, 2021

    i am not seeing anything related to this error in the logs actually

      Kishore_Kumar_
      Kishore_Kumar_
      Level 9
      December 7, 2021

      Hi @sebastiane_edberg_ ,

       

      I am unable to replicate this issue in local instance of aem-sdk-2021.11.6058.20211123T163652Z-211000. I am able to upload and install ACS commons 5.0.14 package successfully.

       

       

        Sebastiane_Edberg_
        Community Advisor
        Sebastiane_Edberg_Community AdvisorAuthor
        Community Advisor
        December 8, 2021

        @kishore_kumar_ any idea what i should start troubleshooting? is it a dependency that is not installed or could it be permission related? 

          Sebastiane_Edberg_
          Community Advisor
          Sebastiane_Edberg_Community AdvisorAuthor
          Community Advisor
          January 4, 2022

          @kishore_kumar_ 
          During the deployment to dev, I tried many changes and always got failed in the last step - "Deploy to Dev" for AEM as a cloud service. And the following messages are printed in logs.

          Failed logs

          2021-12-31T12:11:00+0000 Summary of events during the deployment step:
2021-12-31T12:11:00+0000 Begin deployment in poc-jira-asset-dev [CorrelationId: 8666415]
2021-12-31T12:11:03+0000 Update author indexes job has started.
2021-12-31T12:13:32+0000 Update author indexes job has finished successfully.
2021-12-31T12:13:32+0000 Update publish indexes job has started.
2021-12-31T12:13:43+0000 Update publish indexes job has finished successfully.
2021-12-31T12:15:41+0000 Build Transform job has started.
2021-12-31T12:15:41+0000 Build Transform job has finished successfully.
2021-12-31T13:16:00+0000 Failed deployment in poc-jira-asset-dev
2021-12-31T13:16:00+0000 Detailed events during the deployment step:
...
[2021/12/31 12:12:13] [ info] [engine] started (pid=19)
[2021/12/31 12:12:13] [ info] [storage] version=1.1.1, initializing...
[2021/12/31 12:12:13] [ info] [storage] in-memory
[2021/12/31 12:12:13] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2021/12/31 12:12:13] [error] [sqldb] cannot open database /var/log/aem/logs_error.db
[2021/12/31 12:12:13] [error] [input:tail:tail.1] could not open/create database

          Normal logs

          2021-12-30T11:52:54+0000 Summary of events during the deployment step:
2021-12-30T11:52:54+0000 Begin deployment in poc-jira-asset-dev [CorrelationId: 8662021]
2021-12-30T11:52:57+0000 Update author indexes job has started.
2021-12-30T11:57:49+0000 Update author indexes job has finished successfully.
2021-12-30T11:57:49+0000 Update publish indexes job has started.
2021-12-30T11:58:00+0000 Update publish indexes job has finished successfully.
2021-12-30T11:59:58+0000 Build Transform job has started.
2021-12-30T11:59:58+0000 Build Transform job has finished successfully.
2021-12-30T12:03:17+0000 Install mutable content job has started.
2021-12-30T12:05:49+0000 Install mutable content job has finished successfully.
2021-12-30T12:05:50+0000 Finished deployment in poc-jira-asset-dev
2021-12-30T12:05:50+0000 Detailed events during the deployment step:
...
[2021/12/30 12:03:41] [ info] [engine] started (pid=19)
[2021/12/30 12:03:41] [ info] [storage] version=1.1.1, initializing...
[2021/12/30 12:03:41] [ info] [storage] in-memory
[2021/12/30 12:03:41] [ info] [storage] normal synchronization mode, checksum disabled, max_chunks_up=128
[2021/12/30 12:03:41] [ info] [http_server] listen iface=0.0.0.0 tcp_port=2020
[2021/12/30 12:03:41] [ info] [sp] stream processor started

          As you see, the words in bold are differences. Within failed logs, there are no installing mutable content job steps, but there are error - "cannot open database /var/log/aem/logs_error.db"
          Do you have any ideas? Thanks.



          @huideshao @kishore_kumar_ 

           

          I now get the errors described here when deploying to dev https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/2604

          Code scanning partially passes with a "D" in reliability rating, there are two lines marked as critical:

          adobe/consulting:acs-aem-commons-ui.apps:5.1.0,0,The product interface com.day.cq.search.Query annotated with @ProviderType should not be implemented by custom code. Detected in com.adobe.acs.commons.search.CloseableQuery contained in /apps/acs-commons/install/acs-aem-commons-bundle-5.1.0.jar.,Bug,Critical,30m,CQRules:CQBP-84,cqsoftwarequality,https://www.adobe.com/go/aem_cmcq_cqbp-84_en

          adobe/consulting:acs-aem-commons-ui.apps:5.1.0,0,The product interface com.day.cq.search.Query annotated with @ProviderType should not be implemented by custom code. Detected in com.adobe.acs.commons.wrap.cqsearch.QueryIWrap contained in /apps/acs-commons/install/acs-aem-commons-bundle-5.1.0.jar.,Bug,Critical,30m,CQRules:CQBP-84,cqsoftwarequality,https://www.adobe.com/go/aem_cmcq_cqbp-84_en

           

           

          It is possible to override and continue build in pipeline but maybe theres a better option?

            Terms & ConditionsAccessibility statement

            Loading footer...