Hi All,
I am trying to setup a replication agent between my author and publish server(Default Replication agent on Author).
when I test the connection and page keep spinning in browser.
Below is the error i get in replication.log (Bold)
26.09.2022 22:12:44.949 *INFO* [sling-oak-observation-15] com.day.cq.replication.Agent.publisherone Agent stopped for (re)configuration 26.09.2022 22:12:44.949 *INFO* [sling-oak-observation-15] com.day.cq.replication.Agent.publisherone Agent configuration updated at /etc/replication/agents.author/publisherone/jcr:content 26.09.2022 22:12:44.949 *INFO* [sling-oak-observation-15] com.day.cq.replication.Agent.publisherone Agent updated. State is enabled and valid 26.09.2022 22:12:44.949 *INFO* [sling-oak-observation-15] com.day.cq.replication.Agent.publisherone Agent started. 26.09.2022 22:12:45.181 *DEBUG* [63.96.15.115 [1664248365030] GET /etc/replication/agents.author/publisherone.html HTTP/1.1] com.day.cq.replication.Agent.publisherone.queue Queue com/day/cq/replication/job/publisherone not found
I have checked the following:
A) Correct Transport URI(Able to hit the Transport URI individually with transport user id and password in browser directly)
b) Transport user id and password correct.Able to login to Pub using the transport uid and pwd
c)Agent id was left blank(default)
d) No space in replication agent name.
Please suggest what might be the issue.
Solved! Go to Solution.
Views
Replies
Total Likes
@milind_bachani Thank you for your suggestions. The issue was 'replication-service' missing all permissions. Reverted those permissions back same as out of the box fixed the issue.
@Siva_Sogalapalli Thanks for your reply ! yes, I followed all the steps from the adobe documentation.
Hi @Ganthimathi_R ,
Did you create a fresh replication agent or you just have updated the old default replication agent with required properties ?
What is the status of the queue when you check on this path : http://localhost:4502/etc/replication/agents.author.html ?
Can you try following things as well :
Thanks,
Milind
@milind_bachani Thank you for your suggestions. The issue was 'replication-service' missing all permissions. Reverted those permissions back same as out of the box fixed the issue.
Views
Likes
Replies