publish replication not succesfull | Community
Skip to main content
daobing_ye
New Participant
February 10, 2016
Solved

publish replication not succesfull

  • February 10, 2016
  • 8 replies
  • 3518 views

Hi, all,

Got report from users that the replication from author to publish failed. Did the test of connection with the following errors:

~10.02.2016 16:29:54 - Create new HttpClient for Publish1 Agent
10.02.2016 16:29:54 - * Auth User: admin
10.02.2016 16:29:54 - * HTTP Version: 1.1
10.02.2016 16:29:54 - adding header: Action:Test
10.02.2016 16:29:54 - adding header: Path:/content
10.02.2016 16:29:54 - adding header: Handle:/content
10.02.2016 16:29:54 - deserialize content for delivery
10.02.2016 16:29:54 - No message body: Content ReplicationContent.VOID is empty
10.02.2016 16:29:54 - Sending POST request to http://localhost:5503/bin/receive?sling:authRequestLogin=1
10.02.2016 16:29:54 - sent. Response: 401 Unauthorized
10.02.2016 16:29:54 - Replication (TEST) of /content not successful. Conversation follows
10.02.2016 16:29:54 - ------------------------------------------------
10.02.2016 16:29:54 - Sending message to localhost:5503
10.02.2016 16:29:54 - >> POST /bin/receive HTTP/1.0
10.02.2016 16:29:54 - >> Action: Test
10.02.2016 16:29:54 - >> Path: /content
10.02.2016 16:29:54 - >> Handle: /content
10.02.2016 16:29:54 - >> Referer: about:blank
10.02.2016 16:29:54 - >> Content-Length: 0
10.02.2016 16:29:54 - >> Content-Type: application/octet-stream
10.02.2016 16:29:54 - --
10.02.2016 16:29:54 - << HTTP/1.1 401 Unauthorized
10.02.2016 16:29:54 - << Connection: Close
10.02.2016 16:29:54 - << Server: Day-Servlet-Engine/4.1.52
10.02.2016 16:29:54 - << Date: Wed, 10 Feb 2016 21:29:54 GMT
10.02.2016 16:29:54 - << WWW-Authenticate: Basic realm="Sling (Development)"
10.02.2016 16:29:54 - <<
10.02.2016 16:29:54 - Message sent.
10.02.2016 16:29:54 - ------------------------------------------------
10.02.2016 16:29:54 - Replication (TEST) of /content not successful.
Replication test failed
Unauthorized

 

in the author error.log file, got the following errors:

GET /libs/cq/core/content/login.html HTTP/1.1] servletengine Unable to send back last chunk: Broken pipe

Any suggestion where I should look into to fix the issue?

Thanks,

Daobing

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

You need to find out why you are getting the following message: 

"401 Unauthorized"

Are you able to successfully test the connection? Could it be that someone has changed the admin password on the publish instance?

Regards,

Opkar

8 replies

daobing_ye
New Participant
February 11, 2016

Hi, Opkar, you are right on money. I replaced the password, and it started working. Nobody should have changed that. I will track down.

Thanks for your help, and appreciate all the replies from Amit, Bsloki, Kautuk,

ogillAccepted solution
Employee
February 11, 2016

You need to find out why you are getting the following message: 

"401 Unauthorized"

Are you able to successfully test the connection? Could it be that someone has changed the admin password on the publish instance?

Regards,

Opkar

Lokesh_Shivalingaiah
New Participant
February 11, 2016

Are you able to access publish instance ??

kautuk_sahni
Employee
February 11, 2016

Hi 

Please have look at this forum post :- https://forums.adobe.com/thread/1173233?tstart=0

I hope this could help you.

Thanks and Regards

Kautuk Sahni

Kautuk Sahni
Amit_Kumar
New Participant
February 11, 2016

Can you check your logs, and share here so that we can see the debug trace to help you out.

daobing_ye
New Participant
February 11, 2016

Amit, thanks for the reply.These instances are running on the same VM. No firewall between them. Regarding the credentials, I'm logging as admin. it is the same for all instances. Just don't know where to start to look. Thanks. 

Amit_Kumar
New Participant
February 10, 2016

Check your creds and firewall settings.

daobing_ye
New Participant
February 10, 2016

The same configuration was working even yesterday.