AEM ReplicationServlet Error during replication: Repository error during content import: No such file or directory | Community
Skip to main content
S
shivashankarhr1
September 22, 2023

AEM ReplicationServlet Error during replication: Repository error during content import: No such file or directory

  • September 22, 2023
  • 4 replies
  • 1930 views

Hi Team,

 

Getting below error when trying to replicate assets from AEM 6.5.16 Author (nosamplecontent) to Publish for specific assets and replication gets blocked further. These assets are well replicated in the lower enviornment (nosamplecontent). No repository datastore exception found with the Author or Publish instances. Other assets are replicating without issues. Any support helps.

 

21.09.2023 09:07:49.243 *ERROR* [10.64.65.73 [1695287269242] POST /bin/receive HTTP/1.1] com.day.cq.replication.impl.servlets.ReplicationServlet Error during replication: Repository error during content import: No such file or directory
com.day.cq.replication.ReplicationException: Repository error during content import: No such file or directory
at com.day.cq.replication.impl.content.durbo.DurboImporter.createNode(DurboImporter.java:218) [com.day.cq.cq-replication:6.2.86.CQ650-B0006]

..

..

Caused by: java.io.IOException: No such file or directory

 

--

Thanks

Shiva

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

4 replies

krati_garg
Adobe Employee
krati_gargAdobe Employee
Adobe Employee
September 22, 2023

@shivashankarhr1 Have you recently upgraded?

 

Could be a Repo inconsistency issue. If you have upgraded to a latest version or migrated from Enterprise to Cloud, please mention the same.

    S
    shivashankarhr1Author
    September 25, 2023

    @krati_garg  there is no error related to repository inconsistency seen in the log. Its a stand-alone setup of AEM 6.5.16 and not upgraded from any previous version of AEM.

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      September 25, 2023

      Can you confirm which type of asset you are trying to activate? Also, can you verify that in your replication agent, the Transport URL is not encoded? Sometimes the transport URL may be encoded, and this can interfere with the replication of assets.

      Esteban Bustamante
        S
        shivashankarhr1Author
        September 25, 2023

        @estebanbustamante  type of asset can be any in this case not specific to any type of the asset. Transport URL is also not encoded. 

          S
          shivashankarhr1Author
          September 26, 2023

          Issue seems to be with temp directory which AEM is using, will update if this fix the issue.

            kautuk_sahni
            Community Manager
            kautuk_sahniCommunity Manager
            Community Manager
            October 4, 2023

            @shivashankarhr1  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

            Kautuk Sahni
            Terms & ConditionsAccessibility statement

            Loading footer...