Publishing to multiple instances not triggering | Community
Skip to main content
N
nbg62
Level 4
February 10, 2023

Publishing to multiple instances not triggering

  • February 10, 2023
  • 2 replies
  • 1678 views

hi,

 

we created two publishing instances, on Authoring we configured two publish agents for each instance, test connection works fine for both agents.

Problem is that only first publish agent triggers and syndicates to publishing instance. Second publish agent is enabled connection works but no activity there. We don't see any errors, enabled syndication debugging on Author but there's no errors.

When we stop first publishing instance we see replication queue piling up on first publish agent but still nothing on second publish agent.

When we reconfigure first publish agent to replicate to second publishing instance that works as well.

 

In the replication log for second publish agent we can see.

 

2023-02-10 16:05:10 - INFO - publish-agent-2 : Replication (TEST) of /content successful.
2023-02-10 16:06:29 - INFO - publish-agent-2 : Agent stopped.
2023-02-10 16:06:29 - INFO - publish-agent-2 : Agent stopped for (re)configuration
2023-02-10 16:06:29 - INFO - publish-agent-2 : Agent configuration updated at /etc/replication/agents.author/publish-agent-2/jcr:content
2023-02-10 16:06:29 - INFO - publish-agent-2 : Agent updated. State is enabled and valid
2023-02-10 16:06:29 - INFO - publish-agent-2 : Agent started.
2023-02-10 16:06:31 - INFO - publish-agent-2 : Creating content for path /content
2023-02-10 16:06:31 - INFO - publish-agent-2 : Create new HttpClient for Publish agent 2
2023-02-10 16:06:31 - INFO - publish-agent-2 : * Auth User: admin
2023-02-10 16:06:31 - INFO - publish-agent-2 : * HTTP Version: 1.1
2023-02-10 16:06:31 - INFO - publish-agent-2 : * Connect Timeout: 900000
2023-02-10 16:06:31 - INFO - publish-agent-2 : * Socket Timeout: 900000
2023-02-10 16:06:31 - INFO - publish-agent-2 : Sending POST request to http://localhost:8083/bin/receive?sling:authRequestLogin=1
2023-02-10 16:06:31 - INFO - publish-agent-2 : sent. Response: 200 OK

 

 

Any ideas ?

 

Thank you

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

2 replies

Ritesh_Mittal
Community Advisor and Adobe Champion
Ritesh_MittalCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
February 10, 2023

HI @nbg62 ,

 

What AEM version are you using? Also, what I understanding is, you have one author and two publish instances. One Publish you are running on 8083 port, what port you are using for the second publish instance?

 

I can see the logs clearly says 'Connect Timeout', it means the server is not even up. Are you able to access AEM server on 8083 port on browser?

 

Thanks,

Ritesh Mittal

    N
    nbg62Author
    Level 4
    February 10, 2023

    >I can see the logs clearly says 'Connect Timeout', it means the server is not even up

     

    I think this represent default timeout value not that connection timed out

     

    Authoring is on 8081, and publishing instances od 82 and 83 and I can access all instances.

    AEM version is cluod runtime, 2022.6.7767.etc....

     

    Thanks

      krati_garg
      Adobe Employee
      krati_gargAdobe Employee
      Adobe Employee
      February 10, 2023

      @nbg62 

      Can you please check you have followed the right steps while configuring second Publish Agent. Like Serialization Type, Transport URI etc.

      https://experienceleague.adobe.com/docs/experience-manager-64/deploying/configuring/replication.html?lang=en#configuring-replication-for-multiple-publish-instances

       

      I just tried on my local, I made a copy of my default agent and pointed it towards 2nd Publisher. 

       

      It works fine and even logs says so.

       

        N
        nbg62Author
        Level 4
        February 10, 2023

        Second publishing agent is a copy of the first/default one, just that transport uri is changed to point to second publish instance.

          krati_garg
          Adobe Employee
          krati_gargAdobe Employee
          Adobe Employee
          February 16, 2023

          would it be possible to share screen shots of your Agent 1 and Agent 2, side by side (try adding screenshots of different tabs)

           

          You can start from scratch, delete agent 2 and follow below steps to create 2nd Agent.

          https://experienceleague.adobe.com/docs/experience-manager-64/deploying/configuring/replication.html?lang=en#configuring-replication-for-multiple-publish-instances

           

          @nbg62 

            Terms & ConditionsAccessibility statement

            Loading footer...